NEW - You can now accelerate your migration and modernization with AWS Transform. Read [Getting Started](https://docs.aws.amazon.com/transform/latest/userguide/getting-started.html) in the *AWS Transform User Guide*.

# Initializing AWS Application Migration Service with the API
Initializing with the API

In order to use AWS Application Migration Service (Application Migration Service), the service must first be initialized for any AWS Region in which you plan to use Application Migration Service.

You can initialize the service via the console or via the API.

During the initialization process:
+ The required IAM roles and policies will be created.
+ The required templates are configured.

You can initialize AWS Application Migration Service through the API. This option allows you to automate service initialization through a script when initializing multiple accounts.

You can also initialize Application Migration Service using the console. For more information, see [Initializing Application Migration Service with the console](mgn-initialize-console.md).

To initialize the service via the API, take the following steps:

1. Create the required IAM roles.

1. Create the replication template and launch template.
**Note**  
You must complete both steps to finalize the service initialization process.

## Creating the required IAM roles


To initialize Application Migration Service with the API, create the following IAM roles through the [IAM CreateRoleAPI](https://docs.aws.amazon.com/IAM/latest/APIReference/API_CreateRole.html). Learn more about [creating IAM roles in the AWS IAM documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html). Creation of each role must include the following parameters:


****  

| Role name | Trusted entities |  | **Principal** | **Action** | **Condition** | 
| --- | --- | --- | --- | --- | --- | 
|  **AWSApplicationMigrationReplicationServerRole**  | "ec2.amazonaws.com" | "sts:AssumeRole" | - | 
|  **AWSApplicationMigrationConversionServerRole**  | "ec2.amazonaws.com" | "sts:AssumeRole" | - | 
|  **AWSApplicationMigrationMGHRole**  | "mgn.amazonaws.com" | "sts:AssumeRole" | - | 
|  **AWSApplicationMigrationLaunchInstanceWithDrsRole**  | "ec2.amazonaws.com" | "sts:AssumeRole" | - | 
|  **AWSApplicationMigrationLaunchInstanceWithSsmRole**  | "ec2.amazonaws.com" | "sts:AssumeRole"  | - | 
|  **AWSApplicationMigrationAgentRole**  | "mgn.amazonaws.com" | ["sts:AssumeRole", "sts:SetSourceIdentity"] | \$1"StringLike": \$1"sts:SourceIdentity": "s-\$1", "aws:SourceAccount": "<SOURCE-ACCOUNT-ID>"\$1 | 

1. Attach Managed Policy** AWSApplicationMigrationReplicationServerPolicy** to Role **AWSApplicationMigrationReplicationServerRole**

1. Attach Managed Policy **AWSApplicationMigrationConversionServerPolicy **to Role **AWSApplicationMigrationConversionServerRole**

1. Attach Managed Policy** AWSApplicationMigrationMGHAccess** to Role **AWSApplicationMigrationMGHRole**

1. Attach Managed Policies** AmazonSSMManagedInstanceCore** and ** AWSElasticDisasterRecoveryEc2InstancePolicy** to Role **AWSApplicationMigrationLaunchInstanceWithDrsRole**

1. Attach Managed Policy** AmazonSSMManagedInstanceCore** to Role **AWSApplicationMigrationLaunchInstanceWithSsmRole**

1. Attach Managed Policy** AWSApplicationMigrationAgentPolicy\$1v2** to Role **AWSApplicationMigrationAgentRole**

Once the policies are attached to the roles, run the `aws mgn initialize-service` command. This will automatically create the service-linked role, create instance profiles, add Roles to Instance Profiles, and will finish service initialization. 

[Learn more about AWS Application Migration Service roles and managed policies](security-iam-awsmanpol.md).

## Creating the templates


To finalize the initialization process, you will need to [create the replication template](https://docs.aws.amazon.com/mgn/latest/APIReference/API_CreateReplicationConfigurationTemplate.html) and launch template by running the following commands:
+ `aws mgn create-replication-configuration-template`
+ `aws mgn create-launch-configuration-template`