AMS Workload Ingest (WIGS)

To check the change type version, use this command:

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

You can use the AMS CLI to create an AMS instance from a non-AMS instance migrated to an AMS account.

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

2. 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"
   }

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

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

4. 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"
   }

5. 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.

6. 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.