71–80 of 95 posts
As if all their code was geared to AWS services and they were banned, they couldn't easily deploy elsewhere without a re-write
I stick to to VMs/kubernetes and containers and VMs. No own brand services.
"An AWS consultant who’d been covering my bills disappeared". I wouldn't be surprised if the payer filed a chargeback and then AWS went nuclear.
"The post-closure period is 90 days—during this time, an account can be reopened and data is retained."
Digging deeper, it seems like the user just did it themselves. Didn’t properly verify their account. That’s the end. What do you expect?
"The post-closure period is 90 days—during this time, an account can be reopened and data is retained."
Is this a great situation? No. It's also not "I did everything right and boo hoo AWS did a boo boo". AWS is not your friend, but you also weren't the customer, that was the middleman you gave ownership to.
"An AWS consultant who’d been covering my bills disappeared". I wouldn't be surprised if the payer filed a chargeback and then AWS went nuclear.
If they don’t “know you” financially you’ll need to jump through compliance questions before your new payment method is accepted. If you don’t verify the email verification mail within the 5 days I imagine you have to jump through more hoops, which this person didn’t do in time.
https://www.seuros.com/blog/aws-deleted-my-10-year-account-w...
Root cause: the author had some wacky service-end setup with their AWS account (presumably to save a few cents per month) and the third party screwed them.
Digging deeper, it seems like the user just did it themselves. Didn’t properly verify their account. That’s the end. What do you expect?
> July 14: Form expired. I contact support. Simple question: “What do you need from me?”
> July 16-20: Four days of silence. Then: “We’re escalating to the appropriate > team.”
> July 20: New form finally arrives.
> July 21: I submit ID and utility bill (clear PDF). Response time: 10 hours.
> July 22: AWS: “Document unreadable.” The same PDF my bank accepts without question. > July 23: Account terminated. My birthday gift from AWS.
If I understand the timeline, how were they going to verify themselves properly?
It's not sudden, the account owner disappeared and the account user (the one making all the noise) did not get ownership transferred. Is this a great situation? No. It's also not "I did everything right and boo hoo AWS did a boo boo". AWS is not your friend, but you also weren't the customer, that was the middleman you gave ownership to.
[1] https://www.seuros.com/blog/aws-deleted-my-10-year-account-w...
Author here: Let’s be clear on backups: Yes, I had backups everywhere. Across providers, in different countries. But I built a system tied to my AWS account number, my instances, my IDs, my workflows. When that account went down, all those “other” backups were just dead noise encrypted forever. Bringing them up to the story only invites the 'just use your other backups' fallback, and ignores the real fragility of cen…
> AWS is the apex cloud provider on the planet. This isnt about redundancy or best practices. Sorry, but it is absolutely and undeniably not! I don't think it's accurate to portray AWS as the underlying infrastructure of the internet on the planet at all. Speaking of the "planet", here's a sample statistics for .ru ccTLD on web hosting usage across the 1 million domain names in the zone — one of the top-10 ccTLD zone…