News for hackers. Stuff that matters.

A comment on Google Kubernetes Engine's third consecutive day of service disruption. Parent comment

Re:Google Kubernetes Engine's third consecutive day of servi... by mcqueenjordan on Sunday November 11, 2018 @06:20PM (#18429354)
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.)
[ Parent | on HN ]
Re:Google Kubernetes Engine's third consecutive day of servi... by Twirrim on Sunday November 11, 2018 @06:50PM (#18429504)
Buckets 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.
[ Parent | on HN ]
Re:Google Kubernetes Engine's third consecutive day of servi... by jsjohnst on Sunday November 11, 2018 @07:28PM (#18429690)
This is correct (or at least was a couple years ago).
[ Parent | on HN ]
Re:Google Kubernetes Engine's third consecutive day of servi... by sascha_sl on Sunday November 11, 2018 @06:36PM (#18429431)
Correct, but quite a few AWS services are built on S3, and some apparently weren't using buckets per region.
[ Parent | on HN ]