# Stack from Migration Partner Migrated Instance \$1 Create
<a name="deployment-ingestion-stack-from-migration-partner-migrated-instance-create"></a>

Migrate a running non-AMS instance into an AMS stack, in a given AMS-managed VPC and subnet. Must be an instance that was configured through a cloud migration service. Tags that exist on the instance to be migrated will be applied to the resources created in addition to tags requested in the RFC. Number of total tags between the instance to be migrated and the resources created cannot exceed fifty. Set a Name tag to give the EC2 instance, and AMI, names in the EC2 console. Please note that your RFC will be rejected if a tag on the instance to be migrated has the same key as a tag supplied in the RFC.

**Full classification:** Deployment \$1 Ingestion \$1 Stack from migration partner migrated instance \$1 Create

## Change Type Details
<a name="ct-257p9zjk14ija-DISc-table"></a>


****  

|  |  | 
| --- |--- |
| Change type ID | ct-257p9zjk14ija | 
| Current version | 3.0 | 
| Expected execution duration | 360 minutes | 
| AWS approval | Required | 
| Customer approval | Not required | 
| Execution mode | Automated | 

## Additional Information
<a name="deployment-ingestion-stack-from-migration-partner-migrated-instance-create-info"></a>

### Workload Ingest Stack: Creating
<a name="ex-workload-ingest-col"></a>

#### Migrating an instance to an AMS stack with the Console
<a name="wig-create-con"></a>

Screenshot of this change type in the AMS console:

