How To Migrate a Server to AWS Cloud Services

Summary

This video walks viewers through the process of migrating a physical or virtual machine from on-premises to AWS using AWS's Application Migration Service. It covers the necessary requirements, such as installing .NET Framework 3.5 and configuring RDP ports, followed by step-by-step instructions on replicating servers, launching test instances, and performing final cutovers. The video also highlights important considerations like security groups, public IP allocation, and post-migration cleanup. It's a comprehensive guide for anyone looking to move their server workloads to AWS with practical tips for troubleshooting along the way.

Takeaways

• 😀 Ensure you have an AWS account and a physical or virtual server before starting the migration process.
• 😀 Update the source server and install .NET Framework 3.5 or above to meet the migration prerequisites.
• 😀 Open the RDP port on the firewall of the source server to enable remote access during migration.
• 😀 Use AWS's Application Migration Service to migrate the virtual or physical server to AWS.
• 😀 Install the migration agent on the source server to begin the replication of settings and disk information.
• 😀 Perform a reboot of the source server if there are issues with the agent installation or replication process.
• 😀 Test the migration by launching a test instance to ensure the server has migrated successfully.
• 😀 Once the test instance is running and accessible, verify the settings and ensure RDP access is possible.
• 😀 Modify launch settings, such as instance type, public IP assignment, and security group configuration before the cutover.
• 😀 After testing, finalize the migration by completing the cutover process and shutting down the source server.
• 😀 Clean up unnecessary resources like snapshots and security groups post-migration to finalize the process and ensure no extra costs.

Q & A

What is the main goal of the video?

The main goal of the video is to demonstrate how to migrate a physical or virtual machine from an on-premises setup to AWS using the AWS Application Migration Service.

What are the prerequisites for migrating a server to AWS?

The prerequisites include having an AWS account, a physical or virtual server to migrate, ensuring the server has all updates installed, installing .NET Framework 3.5 or above, and making sure the RDP port is open on the firewall of the source server.

What are the initial steps involved in the server migration process?

The initial steps include identifying the servers to migrate, installing the agent on the source server, replicating disk and settings information, and performing tests before the actual cutover.

What might cause the agent installation to fail, and how was it fixed?

The agent installation might fail due to not rebooting the server after updates or installing the .NET Framework. The fix was to reboot the server and retry the agent installation.

What is the purpose of the test instance during the migration?

The test instance allows users to verify that the server migration is successful and that the server is functioning as expected before the final cutover.

How do you verify that the migration process is successful?

To verify the migration, you should check that the test server is up and running, accessible via RDP, and that any changes made during the testing phase (like creating a test document) persist in the migrated instance.

What changes were made to the launch template before the cutover?

The changes included selecting the correct instance type (M5 large), configuring the subnet, modifying storage options to GP3, ensuring the instance would auto-assign a public IP, and setting termination behavior to 'stop' rather than 'terminate'.

What should you do after completing the migration and the cutover process?

After the cutover is complete, you should shut down the source server, remove any unnecessary snapshots, delete extra volumes, and ensure that the RDP port is closed on the source server. Additionally, verify that the final migrated server is working properly.

What security considerations should be taken during the migration?

You should ensure that the security groups for the migrated instance are configured properly, including enabling RDP access only from trusted IP addresses and removing any unnecessary public IP addresses after the migration.

What steps should you take once the migration is complete and the instance is running in AWS?

Once the migration is complete, ensure that the DNS settings point to the new AWS instance, shut down the source server, and remove any redundant resources like unused security groups and volumes to clean up the environment.