AWS EC2-Classic set for imminent retirement – here’s what you need to know
Amazon Web Services (AWS) has announced that it will soon be retiring EC2-Classic which was first introduced with the original release of Amazon EC2 back in 2006.
According to the cloud computing giant, EC2-Classic is an environment where “instances run in a single, flat network that you share with other customers”.
When EC2-Classic was introduced though, AWS’ first customers immediately saw its value and used it to host web sites, support the launch of Justin.TV and Animoto even used it to scale to 3,400 instances, which was impressive at the time, when the company’s Facebook app went viral.
AWS then launched Amazon Virtual Private Cloud in 2009 and in 2013, the company built on this by releasing Virtual Private Clouds for Everyone. AWS accounts created after December 2013 are already VPC-only unless EC2-Classic was enabled as a result of a support request and this should make its retirement a bit easier on the company’s customers.
According to a new blog post from AWS chief evangelist Jeff Barr, AWS is planning to make the retirement of EC2-Classic as “smooth and as non-disruptive as possible” for the company’s customers. As part of its plans, the company is giving customers plenty of lead time so that they can plan, test and perform their migrations.
Beginning on October 30 of this year, AWS will disable EC2-Classic in regions that have no active EC2-Classic resources. The company will also stop selling both 1-year and 3-year Reserved Instances for EC2-Classic.
AWS expects all migrations from EC2-Classic to VPC to be complete by August 15 of next year with no remaining EC2-Classic resources present in any AWS account. However, the company doesn’t plan to disrupt any of its customers’ workloads and will do its best to help them meet these dates.
For customers still running EC2-Classic instances, AWS has also released a guide detailing how to migrate from EC2-Classic to a VPC.