4 ms·
On February 28th, 2017, S3 had issues in us-east-1, not globally. It just happens that most customers create their buckets in us-east-1. (It’s the default bucke
by mcqueenjordan 8y ago
On February 28th, 2017, S3 had issues in us-east-1, not globally. It just happens that most customers create their buckets in us-east-1. (It’s the default bucket creation region.)
- sascha_sl 8y agoCorrect, but quite a few AWS services are built on S3, and some apparently weren't using buckets per region.
- Twirrim 8y agoBuckets creation/deletion is a global operation, namespaces are all global for it. When us-east-1 goes down, so does bucket creation. All other operations proceed merrily, but yeah as we see over and over again, whenever us-east-1 has an outage everything seems to shit the bed because they've built everything out in us-east-1. Hopefully us-east-2 is starting to eat in to that.
- jsjohnst 8y agoThis is correct (or at least was a couple years ago).