Anyone here actually using EC2-classic? If so, what has been the reason for not upgrading?
Small company, legacy systems, priorities lie elsewhere. That's pretty much it.
Amazon EC2-Classic Is Retiring
71–80 of 155 posts
Re: Amazon EC2-Classic Is Retiring
#72Earlier quoted context omitted.
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.
This is a common error of conflating the name of something with a property that that name typically has.
The "RFC 1918 private range" is "private".
A publicly routeable range that is firewalled off is "private".
There is no practical difference in the level of privacy. There's a difference in naming only.
And of course, there is one other difference: The RFC1918 range is worse, because it can never be routed. You have no choice in the matter, it's not an option.
So you have two kinds of "private networking":
- Private by choice.
- Private with no choice.
Which do you prefer? To have choices, or to have those choices taken away from you?
Re: Amazon EC2-Classic Is Retiring
#73> 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…
[deleted]
Re: Amazon EC2-Classic Is Retiring
#74Earlier 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 :)
My favorite similar mixup is ordinance vs ordnance. Though I suppose they're not mutually exclusive. I'm sure that printed copies of some bylaws are hefty enough to cause serious damage if you lob them at the enemy.
Re: Amazon EC2-Classic Is Retiring
#75Very interesting that mainframes were really only "dead" for about 10-15 years or so: [0] from the early/mid 90's to EC2 in 2006. Yes, the cloud if off-site, but I'm using mainframe in the sense of centralized non-desktop computing resources.
[0] Not that they were ever actually dead. There's mainframes around from decades ago, and HPC continued to be required for a variety of applications, specifically research. But in terms of day-to-day computation needs, things shifted from mainframes to desktops, and centralized systems tended to be servers dedicated to a specific purpose instead of general compute needs.
Re: Amazon EC2-Classic Is Retiring
#76Holy 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.
GCP promises not to deprecate their service until at least the next monthly billing period. /s
Re: Amazon EC2-Classic Is Retiring
#77Earlier quoted context omitted.
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?
No, the retry logic was in-tandem between the client and a separate server endpoint.
Re: Amazon EC2-Classic Is Retiring
#78Disclaimer: I'm a Co-Founder of https://www.vantage.sh/
We just launched EC2 generational upgrades on Vantage that autodetects when there are chances for you to upgrade from older generation EC2 instances to get both cheaper costs and better performance.
You essentially get a summary of all your older generation EC2 instances that are candidates for upgrades and what the associated savings will be.
Very relevant with this news :)
Re: Amazon EC2-Classic Is Retiring
#79Anyone here actually using EC2-classic? If so, what has been the reason for not upgrading?
Hi, we have some customers left running things on our EC2 classic shard at Heroku. Mostly related to having dependence on customers doing things to migrate them cleanly.
How is that dependent on your customers – doesn't Heroku, like, fully abstract the EC2 backend so that the Heroku customer doesn't even have to know it's on EC2?
Re: Amazon EC2-Classic Is Retiring
#80Holy 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.
EC2 Classic was essentially deprecated back in 2013, whether it was said as such at the time or not. 8+ years is an incredibly long sunset period, especially compared to AWS’s competitors.
I know what you mean, but I don’t think it counts as a sunset period if they haven’t announced anything.