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

131–140 of 155 posts

Re: Amazon EC2-Classic Is Retiring

#131

Post by kesor »

dragonwriter wrote: post #39
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…

> This is pretty much the first time I've heard of AWS really deprecating something Amazon has deprecated several things, they tend not to actually retire them (just reduce thei public profile so people aren't tempted to build new instances, while supporting the existing users indefinitely.)

Yep, SimpleDB comes to mind. Released in 2009, last updated circa 2012. Since DynamoDB was released it has been very silent on the SimpleDB front.

Re: Amazon EC2-Classic Is Retiring

#132

Post by njonesuk »

giovannibonetti wrote: post #61

> In order to fully migrate from EC2-Classic to VPC... Whenever I read anything about networking on AWS, I feel glad by having switched to GCP. On Google Cloud, you can put a project into production without having to fumble with networking at all (off course, the options are there if you need it). I feel more productive by only having to split my cloud resources by projects - which is a high-level concept, and a good…

In AWS, accounts within an AWS Organization are roughly analogous to projects within GCP. Most organisations running AWS in production will have tens or hundreds of accounts managed within their Organization. Segregating by security groups hasn't been the recommended approach for years, for this reason amongst others.

The accounts and Organization model is a slightly clunkier abstraction than projects, but on the other hand the security boundaries between accounts are harder than those between projects, which has its benefits.

Re: Amazon EC2-Classic Is Retiring

#133

Post by res0nat0r »

ArchOversight wrote: post #99
res0nat0r wrote: post #83

Earlier quoted context omitted.

The default VPC setup in each region just has a two public subnet configuration by default. You boot up an EC2 instance and it has a public IP address reachable from the internet (if you open up the security group) and a private IP address. If you want a totally private subnet to put your back end app servers on so they are not routable from the world as an extra layer of safety, then you can do that too. Or, if you'…

> [...] route the traffic out of NAT Gateways. Which is AWS's way of printing money. Straight up, no lie. Instead with the advent of IPv6 and everything getting a publicly routable IP address anyway, you no longer can rely on a machine having a "private" IP address. I recently stood up infrastructure where each machine in the VPC got a public IPv4 and IPv6, and used security groups to set up permissions for what syst…

You don't need nat gateways and I suspect most folks don't use them or are even aware they exist. The default setup gives you hosts with public ips directly reachable over the public internet, and no nat gateways or fees required.

Re: Amazon EC2-Classic Is Retiring

#135

Post by res0nat0r »

jitl wrote: post #92
res0nat0r wrote: post #83

Earlier quoted context omitted.

The default VPC setup in each region just has a two public subnet configuration by default. You boot up an EC2 instance and it has a public IP address reachable from the internet (if you open up the security group) and a private IP address. If you want a totally private subnet to put your back end app servers on so they are not routable from the world as an extra layer of safety, then you can do that too. Or, if you'…

Every time you write “subnet” you’re affirming saurik’s original post about the (needless) complexity of network hardware administration being brought to the cloud.

Just because the network is virtual and in a data center you don't own doesn't mean standard networking principals go out the window, you still have to setup the network as you see fit.

Maybe folks are just annoyed at the complexity and want something more plug and play which is understandable. The default vpc usually is fine enough for most everyone out of the box.

Re: Amazon EC2-Classic Is Retiring

#136

Post by treesknees »

hn_throwaway_99 wrote: post #87
dragonwriter wrote: post #39

Earlier quoted context omitted.

> This is pretty much the first time I've heard of AWS really deprecating something Amazon has deprecated several things, they tend not to actually retire them (just reduce thei public profile so people aren't tempted to build new instances, while supporting the existing users indefinitely.)

By that metric, then, EC2-Classic has been for nearly 8 years. Accounts created after 2013 couldn't create classic instances.

>All AWS accounts created after December 4, 2013 are already VPC-only, unless EC2-Classic was enabled as a result of a support request.

By default. You could still request it to be enabled on your account by contacting support.

Re: Amazon EC2-Classic Is Retiring

#137

Post by psanford »

jedberg wrote: post #94
mikeocool wrote: post #6

Earlier quoted context omitted.

You can actually still use SimpleDB: https://aws.amazon.com/simpledb/

The documentation still exists, but you can't launch it anymore.

What? Yes you can. I know because I just created a new domain today.

Re: Amazon EC2-Classic Is Retiring

#138

Post by silicon2401 »

gautamdivgi wrote: post #107
silicon2401 wrote: post #86

Earlier quoted context omitted.

This was hilarious when I saw local businesses put up signs requiring masks due to local "ordnance". I had to wonder what kind of masks they expected us to have

insure vs ensure is another one I've commonly seen. As in "please insure that is complete".

Interestingly, I think this was correct or at least colloquially correct a few centuries ago. I've seen that spelling used in text from the 1700s and 1800s by educated people. Probably a holdover from before spelling got really standardized.

Re: Amazon EC2-Classic Is Retiring

#139

Post by psanford »

murgindrag wrote: post #130
uluyol wrote: post #48

Earlier quoted context omitted.

Any examples?

My family is on Google Apps free edition. Google has been doing it's best to make my life miserable. It recently killed Google Voice in the free edition, so my younger child can no longer get a phone number. With zero warning. I've been through this each time I've (tried) to use Google for anything critical, so I've stopped. I mentioned a family example since B2B would be confidential. But I can count at least a half…

GSuite is separate from Google Cloud.

Re: Amazon EC2-Classic Is Retiring

#140

Post by psanford »

jsnell wrote: post #114
psanford wrote: post #51

Earlier quoted context omitted.

I assume you mean on the Google Cloud side? Maybe start with https://steve-yegge.medium.com/dear-google-cloud-your-deprec...

The only concrete example of a sunset in the rant is support for Python 2.7 (released in 2010) in the gcloud CLI tool. Seems like a pretty bad place to start.

> I know I haven’t gone into a lot of specific details about GCP’s deprecations. I can tell you that virtually everything I’ve used, from networking (legacy to VPC) to storage (Cloud SQL v1 to v2) to Firebase (now Firestore with a totally different API) to App Engine (don’t even get me started) to Cloud Endpoints to… I dunno, everything, has forced me to rewrite it all after at most 2–3 years, and they never automate it for you, and often there is no documented migration path at all. It’s just crickets.
Post reply on HN