Go to Source servers list and click on the Hostname of your server.
On this page, by moving between tabs, you can:
Monitor progress of replication
Initially the progress bar will show 0%, but this will grow as the data is copied from your source server into target AWS environment. It will take ~30 mins for complete replication of this webserver.
Review retrieved information about the source server
Including recommended machine type when its started on AWS
You can always override this recommendation in Launch settings.
Manage tags applied to given replication (note that these are NOT tags applied to target server after the migration).
Manage staging disk settings
As per default replication settings, to save cost, Application Migration Service uses Standard HDD disks for data replication for volumes smaller than 500 GiB. You can change staging disk type on this tab.
Manage replication settings
On this tab you can configure custom replication settings for specific system. It may be useful especially for servers that experience significant amount of changes on their disks. In such case you may want to change the Replication Server instance type to one with more bandwidth and assign a dedicated Replication Server.
On this tab you can configure details of how EC2 instance of replicated system should be configured in AWS. We will disable automated right sizing and define expected configuration of the target EC2 machine.
Click Edit button in the General launch settings section.
On the Launch Settings page, change Instance type right sizing to None, then click Save settings. While rightsizing is a good idea since it allows to optimize cost, we will do it manually in EC2 Launch Template.
Modify EC2 Launch Template
Click on the Modify buton in the EC2 Launch Template section and confirm you want to Modify the launch template.
Review various options available at the Modify template (Create new version) page, by clicking on the Info link next to each section title.
When you’re done - scroll to the Instance type section and change selection to t3.micro machine instance type.
Then in the Resource tags section change the Name tag value to Webserver, like on the screenshot below.
Finally in the Network interfaces section, for the first Network interface, set Auto-assign public IP to Enable to make sure webserver will be accessible over public IP and select TargetVPC-public-a as the Subnet - this is where we want our webserver to run after the migration.
Scroll down and click Create template version button.
Update default EC2 Launch Template
In the Launch Templates screen go to the Versions tab and select the latest version by clicking on the radio box on the left.
From the Actions menu select Set default version
Go back to the Application Migration Service screen, click on Hostname of migrated server.
While waiting for the Data replication status to become Healthy (it should take ~30 mins) review parameters you can use for the agent installation, see how agent can be installed on Windows (if you plan to do Windows migration in the future) and additional information for instalation of agent on a secured network.
When the Data replication status is Healthy, your next step is to launch a test server.