Importing your data inventory

The Import feature allows you to easily import your inventory of servers, applications, and waves from a CSV file that is saved in your local disk or an S3 bucket.

Importing your data inventory from a local disk

To import your inventory from a local disk, take the following steps:

1. Select Import from the left-hand navigation menu (under Import and export) and you’ll be navigated to the Import inventory tab.

2. Select Import from local disk.

3. Click Choose file to choose the CSV file from your which you want to import the data.

4. Click Import.

Note

The file will also be automatically imported to an S3 bucket created by AWS MGN. It is highly recommended that you apply Amazon S3 bucket security practices where your CSV files are stored.

Importing your data inventory from an S3 bucket

To import your inventory from an S3 bucket, take the following steps:

1. Select Import from the left-hand navigation menu (under Import and export) and you’ll be navigated to the Import inventory tab.

2. Select Import from S3.

3. Click Browse to choose the Amazon S3 storage source from which you want to import the data.

4. Click Import.

Note

It is highly recommended that you apply Amazon S3 bucket security practices where your CSV files are stored.

Learn more about S3 permissions and policies.

Import history

Select the Import history tab to view the files imported in the last 7 days, including their status and the task’s start and end time.

You can change the settings according to your preferences by clicking on the settings icon located in the right-hand corner of the screen.

To see all the related task messages, click the task ID. To copy the messages, click Copy.

Required permissions

In order to use the import feature, you will need to create a role with the following policies (or any extension of them):

Managed policies:

• AWSApplicationMigrationFullAccess

• AWSApplicationMigrationEC2Access

Additional policies:

{
  "Sid":  "AllowS3Access",
   "Effect":  "Allow",
   "Action": [
     "s3:GetObject"
  ],
   "Resource":  "arn:aws:s3:::your-bucket/*"
}

When starting an import on an Amazon S3 bucket source that is owned by another account, ensure that the role or user has access to the Amazon S3 objects. When using the API, the Amazon S3 bucket owner parameter defaults to the current user’s account ID.

The following is an example of an S3 bucket policy in the target account:

{
  "Version":  "2012-10-17",
   "Statement": [
    {
       "Sid":  "ExampleStatement",
       "Effect":  "Allow",
       "Principal": {
         "AWS":  "arn:aws:iam::123456789012:user/Dave"
      },
       "Action": [
         "s3:GetObject"
      ],
       "Resource":  "arn:aws:s3:::awsexamplebucket1/*"
    }
  ]
}

Note

If the Amazon S3 objects are encrypted with SSE-KMS, ensure that the role or user initiating the import has access to decrypt using the AWS KMS key. This feature does not support SSE-C encrypted Amazon S3 objects.

Import parameters

The imported file can include multiple parameters, including:

• mgn:account-id – The ID of the account into which to import. This account must be managed by the calling account. Defaults to the calling account.

• mgn:app:description – The description of the application being imported.

• mgn:app:name – The name of the application being imported.

• mgn:app:tag:appkey1 – The value of the application tag key (in this example, the tag key is appkey1).

• mgn:launch:iam-instance-profile:name – The name of the instance profile associated with the launch instance.

• mgn:launch:instance-type – The EC2 instance type of the launch instance (for example, m4.large).

• mgn:launch:nic:0:network-interface-id – The ID of the network interface that appears first in the launch template ("0" refers to the first network interface, "1" would refer to the second network interface, and so on).

• mgn:launch:nic:0:private-ip:0 – The private IP that appears first in the network interface that appears first in the launch template.

• mgn:launch:nic:0:security-group-id:0 – The security group that appears first in the network interface that appears first in the launch template.

• mgn:launch:nic:0:subnet-id – The subnet ID that appears first in the network interface that appears first in the launch template.

• mgn:launch:placement:host-id – The host ID of the placement of the launch instance.

• mgn:launch:placement:tenancy – This tenancy of the launch instance.

• mgn:launch:tag:instance:key1 – The value of launch instance tag "key1" (in this example, the tag key is key1).

• mgn:launch:volume:/dev/sda:type – The type of the launch instance's volume whose name is /dev/sda (in this Linux machine example, the volume's name is /dev/sda; for a Windows machine, a typical volume name would be c:0).

  whose name is /dev/sda (in this example, the volume's name is /dev/sda).

• mgn:region – The AWS Region from which you are importing. Rows from other Regions will be ignored.

• mgn:server:fqdn-for-action-framework – The FQDN that the MGN connector uses to connect to the server.

• mgn:server:platform – The server’s platform (Linux or Windows).

• mgn:server:tag:serverkey1 – The value of the server tag key (in this example, the tag key is serverkey1).

• mgn:server:user-provided-id – The server's user-provided ID. The MGN connector uses this parameter when installing the AWS replication agent on the server.

• mgn:wave:description – The description of the imported wave.

• mgn:wave:name – The name of the imported wave.

• mgn:wave:tag:appkey1 – The value of the wave tag key (in this example, the tag key is appkey1).

Note

Currently, it is only possible to import into the Region being called.

Additional considerations

Please note the following considerations regarding the import parameters:

1. Server entries must include either the server IP address, or the FQDN.

2. If a row provides a property of a resource (e.g. mgn:wave:description is a property of a wave), then that row should also provide a parameter that identifies that resource (as explained in the following considerations).

3. If a resource's ID (mgn:server:id, mgn:app:id, or mgn:wave:id) is provided, the service will look for this resource in order to update it. If this resource is not found, the import will fail.

4. If a resource's ID is not provided, the service will look for a resource's alternative identification:

   • For an application: mgn:app:name

   • For a wave: mgn:wave:name

   • For a server: mgn:server:user-provided-id

5. If a resource's alternative identification exists in AWS MGN, the service will update this resource with new values (if applicable).

6. If a resource's alternative identification does not exist in AWS MGN, the service will create the resource.

7. 2 rows that refer to the same resource need not provide the same parameters for that resource, but they must not conflict. For example, if 2 rows provide the same mgn:wave:name, it is acceptable for one row to provide mgn:wave:description and for the other row to leave the value blank. However, the 2 rows must not provide conflicting values of mgn:wave:description.

Creating a CSV file in Microsoft Excel

When saving the CSV file in Microsoft Excel, ensure to save it in the MS-DOS CSV data format.