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

Amazon EC2-Classic Is Retiring

aws.amazon.com

Post reply on HN
Print view View original

21–30 of 155 posts

Re: Amazon EC2-Classic Is Retiring

#21

Post by mwcampbell »

res0nat0r wrote: post #13
paulddraper wrote: post #11

Hijaking this to say I hate VPC. I hate VPC. Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do. The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now. AWS makes me create a VPC, but I certainly don't set up some central-point-of-failure NAT or pay AWS to do it.

Are you talking about instances you want completely isolated with no public IP addresses and only RFC1918 IP's, but can reach out to the internet? Nat Gateway has been around for ~6 years now and is highly available and a managed service so you just need to click a couple of buttons. https://aws.amazon.com/about-aws/whats-new/2015/12/introduci...

At $0.045/hour, NAT gateways are expensive. This sets up perverse incentives, as it's cheaper to keep wasting public IPv4 addresses. If anyone from AWS is watching, I suggest that you make the base fixed price of NAT gateways way cheaper, and maybe add a small extra charge for EC2 instances and Fargate tasks with public IPs.

Re: Amazon EC2-Classic Is Retiring

#23

Post by 1123581321 »

paulddraper wrote: post #11

Hijaking this to say I hate VPC. I hate VPC. Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do. The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now. AWS makes me create a VPC, but I certainly don't set up some central-point-of-failure NAT or pay AWS to do it.

If VPC isn’t important to you, haven’t you made one catch-all VPC for your account a long time ago with good-enough general settings? It shouldn’t come up that often unless you are in a position to benefit from the feature.

Re: Amazon EC2-Classic Is Retiring

#24

Post by bgentry »

slownews45 wrote: post #16
ComputerGuru wrote: post #8

Earlier quoted context omitted.

You’re generally right but it’s definitely not a hard rule. Amazon/AWS has deprecated and then put to the grave multiple payment services. I made that same comment when SimpleDB was deprecated and someone said the same thing. More recently, torrent support in S3 is being killed off with little notice.

The thing has been that historically even though Amazon would "depreciate" a service they kept it running and supported. "Amazon SimpleDB (N. Virginia) Service is operating normally" is their current status page, but their marketing materials doesn't show any SDB stuff. So if you had some old workload ticking over - you could just leave it usually. I actually used SimpleDB in a light use case wildly past the point at…

FYI, "depreciate" != "deprecate" — I also used to think it was the former once upon a time :)

Re: Amazon EC2-Classic Is Retiring

#25

Post by rhacker »

paulddraper wrote: post #11

Hijaking this to say I hate VPC. I hate VPC. Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do. The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now. AWS makes me create a VPC, but I certainly don't set up some central-point-of-failure NAT or pay AWS to do it.

The fact that we have NATting is why you still have ipv4 addresses at all. Just look at the other thread about ipv6 that's going on in HN right now. Even if a small percent of a population doesn't have an IPv6 address means that no company can use it exclusively yet.

Re: Amazon EC2-Classic Is Retiring

#26

Post by lowbloodsugar »

paulddraper wrote: post #11

Hijaking this to say I hate VPC. I hate VPC. Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do. The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now. AWS makes me create a VPC, but I certainly don't set up some central-point-of-failure NAT or pay AWS to do it.

Why would you think its 1990s NAT? Launch an instance with a public IP and there's no central-point-of-failure. The "Internet Gateway" isn't an actual physical device.

Re: Amazon EC2-Classic Is Retiring

#27

Post by lowbloodsugar »

juliansimioni wrote: post #2

As someone who first used AWS in mid-2009 (just a few weeks before VPCs were announced!), but hasn't used an EC2 Classic enabled AWS account now since around 2012, it's hard to remember just how far the service has come. There were only a few instance types, and they were all slow and small (by todays standards). Everyone's EC2 instances were mostly publicly pingable/ssh-able from the internet. EBS was horribly horri…

I was in a tiny startup, but we could spin up a cluster of 250 c1.xlarge for $200 an hour! 2000 Cores!!!

Re: Amazon EC2-Classic Is Retiring

#28

Post by kstrauser »

kawsper wrote: post #22

Are classic loadbalancers going away, or are they just listed because they might be affected by EC2-Classic going away?

They don't seem to be going away. The linked document says:

> Option 4: Migrate manually to a Classic Load Balancer in a VPC

> The following information provides general instructions for manually creating a new Classic Load Balancer in a VPC based on a Classic Load Balancer in EC2-Classic. You can migrate using the AWS Management Console, the AWS CLI, or an AWS SDK. For more information, see Tutorial: Create a Classic Load Balancer in the User Guide for Classic Load Balancers.

Re: Amazon EC2-Classic Is Retiring

#29

Post by JoshTriplett »

I'm glad to see this.

Whenever I see this kind of deprecation at a company not normally known for deprecating things, I'd tend to guess it's being removed to make way for something else. I look forward to new network functionality being unlocked or optimized or simplified by not having to worry about how it interacts with non-VPCs.

Re: Amazon EC2-Classic Is Retiring

#30

Post by adrusi »

juliansimioni wrote: post #2

As someone who first used AWS in mid-2009 (just a few weeks before VPCs were announced!), but hasn't used an EC2 Classic enabled AWS account now since around 2012, it's hard to remember just how far the service has come. There were only a few instance types, and they were all slow and small (by todays standards). Everyone's EC2 instances were mostly publicly pingable/ssh-able from the internet. EBS was horribly horri…

I worked for AWS, specifically on a backend component specific to EC2 Classic, until late last year, and this will definitely simplify things on Amazon's end. There were, as of last year, still some large customers using Classic. It's not just a drop in the bucket compared to VPC, though definitely quite a bit smaller.
Post reply on HN