this post was submitted on 20 Oct 2025
481 points (99.4% liked)
Technology
76252 readers
3208 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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...
Sounds reasonable, the first errors I encountered were all 403.
Butbutbut AWS reliability and many regions and zones means this can't happen! ;-)