5 ms·

Obviously we don't know what the extent of the issue is yet, but afaik there has never been an AWS incident that has affected multiple regions where an applicat

Obviously we don't know what the extent of the issue is yet, but afaik there has never been an AWS incident that has affected multiple regions where an application had been designed to use them (like using region specific S3 endpoints). GCP and Azure have had issues in multiple regions that would have affected applications designed for multi-region.

votepaunchy 7y ago
> like using region specific S3 endpoints AWS had the S3 incident affecting all of us-east-1: “Other AWS services in the US-EAST-1 Region that rely on S3 for storage, including the S3 console, Amazon Elastic Compute Cloud (EC2) new instance launches, Amazon Elastic Block Store (EBS) volumes (when data was needed from a S3 snapshot), and AWS Lambda were also impacted while the S3 APIs were unavailable.” https://aws.amazon.com/message/41926/ https://aws.amazon.com/message/41926/
- WaxProlix 7y ago
  There was a massive push after that to have everything regionalized. It's not 100% but it's super close at this point.
  - dodobirdlord 7y ago
    S3 buckets are a global namespace, so control plane operations have to be single-homed. As an example, global consensus has to be reached before returning a success response for bucket creation to ensure that two buckets can't be created with the same name.
    - solidasparagus 7y ago
      But isn't CreateBucket the single s3 operation where you need global consistency?
      - dodobirdlord 7y ago
        As far as I know bucket policy operations also require global consistency.
    - cavisne 7y ago
      The availability of CreateBucket shouldnt effect the availability of customers apps. This tends to be true anyway because of the low default limit of buckets per account (if your service creates buckets as part of normal operation it will run out pretty quickly). The difference with Google Cloud is a lot of the core functionality (networking, storage) is multi region and consistent. The only thing thats a bit like that in AWS is IAM, however IAM is eventually consistent.
- tango24 7y ago
  That's one region, not the multiple region that OP mentioned
  - AaronFriel 7y ago
    Services in other regions depended transitively on us-east-1, so it was a multiple region outage.
    - sterwill 7y ago
      Which services in other regions? I remember that day well, but I had my eyes on us-east-1 so I don't remember what else (other than status reporting) was affected elsewhere.

votepaunchy 7y ago

> like using region specific S3 endpoints AWS had the S3 incident affecting all of us-east-1: “Other AWS services in the US-EAST-1 Region that rely on S3 for storage, including the S3 console, Amazon Elastic Compute Cloud (EC2) new instance launches, Amazon Elastic Block Store (EBS) volumes (when data was needed from a S3 snapshot), and AWS Lambda were also impacted while the S3 APIs were unavailable.” https://aws.amazon.com/message/41926/ https://aws.amazon.com/message/41926/

WaxProlix 7y ago
There was a massive push after that to have everything regionalized. It's not 100% but it's super close at this point.
- dodobirdlord 7y ago
  S3 buckets are a global namespace, so control plane operations have to be single-homed. As an example, global consensus has to be reached before returning a success response for bucket creation to ensure that two buckets can't be created with the same name.
  - solidasparagus 7y ago
    But isn't CreateBucket the single s3 operation where you need global consistency?
    - dodobirdlord 7y ago
      As far as I know bucket policy operations also require global consistency.
  - cavisne 7y ago
    The availability of CreateBucket shouldnt effect the availability of customers apps. This tends to be true anyway because of the low default limit of buckets per account (if your service creates buckets as part of normal operation it will run out pretty quickly). The difference with Google Cloud is a lot of the core functionality (networking, storage) is multi region and consistent. The only thing thats a bit like that in AWS is IAM, however IAM is eventually consistent.
tango24 7y ago
That's one region, not the multiple region that OP mentioned
- AaronFriel 7y ago
  Services in other regions depended transitively on us-east-1, so it was a multiple region outage.
  - sterwill 7y ago
    Which services in other regions? I remember that day well, but I had my eyes on us-east-1 so I don't remember what else (other than status reporting) was affected elsewhere.