Migrating Workloads: Standard Process

Migration partner, Set Up:

1. The migration partner submits a Service Request to AMS for an IAM role for the purpose of migrating your instance. For details on submitting service requests, see Service Request Examples.

2. The migration partner submits a Admin Access Request. The AMS Operations team provides the migration partner access to your account through the requested IAM role.

Migration partner, Migrate Individual Workloads:

1. The migration partner migrates your non-AWS instance to a subnet in your AMS account through native Amazon EC2 or other migration tooling, with the customer-mc-ec2-instance-profile IAM instance profile (must be in the account).

2. The migration partner submits an RFC with the Deployment | Ingestion | Stack from migration partner migrated instance | Create CT (ct-257p9zjk14ija); for details on creating and submitting this RFC, see Workload Ingest Stack: Creating.

   The execution output of the RFC returns an instance ID, IP address, and AMI ID.

   The migration partner provides you with the instance ID of the workload created in your account.

You, Access and Validate the Migration:

1. Using the execution output provided you (AMI ID, instance ID, and IP address) by the migration partner, submit an access RFC and log into the newly-created AMS stack and verify that your application is working properly. For details, see Requesting Instance Access.

2. If satisfied, you can continue to use the launched instance as a 1-tier stack and/or use the AMI to create additional stacks, including Auto Scaling groups.

3. If not satisfied with the migration, file a service request and reference the stack and RFC IDs; AMS will work with you to address your concerns.