Tag | Update (Review Required) - AMS Advanced Change Type Reference
Change Type DetailsAdditional InformationExecution Input ParametersExample: Required ParametersExample: All Parameters

Tag | Update (Review Required)

Add tags to, update tags on, or remove tags from, existing, supported, resources except those in AMS infrastructure stacks (stacks named mc-*). Tags simplify categorization, identification and targeting AWS resources. Use BulkUpdate if you have >50 tags to manage. For Autoscaling, EC2, Elastic Load Balancing, RDS resources and S3 buckets, use automated CT ct-0xqwmtn1hfh8u.

Full classification: Management | Advanced stack components | Tag | Update (review required)

Change Type Details

Change type ID

ct-0zko7t3rk2efb

Current version

2.0

Expected execution duration

240 minutes

AWS approval

Required

Customer approval

Not required if submitter

Execution mode

Manual

Additional Information

Update tags (review required)

Screenshot of this change type in the AMS console:

Update Resource Tags interface showing ID, execution mode, version, and description.

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.

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

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

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

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

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.

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

INLINE CREATE:

Issue the create RFC command with execution parameters provided inline (escape quotation marks 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 --title update-tags --change-type-id ct-0zko7t3rk2efb --change-type-version 2.0 --execution-parameters '{"Resources":[{"ResourceArn":"i-abcd1234","AddOrUpdateTags":[{"Key":"Name","Value":"app-instance-1"},{"Key":"Owner","Value":"Dep A"}],"RemoveTags":["Team","Prod"]},{"ResourceArn":"arn:aws:ec2:ap-southeast-2:123456789012:instance/i-019714a96c22f5452","AddOrUpdateTags":[{"Key":"Name","Value":"app-instance-1"},{"Key":"Owner","Value":"Dep A"}],"RemoveTags":["Team","Prod"]}]}'

TEMPLATE CREATE:

  1. Output the execution parameters JSON schema to a file in your current folder. This example names it TagUpdateParams.json.

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

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

    {
    "Resources": [
    {
      "ResourceArn": "i-abcd1234",
      "AddOrUpdateTags": [
        {
          "Key": "Name",
          "Value": "app-instance-1"
        },
        {
          "Key": "Owner",
          "Value": "Dep A"
        }
      ],
      "RemoveTags": [
        "Unused tag 1",
        "Unused tag 2"
      ]
    },
    {
      "ResourceArn": "arn:aws:ec2:ap-southeast-2:123456789012:instance/i-1234567890abcdef1",
      "AddOrUpdateTags": [
        {
          "Key": "Name",
          "Value": "app-instance-1"
        },
        {
          "Key": "Owner",
          "Value": "Dep A"
        }
      ],
      "RemoveTags": [
        "Unused tag 1",
        "Unused tag 2"
      ]
    }
  ]
}

  3. Output the RFC template to a file in your current folder; this example names it TagUpdateRfc.json:

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

  4. Modify and save the TagUpdateRfc.json file.

    The internal quotation marks in the ExecutionParameters JSON extension must be escaped with a backslash (\). Example without start and end time:

    {
"ChangeTypeVersion":    "2.0",
"ChangeTypeId":         "ct-0zko7t3rk2efb",
"Title":                "Update-Tags-RFC"
}

  5. Create the RFC:

    aws amscm create-rfc --cli-input-json file://TagUpdateRfc.json  --execution-parameters file://TagUpdateParams.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.

This is a "review required" change type (an AMS operator must review and run the CT), which means that the RFC can take longer to run and you might have to communicate with AMS through the RFC details page correspondance option. Additionally, if you schedule a "review required" change type RFC, be sure to allow at least 24 hours, if approval does not happen before the scheduled start time, the RFC is rejected automatically.

Execution Input Parameters

For detailed information about the execution input parameters, see Schema for Change Type ct-0zko7t3rk2efb.

Example: Required Parameters

Example not available.

Example: All Parameters

{
  "Resources": [
    {
      "ResourceArn": "arn:aws:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0",
      "AddOrUpdateTags": [
        {
          "Key": "k1",
          "Value": "v1"
        },
        {
          "Key": "k2",
          "Value": "v2"
        },
        {
          "Key": "k3",
          "Value": "v3"
        }
      ],
      "RemoveTags": ["k4", "k5", "k6"]
    },
    {
      "ResourceArn": "i-0fedcba0987654321",
      "AddOrUpdateTags": [
        {
          "Key": "k1",
          "Value": "v1"
        },
        {
          "Key": "k2",
          "Value": "v2"
        },
        {
          "Key": "k3",
          "Value": "v3"
        }
      ],
      "RemoveTags": ["k4", "k5", "k6"]
    }
  ],
  "Priority": "Medium"
}