Amazon EC2-Classic Is Retiring

Post by paulddraper » Thu, Jul 29, 2021, 5:30 AM UTC

1123581321 wrote: post #23

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.

Post by unixhero » Thu, Jul 29, 2021, 7:04 AM UTC

adrusi wrote: post #30

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 by derN3rd » Thu, Jul 29, 2021, 7:27 AM UTC

jitl wrote: post #90

flatiron wrote: post #68

Earlier quoted context omitted.

EB is kinda a mixed bag. Is there much production on EB? It’s great for q&d stuff you don’t want to get into specifics but I couldn’t imagine explaining my architecture with a big “EB does what EB wants to do here” bubble

Notion (my employer) was 100% Elastic Beanstalk until about a month ago, now we’re 100% ECS. We migrated once our 1200 box cluster started stalling deploys randomly while saying everything was healthy in the API. At that many instances, the some pages in the dashboard would hang the browser. One bad day, it took like 18 hours from deploy attempt started to AWS resolving the situation by fiddling knobs on their side.…

Post by lillecarl » Thu, Jul 29, 2021, 7:35 AM UTC

notatoad wrote: post #96

mandelbrotwurst wrote: post #53

Earlier quoted context omitted.

One aspect of this mix-up that I enjoy is the fact that deprecating something causes its value to depreciate, by quite a lot!

not only can deprecate cause depreciation, it can be a synonym for depreciate (in the financial meaning). but depreciate can't be a synonym for deprecate (in the end-of-life meaning). just one of those fun things that gets thrown in to make sure nobody ever fully understands the english language.

Post by EwanToo » Thu, Jul 29, 2021, 8:10 AM UTC

unixhero wrote: post #113

adrusi wrote: post #30

Earlier quoted context omitted.

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.

What I don't understand, and perhaps you may help me understand; is what powers the backend of AWS? Mainframes?