- status boards are rarely up to date, make sure you have your own internal/external monitoring
- a single vm instance does not indicate the health of an entire region. instances can be stopped for a variety of reasons, check the maintenance log and vm console
- when using cloud resources, architecture should not be dependent on a single vm instance
- your cloud architecture and app code should be built to handle transient failures from the start - queueing, retries, backoffs, load-shedding, graceful state failure, etc. use cloud-native services when possible, lift-and-shift of traditional vm architecture to the cloud can be operationally difficult and expensive to run
Serious answer: People will confirm or not in the comments, this post seems pretty reasonable, if a little trigger happy. It could just be a random launch failure.
I've certainly not seen any issue with us-west-2 in the last 24 hours.
For what it's worth, just successfully launched an EC2 instance and created a Bucket...