I suspect the big problem is that IAM is affected and it is not decentralized, which is causing other systems worldwide (even outside of AWS’ us-east-1 location) which rely on IAM in us-east-1 to also fail. I’m having trouble even logging into the AWS console to check on my European servers.
Edit: IAM is the main authentication method. So AWS may still be up and running fine in other locations around the world; but if you can’t connect to them because AWS’ internal authentication is all fucked up…
https://health.aws.amazon.com/health/status
I suspect the big problem is that IAM is affected and it is not decentralized, which is causing other systems worldwide (even outside of AWS’ us-east-1 location) which rely on IAM in us-east-1 to also fail. I’m having trouble even logging into the AWS console to check on my European servers.
Edit: IAM is the main authentication method. So AWS may still be up and running fine in other locations around the world; but if you can’t connect to them because AWS’ internal authentication is all fucked up…
Butbutbut AWS reliability and many regions and zones means this can’t happen! ;-)
Sounds reasonable, the first errors I encountered were all 403.