[flagged]
Farewell EC2-Classic, it’s been swell
111–120 of 187 posts
Re: Farewell EC2-Classic, it’s been swell
#112Now all they need to do is actually allow a fixed budget instead of possible runaway credit card charges. Microsoft do it, and IIRC Google, so why not Amazon? I've been waiting for this for about 20 years too :D
Because it would make them less money and their customers aren't so price sensitive.
Re: Farewell EC2-Classic, it’s been swell
#113This 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 Cloud officially deprecated its EC2 Classic equivalent, legacy networks, years ago but they're still running just fine: https://cloud.google.com/vpc/docs/legacy
Re: Farewell EC2-Classic, it’s been swell
#114> The complexities of managing infrastructure, buying new hardware, upgrading software, replacing failed disks — had been abstracted away ...and replaced by the complexities of AWS. I mean, even in the pre-AWS days, it's not like you had to buy the hardware or replace the failed disks yourself, web hosters did that for you.
AWS doesn’t have to be complex if those aren’t your requirements, you can use something like Lightsail. If all you need is a VPS, get a VPS. (Though if that’s what you need, I personally like Hetzner more).
But AWS needs to be complex to handle the needs of huge organizations.
I will also point out that the AWS console EC2 launching interface has come such a long way. So much to the complexity is handled for you.
Re: Farewell EC2-Classic, it’s been swell
#115EC2-Classic was magical. It felt like we were finally living in the future: a world where software was in charge of networking, and all of the legacy cruft that came from having to build networks out of cable could be forgotten.
Rather than care about legacy IP "subnets", the cloud cared about "security groups", which were missing only a couple features (such as "hierarchy") to entirely replace the role of a subnet in traditional networking.
Having spent a lot of time working with EC2-Classic, it made network engineering fun and easy. The new "VPC" mechanism is demoralizing in its complexity, and doesn't seem to allow anything you couldn't express using security groups.
I've written about this before--in more detail or with more rhetoric, depending on my mood--but the big feeling I get from the transition from EC2-Classic was the frustration that comes when other people make something worse.
https://news.ycombinator.com/item?id=36829190
https://news.ycombinator.com/item?id=33569889
Re: Farewell EC2-Classic, it’s been swell
#116"Retiring services isn’t something we do at AWS. It’s quite rare." I read this while I was taking a break from working on an epic to migrate our stuff off of OpsWorks before it gets shut down in May.
and I, while dealing with the fallout of migrating something from AWS Data Pipeline (it entered "Maintenance Mode" and they removed console access earlier this year.)
Re: Farewell EC2-Classic, it’s been swell
#117> The complexities of managing infrastructure, buying new hardware, upgrading software, replacing failed disks — had been abstracted away ...and replaced by the complexities of AWS. I mean, even in the pre-AWS days, it's not like you had to buy the hardware or replace the failed disks yourself, web hosters did that for you.
> it's not like you had to buy the hardware or replace the failed disks yourself, web hosters did that for you.
That’s an oversimplification. Yes, you didn’t go into the data center and replace the disk yourself, but it was a very different process than what you get with AWS.
There are still plenty of web hosts that operate the old fashioned way if people want to use them. There is a reason people prefer services like AWS though.
Re: Farewell EC2-Classic, it’s been swell
#118Earlier quoted context omitted.
That's a good point. But I am curious how special this Classic offering was, compared to what came after. Would migration have been hard?
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.
[deleted]
Re: Farewell EC2-Classic, it’s been swell
#119Now all they need to do is actually allow a fixed budget instead of possible runaway credit card charges. Microsoft do it, and IIRC Google, so why not Amazon? I've been waiting for this for about 20 years too :D
It would kill the ecosystem of highly paid "cloud cost optimization" consultants who do little more than flip a few switches in the AWS console.
Re: Farewell EC2-Classic, it’s been swell
#120"Retiring services isn’t something we do at AWS. It’s quite rare." I read this while I was taking a break from working on an epic to migrate our stuff off of OpsWorks before it gets shut down in May.
That was jarring for me, I wasn't quite sure what the article wanted to say at first. Title "we're doing X", body "we don't do X here".