us-west

This might be a reason to move your production environment out of us-west-1 for a few years.

We had some Opsworks instances reboot as well, but only minor outages overall (us-east and us-west).

US-East -> US-West), the latencies between the containers seem far higher than just the 200-300ms predicted by speed of light.

I'm sure it's fine, at least as well as a manually-configured NFS, but it's only US-West (Oregon) now.

I agree - the docs are kinda hard to parse, and after launch it didn't work in us-west-2 for several hours.

While Amazon is headquartered on the west coast, I sincerely doubt a failure of even both us-west regions would take out the others.

E.g., CPU userspace cycles on all your instances should be like: provider.region.vpc.group.instance-id.os.cpu.user E.g.: aws.us-west-1.prod.web-front.i-4df567a9.os.cpu.user Then wildcard queries will provide you aggregate stats at any level you like.

I've been seeing connectivity issues with us-west-2 for most of the day.

They have a couple of subdomains hosted with AWS, in the us-west region looks like.

Sure, the AWS us-west datacenters would go down (Oregon and NorCal), but us-east (VA) is still the largest of all AWS regions.

Ultimately it's up to the user: if they're going to put all their eggs in a us-west basket, they're out of luck if the west coast ends up under water.

A notable beta user: AWS will be running a 4.8 megawatt hour pilot program with Tesla's batteries in the us-west-1 AZ (Northern California).