Wherever possible, don't use us-east-1. It's one of the older regions and parts are aging. Yes, I know there are things that are only available in the old regions but most services are globally available. I've worked with a few ex AWS SWEs and SREs. They drink the kool-aid and won't say anything bad about us-east-1 but they also won't launch net-new services there. YMMV
I modified some of our IAM policies earlier this afternoon, followed by the pages that some of our teams were having IAM issues, caused me great discomfort
This probably needs a better link, but the AWS status page shows everything up.<p>UPDATE: Status page now shows it
<a href="https://status.aws.amazon.com/#" rel="nofollow">https://status.aws.amazon.com/#</a>
Noticed something odd today I think is connected to this.<p>The other day we started using Access Advisor, and we found some of our KMS key policies with a Principal of '*'.<p>It wasn't marked as globally open, so we planned to fix them a little later.<p>This morning we found that status had changed.<p>While we were in the wrong to begin with, it was a little surprising to find the interpretation of the key policy changing overnight.<p>Of course it became our top priority and is now fixed.
Something to look out for...
I noticed (pre outage) IAM console won't work at all if I --disable-reading-from-canvas in my launch args to prevent fingerprinting. All the other service consoles I use work. I have to have a special config for my browser just for AWS because of it. Wishful thinking, but maybe they're fixing that just for me.