Do you know what is EC2–Classic?
If you don’t know then chances are you don’t have to worry about it. Unless you are initial AWS customers, you probably will not have heard of the term EC2–Classic. It dates back to year 2006 when EC2 was launched with instance type as m1.small. The current known VPC was not in existence and backed in date it was termed as EC2–Classic which was a flat network model, with public IP addresses that were assigned at launch time.
EC2–Classic did serve well at that time and turns out still in some corner of the world still running to-date. AWS announced it’s retirement in 2021 and briefed on ways to prepare for it (https://aws.amazon.com/blogs/
Even if you are still on EC2-Classic, there is nothing to worry about you can easily migrate to VPC. There are multiple options, we will recommend you the first one.
- Hire the top AWS Partner and Cloud Consultant
- Do it your self.
Below we have listed down some steps if you want to do it yourself.
- Login to your AWS Console.
- Navigate to Systems Manager.
- Goto Automation under Change Management from left sidebar.
- Click Execute automation button.
- Make sure you are in Owned by Amazon tab, in the Automation document search box, enter MigrateEC2Classic.
- Select the radio button for the AWSSupport-MigrateEC2ClassicToVPC document, and then choose Next.
- Under Input parameters, for InstanceId, enter your source EC2-Classic instance ID.
- For TargetInstanceType specify your instance ID.
- For MigrationType, select Test if you would like to test first.
- To perform actual migration CutOver for Migration Type.
- Click Execute.
Thats it, this is how you can migrate your stand-alone servers. In case you have a complicated infrastructure including security groups, ElasticIPs and/or Load balancers, it will be little bit tricky and time consuming.