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 3 days ago | parent | next [-]

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 3 days ago | parent | prev | next [-]

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

▲

throwaway81523 3 days ago | parent | next [-]

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

▲

whstl 3 days ago | parent | prev | next [-]

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 3 days ago | parent [-]

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 3 days ago \| parent \| next [-]
		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 3 days ago \| parent \| prev [-]
		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 3 days ago | parent | prev [-]

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

▲

S0y 3 days ago | parent | prev | next [-]

>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 3 days ago | parent [-]

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

▲

NewJazz 3 days ago | parent [-]

VMs were invented at AWS? Blob storage?

▲

adastra22 3 days ago | parent [-]

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 3 days ago | parent [-]

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 3 days ago | parent [-]

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 3 days ago | parent | next [-]

OK, so, you're saying migration and remote drives over IP is the secret sauce of AWS / EC2?

Per Wikipedia, live migration was added to OpenVZ in April 2006, one year after OpenVZ was open-sourced in 2005, five years after Virtuozzo was first released as a commercial product in 2000, 3 years after the company was started in 1997. Straight from Wikipedia. I would guess that prior to April 2006, live migration was already available as part of commercial Virtuozzo for quite a while, probably.

Not to mention Xen. Isn't it common knowledge that EC2 was powered first by Xen, then by Linux-KVM, switching in 2017? What exactly is their secret sauce, except for stealing OSS and not giving back?

https://en.wikipedia.org/wiki/Virtuozzo_(company)

https://en.wikipedia.org/wiki/OpenVZ#Checkpointing_and_live_...

https://en.wikipedia.org/wiki/Xen

https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine

https://www.theregister.co.uk/2017/11/07/aws_writes_new_kvm_...

---

Dropbox is a little different, but, even then, doesn't everyone simply use Google Drive today? What's so special about Dropbox in 2025?

Just look at Virtuozzo. Why did SWsoft/Parallels open-source it into OpenVZ? The decision makes no sense, wasn't Virtuozzo their whole product they were selling to the hosting providers?

The answer lies in the complexities of the kernel code. By open-sourcing the underlying technology, they're ensuring immediate compatibility with all upcoming kernel changes. Had they kept it in-house, it'd be a nightmare to continue to integrate it with each upcoming Linux release, riddling the technology with preventable bugs, and eventually losing to competitors, including Xen and Linux-KVM at the time. OpenVZ was extremely popular in the VPS community until just a few years ago, before we had more RAM than we known what to do with, before Linux-KVM replaced both Xen and OpenVZ in the majority of the hosting environments in the last 10 years as of 2025.

I do agree with the other commenter that you're just rewriting the history here. All of these EC2 clouds are simply repackaged OSS (Xen and then Linux-KVM in the case of AWS EC2). If Amazon had actually developed some truly unique kernel stuff, we'd see it OSS by now, because of the difficulty with maintaining those kinds of kernel forks locally. But we don't. Because they haven't.

▲

adastra22 2 days ago | parent [-]

You are failing to understand that the product is not the technology. The product is the interface. One of the products you listed had the “cloud” interface we are familiar with today.

	▲	darkwater 21 hours ago \| parent [-]
		The product AWS invented was selling it as a service to 3rd parties over the Internet. And that's it.

▲

supriyo-biswas 3 days ago | parent | prev [-]

This is such a blatant rewrite of history; as an example live migrations were a thing in Xen: https://docs.redhat.com/en/documentation/red_hat_enterprise_....

▲

whstl 3 days ago | parent | next [-]

Quoting myself from another post:

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

They also have near-zero knowledge on the history of the field.

▲

adastra22 2 days ago | parent | prev [-]

I didn’t realize Xen migrations were made available from a uniform web API accessible from remote tools and fully abstracted/automated at the cluster level.

You are focused on the details and missing entirely the point of my post.

	▲	cnst 2 days ago \| parent [-]
		What do you think was the purpose of FreeBSD jail, Virtuozzo and Xen? https://web.archive.org/web/20011204195446/http://www.sw-sof... https://web.archive.org/web/20011224040032/http://www.sw-sof... That's 2001, and Virtuozzo was already advertised supporting migrations. OpenVZ remained super popular for at least like 10 years after it was open-sourced as OpenVZ in 2005, well into 2015, at least. Primarily because it allowed over-provisioning of RAM and all the other resources, which wasn't possible in other environments without the memory balloon drivers and other issues. I imagine the major reason OpenVZ has declined in popularity is because nowadays memory is cheap enough that over-provisioning of RAM isn't that much of a selling point, and not being able to run your own kernel with processor-guaranteed virtualisation, is deemed too old-fashioned and less secure for true multitenancy than Linux-KVM, which has basically taken over the entire market, from both Xen and OpenVZ, and VMware, and everybody else. Even Amazon EC2 is based on Linux-KVM now, whereas previously it was based on Xen.

▲

cnst 3 days ago | parent | prev [-]

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