"Hundreds of applications and websites impacted by the AWS outage are now back online and operating as normal. However, questions still remain over the cost of the incident and a growing reliance on a select few cloud providers underpinning the digital economy. Over the course of Monday morning through to the afternoon, services running on AWS struggled with outages, hitting websites but also payment services."
"The outage began late Sunday night, AWS said in a statement, with increased error rates in what it calls the US-EAST-1 Region, which is northern Virginia - home to a huge swathe of data centers. By just after midnight, Amazon realized the problem was caused by DNS resolution issues for regional DynamoDB service endpoints, and mitigated it by 2:24am PDT, so by just about half past 10am in the UK."
"AWS said the incident was triggered by a DNS issue and that services were largely up and running by the afternoon, though a backlog of messages would take time to work through. The incident follows last year's CrowdStrike outage and a similar outage by AWS in 2021, highlighting our overreliance on digital systems and networks run by a few companies - a fact noted by many industry experts over the last day or so."
Services running on AWS experienced outages starting late Sunday night in the US-EAST-1 region, affecting hundreds of applications, websites and payment systems. Amazon identified DNS resolution failures for regional DynamoDB endpoints and mitigated the primary issue by 2:24am PDT, though full recovery required clearing backlogs and restoring impaired internal subsystems. AWS stated services were largely restored by afternoon, but message backlogs remained. The incident follows similar outages in 2021 and last year's CrowdStrike interruption, underscoring systemic risk from concentration among a few cloud providers. Analysts pointed to DNS and cloud architecture shortcomings as root resilience concerns.
Read at IT Pro
Unable to calculate read time
Collection
[
|
...
]