Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Farewell EC2-Classic, it’s been swell

allthingsdistributed.com

Post reply on HN
Print view View original

51–60 of 187 posts

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

#51

Post by londons_explore »

motoboi wrote: post #15
londons_explore wrote: post #11

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…

The had to be restarted, but not only that, has to have their networks reconfigured. But they gave people YEARS to do that, and tracked down every user to help them if necessary.

> has to have their networks reconfigured.

I don't see why every user couldn't be auto-created a virtual network with the same 10.x.x.x IP addresses as their original machine had - and therefore there is no need to do any reconfiguration on the users side.

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

#52

Post by ilyt »

weinzierl wrote: post #45
keltex wrote: 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.

Sure but if you ask online and those people will be yelling "dont pick they will pull a rug from under you" at every occasion...

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

#53

Post by slyall »

voytec wrote: post #43
flir wrote: post #8

Earlier quoted context omitted.

Google Reader. Never forget.

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

No because if anything (the effect might have been small) it reduced the power of the open web and many websites (which Google tied togeather) and encouraged people to go to walled gardens ( Facebook, Instagram, twitter, etc ) which are controlled by other companies.

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

#54

Post by rob74 »

> 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.

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

#55

Post by brianshaler »

Off topic, but I'm confused about the IPv4 notation in this quote:

> When we launched EC2 in 2006, it was one giant network of 10.2.0.0/8.

In my understanding, /8 means the first octet would be fixed (10.0.0.0-10.255.255.255) and I'm having trouble understanding the significance of the 2 here. If the 2 is significant, wouldn't you write it as /16? Given the source and my confidence on this notation, I feel like there must be some meaning an expert can glean from this. If so, I'm curious to learn. If it's just a typo, then that's fine and I apologize if this is nit-picky.

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

#56

Post by AaronM »

skizm wrote: post #40

I haven't spun up anything in the cloud in a while. I used to dabble in both AWS and Digital Ocean. Usually went with DO because it seemed simpler and my projects were super small (and they had a lot of relevant guides to spinning up X, Y, and Z service on their systems). What is the difference between EC2-classic and whatever is available today? Are you still able to just get a linux box with a public IP address?

You have to create at minimum a vpc, internet gateway and at least one subnet/route table pointing to the igw

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

#57

Post by michelledepeil »

skizm wrote: post #40

I haven't spun up anything in the cloud in a while. I used to dabble in both AWS and Digital Ocean. Usually went with DO because it seemed simpler and my projects were super small (and they had a lot of relevant guides to spinning up X, Y, and Z service on their systems). What is the difference between EC2-classic and whatever is available today? Are you still able to just get a linux box with a public IP address?

Yes, but the reality is that EC2 is optimized for a target audience who wants to customize the deployment beyond a linux box with a public IP.

But iirc following the "Launch Instance" wizard and choosing defaults for everything, as well as a (default) public subnet gives the exact thing you're asking for.

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

#58

Post by acdha »

devit wrote: post #42
crabbone wrote: post #36

Earlier quoted context omitted.

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?

They have live migration now (for many years) but they didn’t back in the early era. I’m not sure they set it up for the classic environment but I think they must have - in the early 2010s you could get notices that your VM’s host had failed or was about to fail and you needed to launch a new one but I think that stopped by around 2015 as I had servers running for a deprecated project which were finally shutdown this decade and it seems like rather good luck not to have any failures in 7+ years on old hardware.

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

#59

Post by supazek »

anonymoushn wrote: post #47

I was overbilled for this service in 2011 and Amazon insists to this day that they do not have records about this even if I forward them the emails :)

I setup an AWS account in college before I had ever worked and dealt with enterprise security. Didn’t use the account for anything. No 2FA and a weak password and all of a sudden I have a $15,000 bill from a crypto mining script. Worked with Amazon, got everything cleaned up, turned on 2FA and was only charged $100. Pretty generous considering it was entirely my fault

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

#60

Post by [deleted] »

crabbone wrote: post #32
gnfargbl wrote: post #28

> one giant network of 10.2.0.0/8 Huh? Do they mean 10.0.0.0/8, or 10.2.0.0/16 (/15 would also work), or is this a new CIDR notation? Something specific to AWS, maybe?

Technically, it doesn't matter what number you stick after the first stop in a /8 network. Might as well write it as 10.X.X.X/8, it's all the same. I'm not sure where I've seen this done, but >90% certain some of the ip commands output this kind of CIDRs by simply concatenating the IP of the node you are querying and the size of the network.

[deleted]
Post reply on HN