![\[Instance migration details showing ID, execution mode, version, classification, and description.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiIngestStackFromPartMigStackCreateCT.png)


How it works:

1. Navigate to the **Create RFC** page: In the left navigation pane of the AMS console click **RFCs** to open the RFCs list page, and then click **Create RFC**.

1. Choose a popular change type (CT) in the default **Browse change types** view, or select a CT in the **Choose by category** view.
   + **Browse by change type**: You can click on a popular CT in the **Quick create** area to immediately open the **Run RFC** page. Note that you cannot choose an older CT version with quick create.

     To sort CTs, use the **All change types** area in either the **Card** or **Table** view. In either view, select a CT and then click **Create RFC** to open the **Run RFC** page. If applicable, a **Create with older version** option appears next to the **Create RFC** button.
   + **Choose by category**: Select a category, subcategory, item, and operation and the CT details box opens with an option to **Create with older version** if applicable. Click **Create RFC** to open the **Run RFC** page.

1. On the **Run RFC** page, open the CT name area to see the CT details box. A **Subject** is required (this is filled in for you if you choose your CT in the **Browse change types** view). Open the **Additional configuration** area to add information about the RFC.

   In the **Execution configuration** area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the **Additional configuration** area.

1. When finished, click **Run**. If there are no errors, the **RFC successfully created** page displays with the submitted RFC details, and the initial **Run output**. 

1. Open the **Run parameters** area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.

**Note**  
If the RFC is rejected, the execution output includes a link to Amazon CloudWatch logs. AMS Workload Ingest (WIGS) RFCs are rejected when requirements are not met; for example, if anti-virus software is detected on the instance. The CloudWatch logs will include information about the failed requirement and the actions to take for remediation.

#### Migrating an instance to an AMS stack with the CLI
<a name="wig-create-cli"></a>

How it works:

1. Use either the Inline Create (you issue a `create-rfc` command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the `create-rfc` command with the two files as input. Both methods are described here.

1. Submit the RFC: `aws amscm submit-rfc --rfc-id ID` command with the returned RFC ID.

   Monitor the RFC: `aws amscm get-rfc --rfc-id ID` command.

To check the change type version, use this command:

```
aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
```
**Note**  
You can use any `CreateRfc` parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, `--notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}"` to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the [AMS Change Management API Reference](https://docs.aws.amazon.com/managedservices/latest/ApiReference-cm/API_CreateRfc.html).

You can use the AMS CLI to create an AMS instance from a non-AMS instance migrated to an AMS account.
**Note**  
Be sure you have followed the prerequisites; see [Migrating Workloads: Prerequisites for Linux and Windows](https://docs.aws.amazon.com/managedservices/latest/appguide/ex-migrate-instance-prereqs.html).

To check the change type version, use this command:

```
aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
```

*INLINE CREATE*:

Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:

```
aws amscm create-rfc --change-type-id "ct-257p9zjk14ija" --change-type-version "2.0" --title "AMS-WIG-TEST-NO-ACTION" --execution-parameters "{\"InstanceId\":\"INSTANCE_ID\",\"TargetVpcId\":\"VPC_ID\",\"TargetSubnetId\":\"SUBNET_ID\",\"TargetInstanceType\":\"t2.large\",\"ApplyInstanceValidation\":true,\"Name\":\"WIG-TEST\",\"Description\":\"WIG-TEST\",\"EnforceIMDSV2\":\"false\"}"
```

*TEMPLATE CREATE*:

1. 0utput the execution parameters JSON schema for this change type to a file; example names it MigrateStackParams.json:

   ```
   aws amscm get-change-type-version --change-type-id "ct-257p9zjk14ija" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > MigrateStackParams.json
   ```

1. Modify and save the execution parameters JSON file. For example, you can replace the contents with something like this:

   ```
   {
   "InstanceId":          "MIGRATED_INSTANCE_ID",
   "TargetVpcId":         "VPC_ID",
   "TargetSubnetId":      "SUBNET_ID",
   "Name":                "Migrated-Stack",
   "Description":         "Create-Migrated-Stack",
   "EnforceIMDSV2":       "false"
   }
   ```

1. Output the RFC template JSON file; example names it MigrateStackRfc.json:

   ```
   aws amscm create-rfc --generate-cli-skeleton > MigrateStackRfc.json
   ```

1. Modify and save the MigrateStackRfc.json file. For example, you can replace the contents with something like this:

   ```
   {
   "ChangeTypeId":         "ct-257p9zjk14ija",
   "ChangeTypeVersion":    "2.0",
   "Title":                "Migrate-Stack-RFC"
   }
   ```

1. Create the RFC, specifying the MigrateStackRfc file and the MigrateStackParams file:

   ```
   aws amscm create-rfc --cli-input-json file://MigrateStackRfc.json  --execution-parameters file://MigrateStackParams.json
   ```

   You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.

   The new instance appears in the Instance list for the application owner's account for the relevant VPC.

1. Once the RFC completes successfully, notify the application owner so he or she can log into the new instance and verify that the workload is operational.

**Note**  
If the RFC is rejected, the execution output includes a link to Amazon CloudWatch logs. AMS Workload Ingest (WIGS) RFCs are rejected when requirements are not met; for example, if anti-virus software is detected on the instance. The CloudWatch logs will include information about the failed requirement and the actions to take for remediation.

#### Tips
<a name="ex-workload-ingest-tip"></a>

**Note**  
Be sure you have followed the prerequisites; see [Migrating Workloads: Prerequisites for Linux and Windows](https://docs.aws.amazon.com/managedservices/latest/appguide/ex-migrate-instance-prereqs.html).

**Note**  
If a tag on the instance being migrated has the same key as a tag supplied in the RFC, the RFC fails.

**Note**  
You can specify up to four Target IDs, Ports, and Availability Zones.

**Note**  
If the RFC is rejected, the execution output includes a link to Amazon CloudWatch logs. AMS Workload Ingest (WIGS) RFCs are rejected when requirements are not met; for example, if anti-virus software is detected on the instance. The CloudWatch logs will include information about the failed requirement and the actions to take for remediation.

**Note**  
If the RFC is rejected, the execution output includes a link to Amazon CloudWatch logs. AMS Workload Ingest (WIGS) RFCs are rejected when requirements are not met; for example, if anti-virus software is detected on the instance. The CloudWatch logs will include information about the failed requirement and the actions to take for remediation.



If needed, see [Workload ingestion (WIGS) failure](https://docs.aws.amazon.com/managedservices/latest/userguide/rfc-troubleshoot.html#rfc-valid-execute-wigs).

## Execution Input Parameters
<a name="deployment-ingestion-stack-from-migration-partner-migrated-instance-create-input"></a>

For detailed information about the execution input parameters, see [Schema for Change Type ct-257p9zjk14ija](schemas.md#ct-257p9zjk14ija-schema-section).

## Example: Required Parameters
<a name="deployment-ingestion-stack-from-migration-partner-migrated-instance-create-ex-min"></a>

```
Example not available.
```

## Example: All Parameters
<a name="deployment-ingestion-stack-from-migration-partner-migrated-instance-create-ex-max"></a>

```
{
  "InstanceId" : "i-1234567890abababa",
  "TargetVpcId" : "vpc-01234567890abcdef",
  "TargetSubnetId" : "subnet-12345678901234567",
  "TargetSecurityGroupIds": ["sg-01234567890abcdef", "sg-1234567890abcdef0"],
  "Name": "My Stack",
  "Description": "This is my stack",
  "TargetInstanceType": "t2.large",
  "ApplyInstanceValidation": true,
  "KmsKeyId": "arn:aws:kms:us-east-1:012345678910:key/a3ccc020-abcd-1234-8d69-2f060c3c1234",
  "EnforceIMDSV2": "true",
  "Tags": [
    {
      "Key": "key1",
      "Value": "value1"
    },
    {
      "Key": "key2",
      "Value": "value2"
    },
    {
      "Key": "key3",
      "Value": "value3"
    },
    {
      "Key": "key4",
      "Value": "value4"
    },
    {
      "Key": "key5",
      "Value": "value5"
    },
    {
      "Key": "key6",
      "Value": "value6"
    },
    {
      "Key": "key7",
      "Value": "value7"
    },
    {
      "Key": "key8",
      "Value": "value8"
    },
    {
      "Key": "key9",
      "Value": "value9"
    },
    {
      "Key": "key10",
      "Value": "value10"
    },
    {
      "Key": "key11",
      "Value": "value11"
    },
    {
      "Key": "key12",
      "Value": "value12"
    },
    {
      "Key": "key13",
      "Value": "value13"
    },
    {
      "Key": "key14",
      "Value": "value14"
    },
    {
      "Key": "key15",
      "Value": "value15"
    },
    {
      "Key": "key16",
      "Value": "value16"
    },
    {
      "Key": "key17",
      "Value": "value17"
    },
    {
      "Key": "key18",
      "Value": "value18"
    },
    {
      "Key": "key19",
      "Value": "value19"
    },
    {
      "Key": "key20",
      "Value": "value20"
    },
    {
      "Key": "key21",
      "Value": "value21"
    },
    {
      "Key": "key22",
      "Value": "value22"
    },
    {
      "Key": "key23",
      "Value": "value23"
    },
    {
      "Key": "key24",
      "Value": "value24"
    },
    {
      "Key": "key25",
      "Value": "value25"
    },
    {
      "Key": "key26",
      "Value": "value26"
    },
    {
      "Key": "key27",
      "Value": "value27"
    },
    {
      "Key": "key28",
      "Value": "value28"
    },
    {
      "Key": "key29",
      "Value": "value29"
    },
    {
      "Key": "key30",
      "Value": "value30"
    },
    {
      "Key": "key31",
      "Value": "value31"
    },
    {
      "Key": "key32",
      "Value": "value32"
    },
    {
      "Key": "key33",
      "Value": "value33"
    },
    {
      "Key": "key34",
      "Value": "value34"
    },
    {
      "Key": "key35",
      "Value": "value35"
    },
    {
      "Key": "key36",
      "Value": "value36"
    },
    {
      "Key": "key37",
      "Value": "value37"
    },
    {
      "Key": "key38",
      "Value": "value38"
    },
    {
      "Key": "key39",
      "Value": "value39"
    },
    {
      "Key": "key40",
      "Value": "value40"
    },
    {
      "Key": "key41",
      "Value": "value41"
    },
    {
      "Key": "key42",
      "Value": "value42"
    },
    {
      "Key": "key43",
      "Value": "value43"
    },
    {
      "Key": "key44",
      "Value": "value44"
    },
    {
      "Key": "key45",
      "Value": "value45"
    },
    {
      "Key": "key46",
      "Value": "value46"
    },
    {
      "Key": "key47",
      "Value": "value47"
    },
    {
      "Key": "key48",
      "Value": "value48"
    },
    {
      "Key": "key49",
      "Value": "value49"
    },
    {
      "Key": "key50",
      "Value": "value50"
    }
  ]
}
```