[huksley]

If you are given only 5 days to comply with some request, that's how complicated your infra at AWS should be - so you can migrate to another provider in that time.

Just use EC2 and basic primitives which are easy to migrate (ie S3, SES)

[seuros]

Hi, The infrastructure was not complex at at all, i can transfer it in 1 day.

I was hospitalized, in another city, with all the computer at home, and locked behind 2FA.

They send me is on notice on Thursday, by Monday evening, all access was revoked.

For weeks i asked for a readonly access to my data, then they could take anytime they want to verify, they refused.

And he more i ask about my data, they more they avoid to speak about it.

Think about it , you could be sick, on a trip, having jetlag, in some festival, getting married... by the time you are back online, the delay was gone.

[jasonvorhe]

The amount of people shilling for a multi billion dollar corporation is baffling.

[throwaway81523]

https://en.wikipedia.org/wiki/System_justification_theory_(s...

[whstl]

You know the quote: It is difficult to get a man to understand something, when his salary depends on his not understanding it.

A lot of people in this industry have near-zero operations knowledge that doesn't involve AWS, and it's frightening.

[jasonvorhe]

True. I get that you can blame someone for having no backups and yoloing their thing. But OP did so much right if the threat model doesn't involve "corporate behemoth anti-user automation nukes everything including backups".

Everyone saying "you should've had offsite backups" certainly has a point but 99% of the blame lies with AWS here. This entire process must've crossed so many highly paid "experts" and no one considered freezing an account before nuking it for some compliance thing.

It's just baffling.

Hope these cases will lead to more people leaving the clouds and going back to on-prem stuff.

[whstl]

It is worth saying that AWS educates people to behave like this.

In the last "mandatory education program" I participated, the AWS instructor laughed at the possibility of data loss.

[anonymars]

Worth noting that's not the only way this can be a single point of failure, this one was an account breach:

https://www.infosecurity-magazine.com/news/code-spaces-demis...

[AtlasBarfed]

Should I bring up Elon Musk? That gets into cult behavior

[S0y]

>Just use EC2 and basic primitives which are easy to migrate (ie S3, SES)

If that's your whole infra you really shouldn't be on AWS in the first place.

[adastra22]

A bit ironic when that entire stack was invented at AWS.

[NewJazz]

VMs were invented at AWS? Blob storage?

[adastra22]

EC2? S3? Yes. That kind of "cloud" tech was invented at AWS. Nothing like the ec2 API existed before Amazon. It's what made AWS big. Maybe my graybeard is showing, but I remember when that kind of pre-containerization cloud provisioned VM resources was a radically new idea.

[cnst]

FreeBSD jail predates Amazon Web Services, and so does SWsoft's Virtuozzo that was subsequently open-sourced as OpenVZ. For Amazon SES, DJB's qmail made it possible to send a ridiculous amount of subscription emails very efficiently, too.

I've been using a VPS powered by Virtuozzo since like 2002 or 2003, how is EC2 all that different? Just the API?

Per https://en.wikipedia.org/wiki/Virtuozzo_(company), SWsoft was founded in 1997, and publicly released Virtuozzo in 2000.

Per https://en.wikipedia.org/wiki/FreeBSD_jail, FreeBSD jail was committed into FreeBSD in 1999 "after some period of production use by a hosting provider", and released with FreeBSD 4.0 in 2000.

Per https://en.wikipedia.org/wiki/Qmail, qmail was released in 1998.

Today, lots of AWS services are basically just re-packaged OSS packages.

[adastra22]

EC2 services aren't tied to a machine, just a region. The details of what machine to instantiate a VM on, or the details of moving a VM between hosts, attaching remote drives over IP, or handling the networking that makes this all possible, that was worked out by Amazon to host Amazon.com, which they then resold as a service under the banner AWS. The pieces were there, but not a unified "cloud" architecture.

This is smelling like the classic "Dropbox isn't anything new" HN comment.

TODAY amazon services are just re-packaged OSS packages, yes. That wasn't the case before.

[cnst]

Why use any AWS at all when the other providers offer a cheaper product with better service?