8:05 AM PST: Kinesis is experiencing increased API errors in the US-EAST-1 Region.The Kinesis Data Streams API is currently impaired in the US-EAST-1 Region. As a result customers are not able to write or read data published to Kinesis streams.
CloudWatch metrics and events are also affected, with elevated PutMetricData API error rates and some delayed metrics.
While EC2 instances and connectivity remain healthy, some instances are experiencing delayed instance health metrics, but remain in a healthy state.
AutoScaling is also experiencing delays in scaling times due to CloudWatch metric delays.
This is also causing issues with ACM, Amplify Console, API Gateway, AppMesh, AppStream2, AppSync, Athena, AutoScaling, Batch, CloudFormation, CloudTrail, CloudWatch, Cognito, Connect, DynamoDB, EventBridge, IoT Services, Lambda, LEX, Managed Blockchain, Resource Groups, SageMaker, Support Console, and Workspaces.
Other services, like S3, remain unaffected by this event.
This issue has also affected our ability to post updates to the Service Health Dashboard.
We are continuing to work towards resolution.
https://status.aws.amazon.com/
Update.+ CloudFront:
We are investigating longer than usual reporting update delays for change propagation of invalidations and CloudFront configurations. Customer changes are propagating fine across our edge locations but the associated reporting is not getting updated. Also, end-user requests for content from our edge locations are not affected by this issue and are being served normally.
+ Fargate:
We are investigating increased API error rates and delays delivering task events and metrics in the
US-EAST-1 region. We are also investigating increased task launch error rates for the Fargate launch type. Running tasks are not impacted.+ EKS:
We are investigating increased API error rates for cluster and node group operations in the
US-EAST-1 region. We are also investigating increased Fargate pod launch failures. Existing EKS clusters and managed node groups are operating normally+ ECS:
Currently running ECS tasks are not impacted for either the EC2 or Fargate launch types. We are continuing to experience API error rates and delays delivering task events and metrics in the
US-EAST-1 region. ECS clusters are also not able to scale up or down due to task launch errors. Customers are missing metrics and events from their running tasks as ECS Insights is not able to propagate information. Task Set and Capacity Providers are also impacted. Customers using ECS on Fargate are not able to launch new tasks, running Fargate tasks are not impacted.===
Обновление после окончания инцидента — официальный отчёт о том, что произошло:
https://aws.amazon.com/message/11201/