""After resolving the DynamoDB DNS issue, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB," the status page explains. Not being able to launch EC2 instances meant Amazon's foundational rent-a-server offering was degraded, a significant issue because many users rely on the ability to automatically create servers as and when needed."
"While Amazonian engineers tried to get EC2 working properly again, "Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch." AWS recovered Network Load Balancer health checks at 9:38 AM, but "temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations.""
A DNS failure prevented services from reaching a DynamoDB API and was corrected at 02:24 AM PDT. After that fix, an EC2 internal subsystem that depends on DynamoDB became impaired, preventing EC2 instance launches and degrading core compute capabilities. Network Load Balancer health checks then became impaired, causing connectivity issues for Lambda, DynamoDB, and CloudWatch. AWS restored load balancer health checks at 9:38 AM but temporarily throttled operations such as EC2 launches, SQS processing via Lambda, and asynchronous Lambda invocations to aid recovery. Throttling was reduced over time and services returned to normal by 3:01 PM.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]