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

61–70 of 155 posts

Re: Amazon EC2-Classic Is Retiring

#61

Post by giovannibonetti »

> 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 abstraction - instead of security groups - which is a low-level implementation detail.

Re: Amazon EC2-Classic Is Retiring

#62

Post by simfree »

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.

Sounds like a good reason to integrate with Authorize.net or another vendor that provides platform agnostic APIs that let you pick your own payment vendor (at much lower cost than Amazon's payment offerings).

Re: Amazon EC2-Classic Is Retiring

#63

Post by res0nat0r »

saurik wrote: post #41
arriu wrote: post #38

Anyone here actually using EC2-classic? If so, what has been the reason for not upgrading?

Six months ago I left the following comment about this. > I miss EC2 Classic :/. It always feels like the entire world of VPCs must have come from the armies of network engineers who felt like if the world didn't support all of the complexity they had designed to fix a problem EC2 no longer had--the tyranny of cables and hubs and devices acting as routers--that maybe they would be out of a job or something, and so ra…

Creating completely private networks in a public cloud, and also being able to link these networks across the WAN to other private networks in different regions seems the opposite of nothing to offer IMO.

Re: Amazon EC2-Classic Is Retiring

#64

Post by Alex3917 »

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.

> is this one of the first actual depreciation and get off service things AWS has done?

The transition from Amazon Linux to Amazon Linux 2 on Elastic Beanstalk was pretty rough. The migration took a full week, and there was really only a six month window where it could be done.

Re: Amazon EC2-Classic Is Retiring

#65

Post by ComputerGuru »

simfree wrote: post #62
ComputerGuru wrote: post #40

Earlier quoted context omitted.

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

Sounds like a good reason to integrate with Authorize.net or another vendor that provides platform agnostic APIs that let you pick your own payment vendor (at much lower cost than Amazon's payment offerings).

It was never our primary payment method, but we had higher conversion rates with it. We had Authorize.net at the time, then added PayPal PayFlow and Stripe. I actually authored a payment abstraction library that would try providers in order of priority and fall back gracefully, avoiding double charges and even abstracting over payment status, refunds, etc.

Re: Amazon EC2-Classic Is Retiring

#66

Post by ComputerGuru »

bpodgursky wrote: post #20
ComputerGuru wrote: post #7

Earlier quoted context omitted.

> This is pretty much the first time I've heard of AWS really deprecating something Amazon has deprecated and then put to the grave multiple payment services. Torrent support in S3 is being killed off with little notice.

As discussed on that thread, nobody used S3 torrents.

I can assure you that is not true. Not enough people used it, but it was not unused.

Re: Amazon EC2-Classic Is Retiring

#67

Post by ComputerGuru »

duskwuff wrote: post #19
ComputerGuru wrote: post #7

Earlier quoted context omitted.

> This is pretty much the first time I've heard of AWS really deprecating something Amazon has deprecated and then put to the grave multiple payment services. Torrent support in S3 is being killed off with little notice.

> Torrent support in S3 is being killed off with little notice. Did anyone ever seriously use it? It never made much sense to me -- if you're trying to optimize for performance, S3 is already pretty good and a CDN can make that even better; if you're trying to optimize for cost, you wouldn't be using S3 in the first place.

If you have a paid service that requires guaranteed delivery but want to offset a portion of the cost, it made sense. The problem is that BitTorrent is not trivial to integrate into non-torrent applications.

Re: Amazon EC2-Classic Is Retiring

#68

Post by flatiron »

Alex3917 wrote: post #64
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.

> is this one of the first actual depreciation and get off service things AWS has done? The transition from Amazon Linux to Amazon Linux 2 on Elastic Beanstalk was pretty rough. The migration took a full week, and there was really only a six month window where it could be done.

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

Re: Amazon EC2-Classic Is Retiring

#69

Post by [deleted] »

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.

[deleted]

Re: Amazon EC2-Classic Is Retiring

#70

Post by jsjohnst »

ComputerGuru wrote: post #65
simfree wrote: post #62

Earlier quoted context omitted.

Sounds like a good reason to integrate with Authorize.net or another vendor that provides platform agnostic APIs that let you pick your own payment vendor (at much lower cost than Amazon's payment offerings).

It was never our primary payment method, but we had higher conversion rates with it. We had Authorize.net at the time, then added PayPal PayFlow and Stripe. I actually authored a payment abstraction library that would try providers in order of priority and fall back gracefully, avoiding double charges and even abstracting over payment status, refunds, etc.

> I actually authored a payment abstraction library that would try providers in order of priority

Were you storing PANs then?

Post reply on HN