Live data from Hacker News

Farewell EC2-Classic, it’s been swell

allthingsdistributed.com

41–50 of 187 posts

Re: Farewell EC2-Classic, it’s been swell

#41
post #14

Earlier quoted context omitted.

It's not so much that EC2 Classic offered any features that were difficult to live without. It's just that migraine away from it means migrating, period. You need to move all of your systems, including any data stored on those systems (in instance store or EBS), to effectively a new data center. Migrating a live production environment can be a pain and/or cause downtime.

It's also worth remembering that infrastructure stuck on EC2 Classic would have been built so long ago it may predate modern cloud tooling and even modern best practices around reproducibility and CI/CD. (EC2 user since 2010)

Exactly - and with fewer managed services back then they’d also be more likely to have hand-rolled servers doing things which you’d now try to hand off to a managed service. I remember entire servers running small tasks which you’d now have, say, CloudFront or an ALB invoking Lambdas or at least sending it to a container.

Re: Farewell EC2-Classic, it’s been swell

#42
post #19

Earlier quoted context omitted.

It's not clear, but my interpretation is that they contacted every account holder, somehow convinced them to migrate (perhaps with discounts and/or threats of termination) and then shut down once everyone migrated. Would be very interesting to learn how that was possible, it seems surprising to me that there wasn't even one instance that the owner forgot about or just was unwilling to do any work on. It's possible th…

They don't need to threaten. Their SLAs don't offer to run VMs indefinitely. AWS will send you an email about shutting down your VM if, eg. they need to rotate the disk used for storing VM image etc. It's somewhere there in the contract, and it's a usual process for someone who keeps long-running VMs in EC2.

Do they really not do live migration or at least auto-restart (if configured) in those cases?

Re: Farewell EC2-Classic, it’s been swell

#43
post #8
post #4

This is something Google Cloud should learn from. It doesn't matter if product XX still makes money or fits in your business model. There are people who rely on it. And they'll remember if the vendor kept it running trouble free for years. They'll also remember if it was arbitrarily shut down or the price was suddenly increased by 4x and they had to spend many man hours migrating to another option. (Google maps api?)…

Google Reader. Never forget.

I see Reader as Google's attack on RSS' popularity. The product was killed off when its job was accomplished.

Re: Farewell EC2-Classic, it’s been swell

#45
post #4

This is something Google Cloud should learn from. It doesn't matter if product XX still makes money or fits in your business model. There are people who rely on it. And they'll remember if the vendor kept it running trouble free for years. They'll also remember if it was arbitrarily shut down or the price was suddenly increased by 4x and they had to spend many man hours migrating to another option. (Google maps api?)…

I agree with everything you wrote, except for the very last sentence. This is just wishful thinking. First of all "when the same person is responsible" is a very big if, and then no two buying decisions are the same and even if the person with decision-making power remembers it'll be just one point on a long list.

Re: Farewell EC2-Classic, it’s been swell

#46
Minor nitpick, 10.2.0.0/8 is not a valid subnet mask. The largest subnet you can make starting with 10.2.0.0 is 10.2.0.0/15. As far as I can tell everything was done in 10.0.0.0/8 but Amazon has took down EC2-Classic documentation.

https://web.archive.org/web/20150302235811/https://docs.aws....

Re: Farewell EC2-Classic, it’s been swell

#48

Ec2 classic was dirt simple. You basically were on a big public lan it felt like. If I remember right there were some issues with folks running scans / abuse originating inside AWS that felt like got a touch slow of a response - then at some point it all cleared up? I remember hardening internal systems as if the they were public which was a good practice even as vpc arrived. They might have gotten a default public i…

The public IPs were the big part: if you had the default 0.0.0.0/0 rule allowing SSH, you’d see brute force attacks within a few seconds of launching a new instance.

VPCs gave a little more room to prevent that but the big thing was really better tooling - the average developer still doesn’t think about security enough to be trusted with the EC2 or GCP launch wizard.

Re: Farewell EC2-Classic, it’s been swell

#49
post #4

This is something Google Cloud should learn from. It doesn't matter if product XX still makes money or fits in your business model. There are people who rely on it. And they'll remember if the vendor kept it running trouble free for years. They'll also remember if it was arbitrarily shut down or the price was suddenly increased by 4x and they had to spend many man hours migrating to another option. (Google maps api?)…

I agree with everything you wrote, except for the very last sentence. This is just wishful thinking. First of all "when the same person is responsible " is a very big if , and then no two buying decisions are the same and even if the person with decision-making power remembers it'll be just one point on a long list.

OTOH, I have a feeling that "nobody ever got fired for choosing AWS" will become the new "nobody ever got fired for buying IBM", so...

Re: Farewell EC2-Classic, it’s been swell

#50

So if I'm understanding correctly, all the classic instances were migrated to more modern types with no intervention from the account holder? Did they suffer a reboot during that migration, or was it done via some live-migration process (it's hard to live-migrate off a virtualization platform that was never designed with that in mind!). What about the original network setup? Is that still emulated, or might some cust…

No, migrating did involve intervention from the account holder. More information here: https://aws.amazon.com/blogs/aws/ec2-classic-is-retiring-her... It seems like AWS spent time, people and money to migrate customers off EC2 classic. They made a fairly good effort to automate the process and make it less painful for customers. For example: https://repost.aws/knowledge-center/ssm-migrate-ec2classic-v... The original…

Looking at that blog post, I think AWS could have done the migration for most users with no involvement of the user themselves.

In the ideal world, they would have written software to live-migrate VM's to the new platform and emulate the old networking.

Emulating old stuff should be pretty easy, because hardware moves on, and an instance back in 2006 probably had far lower performance expectations - and therefore even a fairly poor performance emulation will be sufficient to meet user needs.

Post reply on HN