- Newest
- Most votes
- Most comments
After completing a migration using AWS Application Migration Service (MGN), it's important to perform post-migration cleanup to ensure optimal security and cost-efficiency. While there isn't a specific tool or script provided by AWS to clean up all leftovers from the migration process, there are several steps you can take to address this issue:
-
Uninstall the AWS Replication Agent: If you haven't already done so, you should uninstall the AWS Replication Agent from your migrated servers. This can be done through the AWS Application Migration Service Console by navigating to the Source servers page, selecting the server(s), and choosing "Disconnect from service" from the Actions menu.
-
Remove migration-related resources: AWS MGN creates various resources during the migration process that should be cleaned up after a successful migration. This includes:
- Terminating replication servers (EC2 instances) created by AWS MGN
- Deleting EBS volumes and snapshots created during the replication process
-
Clean up discovered data: If you used the Application Discovery Service as part of your migration process, you may need to remove discovered servers and applications from the Migration Hub.
-
Remove unnecessary files and folders: In your specific case, where you've found an old Python DLL in the replication folder, it's generally safe to delete such leftover files or folders after ensuring that your migrated application is running correctly. However, it's advisable to back up the file before deletion, just in case.
-
Review and update security groups and firewall rules: Ensure that any temporary security group rules or firewall configurations set up for the migration process are removed or updated as necessary.
-
Clean up test data and accounts: Remove any test data, databases, or accounts that were created for migration purposes.
By following these steps, you can effectively clean up most of the leftovers from the migration process. Always exercise caution when deleting files or resources, and ensure that your applications are functioning correctly after any cleanup activities.
Sources
Using service-linked roles for AWS Application Migration Service - Application Migration Service
Process perspective - AWS Prescriptive Guidance
Unlock Cloud Savings, A Rehost Migration Playbook (Part 3: Mobilize – Understand and Control Cloud Spend) | Migration & Modernization
Uninstalling the Agent - Application Migration Service
answered 2 years ago
Relevant content
asked 2 years ago
asked 3 years ago

After migration, you disconnect MGN replication instance. The cleanup is something you need to perform, ultimately, it's your application and AWS would not know. However, if you are coding the application, you can use Code Whisperer that can provide code to for the later version of Python.