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.<p>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 horribly slow (our DBAs set up a super convoluted RAID 0+1 configuration for our MySQL databases and even then we needed massive sharding to keep up with growth). EC2 instances were, in general, very unreliable (I recall something like 1 in 500 instances failing _per week_), and especially so in the leadup to Christmas (where the rumor was AWS kept the best instances for themselves).<p>This is pretty much the first time I've heard of AWS really deprecating something, so I have a feeling it will _hugely_ simplify things on their end. From reading the post I also get the idea that it won't be _that_ hard of an operation from their side. I bet few people (by AWS standards) are still using EC2 classic heavily.
Holy crap - is this one of the first actual depreciation and get off service things AWS has done?<p>Kind of crazy honestly? They were kind of famous for NOT doing this sort of thing - at all.<p>GCP just announced enterprise API's I see with some (pretty vague) promises about longevity.
> In order to fully migrate from EC2-Classic to VPC...<p>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).<p>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.
<i>In order to fully migrate from EC2-Classic to VPC, you need to find, examine, and migrate all of the following resources:</i><p><LIST OF AWS BILLIABLE RESOURCES><p>I'm not sure if this was unintentional or done as a tongue-in-check joke, but "you yourself must FIND what you're using in our services" indicates to me that they're fully aware of how hard it is to easily see what exactly you're paying for when using AWS.
I'm glad to see this.<p>Whenever I see this kind of deprecation at a company <i>not</i> normally known for deprecating things, I'd tend to guess it's being removed to make way for something else. I look forward to new network functionality being unlocked or optimized or simplified by not having to worry about how it interacts with non-VPCs.
A decade without interruption is better than most enterprise IT departments manage despite considerably higher costs. I still have a couple of instance which have been upgraded a number of times over the year but aren’t quite ready to turn off yet.
Disclaimer: I'm a Co-Founder of <a href="https://www.vantage.sh/" rel="nofollow">https://www.vantage.sh/</a><p>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.<p>You essentially get a summary of all your older generation EC2 instances that are candidates for upgrades and what the associated savings will be.<p>Very relevant with this news :)
Hijaking this to say I hate VPC. I hate VPC.<p>Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do.<p>The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now.<p>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.
Just think of all those people putting off ever migrating off EC2-Classic that now have to reboot databases that nobody knows or remembers how they were configured. The time has come. Good luck.
Very 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.<p>[0] Not that they were ever actually <i>dead</i>. 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 <i>servers</i> dedicated to a specific purpose instead of general compute needs.