Choosing the replatforming environment
We recommend that you replatform an application in the AWS Cloud to use capabilities such as Amazon Elastic Block Store (Amazon EBS) snapshots or cloning an EC2 instance to create an AMI. These capabilities help your upgrading and testing process.
Typically, you start by rehosting the application to the AWS Cloud and then begin the replatforming process. However, you must be careful if you migrate applications that have vulnerabilities or run unsupported software and OSs. These applications could expose security vulnerabilities that are dangerous for your migration and future operations. Instead, we recommend using Application Migration Service to replicate the application components to a private subnet with limited egress. This approach isolates your workloads, and you can then securely replatform and test them before they are deployed to a production environment.
Your organization might have purchased extended OS support from an ISV, which extends OS
patching beyond the official EOS date for a period of three to five years. This is a temporary measure
and provides additional time to refactor or align your product upgrade or migration timelines with
a COTS application vendor's product release schedule. However, we recommend using AWS tools and expertise
from AWS Professional Services
