|
Replace (July 29, 2021) – Added hyperlink to the Assist Automation Workflow doc & clarified hyperlink to AWS MGN pricing. Additionally up to date the checklist of really helpful occasion sorts to favor these constructed on AWS Nitro System, and added “Networking” to the title.
Let’s return to the summer time of 2006 and the launch of EC2. We began out with one occasion sort (the venerable m1.small), safety teams, and the venerable US East (N. Virginia) Area. The EC2-Traditional community mannequin was flat, with public IP addresses that had been assigned at launch time.
Our preliminary prospects noticed the worth instantly and began to place EC2 to make use of in many alternative methods. We hosted internet sites, supported the launch of Justin.TV, and helped Animoto to scale to a then-amazing 3400 situations when their Fb app went viral.
Among the early enhancements to EC2 targeted on networking. For instance, we added Elastic IP addresses in early 2008 in order that addresses could possibly be long-lived and related to totally different situations over time if obligatory. After that we added Auto Scaling, Load Balancing, and CloudWatch that will help you to construct extremely scalable functions.
Early prospects wished to attach their EC2 situations to their company networks, train further management over IP tackle ranges, and to assemble extra refined community topologies. We launched Amazon Digital Non-public Cloud in 2009, and in 2013 we made the VPC mannequin basically clear with Digital Non-public Clouds for Everybody.
Retiring EC2-Traditional Networking
EC2-Traditional has served us nicely, however we’re going to provide it a gold watch and a well-deserved sendoff! This put up will let you know what you have to know, what you have to do, and when you have to do it.
Earlier than I dive in, relaxation assured that we’re going to make this as easy and as non-disruptive as attainable. We’re not planning to disrupt any workloads and we’re supplying you with loads of lead time as a way to plan, take a look at, and carry out your migration. Along with this weblog put up, we now have instruments, documentation, and other people which might be all designed to assist.
Timing
We’re already notifying the remaining EC2-Traditional prospects by way of their account groups, and can quickly begin to situation notices within the Private Well being Dashboard. Listed here are the necessary dates on your calendar:
- All AWS accounts created after December four, 2013 are already VPC-only, until EC2-Traditional was enabled on account of a help request.
- On October 30, 2021 we are going to disable EC2-Traditional in Areas for AWS accounts that don’t have any energetic EC2-Traditional assets within the Area, as listed under. We may also cease promoting 1-year and Three-year Reserved Situations for EC2-Traditional.
- On August 15, 2022 we count on all migrations to be full, with no remaining EC2-Traditional assets current in any AWS account.
Once more, we don’t plan to disrupt any workloads and can do our greatest that will help you to satisfy these dates.
Affected Sources
With the intention to totally migrate from EC2-Traditional to VPC, you have to discover, study, and migrate the entire following assets:
In preparation on your migration, remember to learn Migrate from EC2-Traditional to a VPC.
You might have to create (or re-create, should you deleted it) the default VPC on your account. To learn to do that, learn Making a Default VPC.
In some circumstances it is possible for you to to switch the present assets; in others you have to to create new and equal assets in a VPC.
Discovering EC2-Traditional Sources
Use the EC2 Traditional Useful resource Finder script to seek out the entire EC2-Traditional assets in your account. You may run this immediately in a single AWS account, or you should use the included multi-account-wrapper to run it in opposition to every account of an AWS Group. The Useful resource Finder visits every AWS Area, appears to be like for particular assets, and generates a set of CSV recordsdata. Right here’s the primary a part of the output from my run:
The script takes a couple of minutes to run. I examine the checklist of CSV recordsdata to get a way of how a lot work I have to do:
After which I have a look inside to be taught extra:
Seems that I’ve some stopped OpsWorks Stacks that I can both migrate or delete:
Migration Instruments
Right here’s an outline of the migration instruments that you should use emigrate your AWS assets:
AWS Utility Migration Service (AWS MGN) – Use AWS MGN emigrate your situations and your databases from EC2-Traditional to VPC with minimal downtime. This service makes use of block-level replication and runs on a number of variations of Linux and Home windows (learn The way to Use the New AWS Utility Migration Service for Raise-and-Shift Migrations to be taught extra). The primary 90 days of replication are free for every server that you just migrate; see the AWS Utility Migration Service Pricing web page for extra info.
Assist Automation Workflow – The AWSSupport-MigrateEC2ClassicToVPC runbook helps easy, instance-level migration. It converts the supply occasion to an AMI, creates mirrors of the safety teams, and launches new situations within the vacation spot VPC. To be taught extra about this, learn How do I migrate an EC2-Traditional occasion to a VPC in similar Area of similar account?
After you’ve got migrated the entire assets inside a selected area, you may disable EC2-Traditional by making a help case. You are able to do this if you wish to keep away from by chance creating new EC2-Traditional assets within the area, however it’s undoubtedly not required.
Disabling EC2-Traditional in a area is meant to be a one-way door, however you may contact AWS Assist should you run it after which discover that you have to re-enable EC2-Traditional for a area. Make sure to run the Useful resource Finder that talked about earlier and just be sure you haven’t left any assets behind. These assets will proceed to run and to accrue fees even after the account standing has been modified.
IP Handle Migration – In case you are migrating an EC2 occasion and any Elastic IP addresses related to the occasion, you should use move-address-to-vpc then connect the Elastic IP to the migrated occasion. It will assist you to proceed to reference the occasion by the unique DNS identify.
Traditional Load Balancers – If you happen to plan emigrate a Traditional Load Balancer and have to protect the unique DNS names, please contact AWS Assist or your AWS account crew.
Updating Occasion Varieties
All the occasion sorts which might be accessible in EC2-Traditional are additionally accessible in VPC. Nevertheless, many more moderen occasion sorts can be found solely in VPC, and you might need to think about an replace as a part of your general migration plan. Right here’s a map to get you began (the * signifies that there are a number of situations with the identical identify prefix):
Depend on Us
My colleagues in AWS Assist are prepared that will help you along with your migration to VPC. I’m additionally planning to replace this put up with further info and different migration assets as quickly as they develop into accessible.
— Jeff;
