Service: Amazon WorkSpaces
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#workspaces-us-east-1_1606362975

We have identified the root cause of the issue affecting provisioning of Amazon WorkSpaces in the US-EAST-1 Region. We expect to see recovery once the on-going Kinesis issue is fully resolved. We recommend customers do not perform modify, migrate, reboot, rebuild and/or restore operations on existing WorkSpaces at this time.

#workspaces #useast1

Service: Amazon CloudWatch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#cloudwatch-us-east-1_1606364282

We continue to experience API error rates and delayed CloudWatch metrics. We expect to see recovery once the on-going Kinesis issue is fully resolved. Metrics will start to backfill once the Kinesis issue is resolved.

#cloudwatch #useast1

Service: Amazon Kinesis Data Streams
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#kinesis-us-east-1_1606366390

We are continuing to relax the request throttles for Kinesis Data Streams and are gradually increasing the traffic into the service. We have not yet enabled requests to Kinesis Data Streams from VPC Endpoints. The Kinesis Data Streams subsystem continues to operate normally, and we expect incremental recovery over the next few hours.

#kinesis #useast1

Отлично

Очереди это сложно, даже для aws.

Service: Amazon Elastic Container Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ecs-us-east-1_1606367163

ECS is investigating slow deprovisioning of tasks causing tasks to remain in a deactivating or deprovisioning for extended periods of time. For ECS tasks using awsvpc networking mode, including Fargate tasks, this means the ENI associated with the task remains provisioned longer than normal. CloudWatch Container Insights is now correctly showing recent metrics from ECS. CloudWatch metrics for ECS and Capacity Providers are continuing to see impact while we wait for Kinesis and CloudWatch recovery.

#ecs #useast1

Service: AWS IoT Core
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#awsiot-us-east-1_1606368068

We are seeing recovery for Connect and Subscribe operations in the US-EAST-1 region. We continue to work towards full resolution. Messaging on existing connections and Shadow operations continue to operate normally.

#awsiot #useast1

Service: Amazon WorkSpaces
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#workspaces-us-east-1_1606368148

We are beginning to see recovery on provisioning of Linux and non-BYOL Windows WorkSpaces in the US-EAST-1 Region. We recommend customers continue to not perform modify, migrate, reboot, rebuild and/or restore operations on all existing WorkSpaces until complete recovery. We continue to work toward full resolution.

#workspaces #useast1

Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606368232

We have full recovery for AWS Batch jobs not using AWSvpc networking mode. Customers running Multi-Node Parallel jobs may see deprovisioning delays while we wait for ECS recovery.

#batch #useast1

Service: Amazon Kinesis Data Streams
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#kinesis-us-east-1_1606368404

We have now enabled a subset of requests to Kinesis Data Streams using VPC Endpoints.

#kinesis #useast1

Service: Amazon CloudFront
Region: 🌏 Global
URL: http://status.aws.amazon.com/#cloudfront_1606369471

CloudFront Access Logs, Metrics, and Reporting continues to be affected by the Kinesis event but we are continuing to observe partial recovery. CloudFront edge locations are continuing to serve traffic as expected and change propagations and invalidations times are nominal.

#cloudfront

Service: Amazon Elastic Kubernetes Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#eks-us-east-1_1606369706

We continue to observe partial recovery for EKS cluster and node group API operations in the US-EAST-1 Region and are working towards full resolution. We expect to see complete recovery once the on-going Kinesis issue is fully resolved. Until then, customers may still experience errors when creating, upgrading and deleting EKS clusters and managed node groups.

#eks #useast1

Service: Amazon EventBridge
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1606369955

Between 5:15 AM and 9:30 PM PST, we experienced elevated API errors and event delivery latency in the US-EAST-1 Region related to an issue with Kinesis Data Streams. While the issue has been resolved and the service is operating normally, we are continuing to work through the backlog of AWS CloudTrail events which will be delivered over the next several hours.

#events #useast1

Идея для доклада на re:Invent 2020 от AWS - подробнейший постмортем для этого (еще не закончившегося) инцидента.

Вероятно на re:Invent будет какая то фича которая всё и сломала))

Только что

Каждому свои проблемы)) кому бакс, кому лежащий авс

Как там оно, кто-нить уже залезал смотреть?

CloudMap еще барахлит у нас