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

51–60 of 155 posts

Re: Amazon EC2-Classic Is Retiring

#51

Post by psanford »

uluyol wrote: post #48
psanford wrote: post #32

Earlier quoted context omitted.

SimpleDB is still supported though. You can still make new SimpleDB domains. Thats part of what people love about AWS compared to Google Cloud. Google is quick to kill off services it finds no longer convenient for it to run. AWS has historically gone out of its way to keep old services running even as it releases new, better alternatives.

Any examples?

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

Re: Amazon EC2-Classic Is Retiring

#52

Post by slownews45 »

ComputerGuru wrote: post #40
slownews45 wrote: post #16

Earlier quoted context omitted.

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…

We were SOL when Amazon simple payments was killed off with very short notice and then again with FlexPay.

Good example - and goes to show how miserable it is when these folks kill stuff off.

Re: Amazon EC2-Classic Is Retiring

#53

Post by mandelbrotwurst »

bgentry wrote: post #24
slownews45 wrote: post #16

Earlier quoted context omitted.

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 :)

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

Re: Amazon EC2-Classic Is Retiring

#54

Post by staticassertion »

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 purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now.

You mean by nat'ing?

Re: Amazon EC2-Classic Is Retiring

#55

Post by temp_aws_mobile »

uluyol wrote: post #48
psanford wrote: post #32

Earlier quoted context omitted.

SimpleDB is still supported though. You can still make new SimpleDB domains. Thats part of what people love about AWS compared to Google Cloud. Google is quick to kill off services it finds no longer convenient for it to run. AWS has historically gone out of its way to keep old services running even as it releases new, better alternatives.

Any examples?

I work in the AWS Mobile org. The predecessor to our premier service, Amplify, was called Mobile Hub (https://aws.amazon.com/blogs/aws/aws-mobile-hub-build-test-a...). While I haven't personally worked on either service, I've heard and seen enough to know that they've taken customer obsession over keeping the lights on for any existing workloads farther than most reasonable businesses would. There is no sentiment of "force them to move to Amplify" in any conversations or design discussions, but rather "accommodate their existing workloads" as long as they exist.

Update: it looks like we're executing a migration plan this year by building seemingly-full parity between Mobile Hub and Amplify (https://docs.aws.amazon.com/aws-mobile/latest/developerguide...) such that "if you don't migrate your project to Amplify, your app will continue to function, and all your related cloud resources will continue to be available". This seems like a great solution for existing Mobile Hub customers.

Re: Amazon EC2-Classic Is Retiring

#56

Post by JMTQp8lwXL »

slownews45 wrote: post #5

Holy crap - is this one of the first actual depreciation and get off service things AWS has done? Kind of crazy honestly? They were kind of famous for NOT doing this sort of thing - at all. GCP just announced enterprise API's I see with some (pretty vague) promises about longevity.

Combining "enterprise" with "vague promise of longevity" is quite the oxymoron. Google should start celling cell service if they want to continue upleveling their doublespeak abilities.

Re: Amazon EC2-Classic Is Retiring

#58

Post by simfree »

JMTQp8lwXL wrote: post #56
slownews45 wrote: post #5

Holy crap - is this one of the first actual depreciation and get off service things AWS has done? Kind of crazy honestly? They were kind of famous for NOT doing this sort of thing - at all. GCP just announced enterprise API's I see with some (pretty vague) promises about longevity.

Combining "enterprise" with "vague promise of longevity" is quite the oxymoron. Google should start celling cell service if they want to continue upleveling their doublespeak abilities.

Google Fi already sells cell service, it's essentially T-Mobile service but without most domestic roaming and with higher prices than Mint, T-Mobile Connect and their other MVNOs.

From what I hear MMS stopped working a few months ago for iPhones on Google Fi.

Post reply on HN