id
stringlengths 8
78
| source
stringclasses 743
values | chunk_id
int64 1
5.05k
| text
stringlengths 593
49.7k
|
|---|---|---|---|
ams-ct-469 | ams-ct.pdf | 469 | list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID Managed Landing Zone Version April 22, 2025 1641 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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: Note Run this change type from your Management account. 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-1yqy4frl5s8y8" --change-type-version "1.0" -- title "Delete StackSets Stack" --execution-parameters "{\"Name\": \"Stackset name\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it DeleteStacksetsStackParams.json: aws amscm get-change-type-version --change-type-id "ct-1yqy4frl5s8y8" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > DeleteStacksetsStackParams.json 2. Modify and save the DeleteStacksetsStackParams file. For example, you can replace the contents with something like this: { "Name": "Stackset name", Managed Landing Zone Version April 22, 2025 1642 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Region": "us-east-1", "Priority": "High" } 3. Output the RFC template JSON file to a file; this example names it DeleteStacksetsStackRfc.json: aws amscm create-rfc --generate-cli-skeleton > DeleteStacksetsStackRfc.json 4. Modify and save the DeleteStacksetsStackRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1yqy4frl5s8y8", "Title": "Delete StackSets Stack" } 5. Create the RFC, specifying the DeleteStacksetsStack Rfc file and the DeleteStacksetsStackParams file: aws amscm create-rfc --cli-input-json file://DeleteStacksetsStackRfc.json -- execution-parameters file://DeleteStacksetsStackParams.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. Tips • For AWS CloudFormation details, see Delete a stack set • For general AWS CloudFormation information on stack sets, see StackSets concepts • To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1yqy4frl5s8y8. Managed Landing Zone Version April 22, 2025 1643 AMS Advanced Change Type Reference AMS Advanced Change Type Details Example: Required Parameters { "Name": "test-stackset" } Example: All Parameters { "Name": "test-stackset", "Region": "us-east-1", "Priority": "High" } Management Account | Enable Developer Mode Enable Developer Mode for an existing application account. Note that, in Developer mode, you are responsible for monitoring infrastructure resources that are provisioned outside of the AMS change management process. Full classification: Management | Managed landing zone | Management account | Enable developer mode Change Type Details Change type ID ct-1opjmhuddw194 Current version 1.0 Expected execution duration 3600 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1644 AMS Advanced Change Type Reference Additional Information Enable Developer mode AMS Advanced Change Type Details Management account: Enabling Management account Developer mode with the console Screenshot of this change type in the AMS console: 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. Managed |
ams-ct-470 | ams-ct.pdf | 470 | 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. Managed Landing Zone Version April 22, 2025 1645 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Management account: Enabling Management account Developer mode with the CLI 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: Managed Landing Zone Version April 22, 2025 1646 AMS Advanced Change Type Reference AMS Advanced Change Type Details Note Run this change type from your Management account. 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-1opjmhuddw194" \ --change-type-version "1.0" --title "Enable developer mode" \ --execution-parameters "{\"ApplicationAccountId\": \"ACCOUNT_ID\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it EnableDevModeParams.json: aws amscm get-change-type-version --change-type-id "ct-1opjmhuddw194" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > EnableDevModeParams.json 2. Modify and save the EnableDevModeParams file. For example, you can replace the contents with something like this: { "ApplicationAccountId":"ACCOUNT_ID" } 3. Output the RFC template JSON file to a file; this example names it EnableDevModeRfc.json: aws amscm create-rfc --generate-cli-skeleton > EnableDevModeRfc.json 4. Modify and save the EnableDevModeRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-1opjmhuddw194", "ChangeTypeVersion": "1.0", Managed Landing Zone Version April 22, 2025 1647 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Title": "Enable developer mode" } 5. Create the RFC, specifying the EnableDevMode Rfc file and the EnableDevModeParams file: aws amscm create-rfc --cli-input-json file://EnableDevModeRfc.json --execution- parameters file://EnableDevModeParams.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. Tips To learn more about developer mode, see Developer mode. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1opjmhuddw194. Example: Required Parameters { "ApplicationAccountId": "123456789012" } Example: All Parameters Example not available. Management Account | Move Account To OU Move an account under an AWS organizational unit (OU) to a different OU. Full classification: Management | Managed landing zone | Management account | Move account to OU Change Type Details Change type ID ct-1vq0f289r36ay Managed Landing Zone Version April 22, 2025 1648 AMS Advanced Change Type Reference AMS Advanced Change Type Details Current version 1.0 Expected execution duration 3600 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Move account to OU Moving an account to a different OU with the console Screenshot of this change type in the AMS console: 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 |
ams-ct-471 | ams-ct.pdf | 471 | 22, 2025 1648 AMS Advanced Change Type Reference AMS Advanced Change Type Details Current version 1.0 Expected execution duration 3600 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Move account to OU Moving an account to a different OU with the console Screenshot of this change type in the AMS console: 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. Managed Landing Zone Version April 22, 2025 1649 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Moving an account to a different OU with the CLI 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 Managed Landing Zone Version April 22, 2025 1650 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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: Note Run this change type from your Management account. 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-1vq0f289r36ay" \ --change-type-version "1.0" --title "Move Account To OU" \ --execution-parameters "{ \"AccountId\": \"ACCOUNT_ID\", \"TargetOUPath\": \"applications:managed:OU1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it MvAcctToOuParams.json: aws amscm get-change-type-version --change-type-id "ct-1vq0f289r36ay" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > MvAcctToOuParams.json 2. Modify and save the MvAcctToOuParams file. For example, you can replace the contents with something like this: { "AccountId": "ACCOUNT_ID", "TargetOUPath": "applications:managed:OU1", } 3. Output the RFC template JSON file to a file; this example names it MvAcctToOuRfc.json: Managed Landing Zone Version April 22, 2025 1651 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --generate-cli-skeleton > MvAcctToOuRfc.json 4. Modify and save the MvAcctToOuRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1vq0f289r36ay", "Title": "Move-Acct-To-OU-RFC" } 5. Create the RFC, specifying the MvAcctToOuRfc file and the MvAcctToOuParams file: aws amscm create-rfc --cli-input-json file://MvAcctToOuRfc.json --execution- parameters file://MvAcctToOuParams.json You receive the ID of the new RFC in the response |
ams-ct-472 | ams-ct.pdf | 472 | "ACCOUNT_ID", "TargetOUPath": "applications:managed:OU1", } 3. Output the RFC template JSON file to a file; this example names it MvAcctToOuRfc.json: Managed Landing Zone Version April 22, 2025 1651 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --generate-cli-skeleton > MvAcctToOuRfc.json 4. Modify and save the MvAcctToOuRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1vq0f289r36ay", "Title": "Move-Acct-To-OU-RFC" } 5. Create the RFC, specifying the MvAcctToOuRfc file and the MvAcctToOuParams file: aws amscm create-rfc --cli-input-json file://MvAcctToOuRfc.json --execution- parameters file://MvAcctToOuParams.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. Tips Note When moving accounts between OUs having custom SCPs, functionality may break due to SCPs being applied or a security posture compromised due to SCPs being removed. When moving accounts from an OU having a custom stackset (with CloudFormation auto-deployment feature enabled (see Manage automatic deployments for a stack set with service-managed permissions, to an OU which does not have this stackset, AWS CloudFormation would remove the stackset instance from the account. This may cause functionality loss. Vice versa, you should be aware of the addition of unwanted stackset instances when moving to a new OU. When an account is moved, it may no longer have access to resources specified by OU based policy conditions (aws:PrincipalOrgID) in IAM/S3, (see AWS global condition context keys. To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Managed Landing Zone Version April 22, 2025 1652 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1vq0f289r36ay. Example: Required Parameters { "AccountId": "123456789012", "TargetOUPath": "applications:development" } Example: All Parameters Example not available. Management Account | Offboard Application Account Offboard the specified application account. Run this from the management account for the application account that you want offboarded. You must first confirm the offboarding request by submitting the Confirm offboarding CT (ct-2wlfo2jxj2rkj) from the application account. If you are offboarding a customer-managed account, then ct-2wlfo2jxj2rkj is not needed. After you successfully submit both CTs, AMS can't undo the offboarding, repurpose the account, or help you to remediate issues in the account. Full classification: Management | Managed landing zone | Management account | Offboard application account Change Type Details Change type ID ct-0vdiy51oyrhhm Current version 2.0 Expected execution duration 3600 minutes AWS approval Required Customer approval Not required Managed Landing Zone Version April 22, 2025 1653 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution mode Automated Additional Information Management account: Offboard Application account Important You have 48 hours to offboard the specified application account after successfully running the Confirm offboarding change type (ct-2wlfo2jxj2rkj). After 48 hours, the offboarding request fails and the process of confirming and then offboarding must be restarted. Management account: Offboarding an Application account with the Console Screenshot of this change type in the AMS console: 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. Managed Landing Zone Version April 22, 2025 1654 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-473 | ams-ct.pdf | 473 | 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. Management account: Offboarding an Application account with the CLI 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. Managed Landing Zone Version April 22, 2025 1655 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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: Note Run this change type from the Management account associated with the application account being offboarded. 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-0vdiy51oyrhhm" --change-type-version "2.0" --title "Run Offboarding" --execution-parameters "{\"AccountID\": \"000000000000\",\"AccountEmail\": \"email@amazon.com\",\"Confirmation\": \"confirm\", \"DeleteTransitGatewayAttachment\":true}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it RunAppAcctOffBParams.json: aws amscm get-change-type-version --change-type-id "ct-0vdiy51oyrhhm" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > RunAppAcctOffBParams.json Managed Landing Zone Version April 22, 2025 1656 AMS Advanced Change Type Reference AMS Advanced Change Type Details 2. Modify and save the RunAppAcctOffBParams file. For example, you can replace the contents with something like this: { "AccountID": "000000000000", "AccountEmail": "email@amazon.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment" : true } 3. Output the RFC template JSON file to a file; this example names it RunAppAcctOffBRfc.json: aws amscm create-rfc --generate-cli-skeleton > RunAppAcctOffBRfc.json 4. Modify and save the RunAppAcctOffBRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "2.0", "ChangeTypeId": "ct-0vdiy51oyrhhm", "Title": "Execute Offboarding" } 5. Create the RFC, specifying the RunAppAcctOffBRfc file and the RunAppAcctOffBParams file: aws amscm create-rfc --cli-input-json file://RunAppAcctOffBRfc.json -- execution-parameters file://RunAppAcctOffBParams.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. Tips • The first step to offboarding the AMS multi-account landing zone Application account is to submit the Confirm offboarding CT (ct-2wlfo2jxj2rkj) from the application account. Run this change type within 48 hours of successfully running the confirmation change type. • There is no prerequisite or confirmation CT for Customer Managed application accounts. Managed Landing Zone Version April 22, 2025 1657 AMS Advanced Change Type Reference AMS Advanced Change Type Details • Note that offboarding is irreversible. • If you intend to self-operate the account after offboarding from AMS, then make sure to specify DeleteTransitGatewayAttachment parameter as false to retain connectivity. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0vdiy51oyrhhm. Example: Required Parameters { "RequestType": "OffboardingExecution", "Parameters": { "AccountId": "000000000000", "AccountEmail": "example@email.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment": true } } Example: All Parameters { "RequestType": "OffboardingExecution", "Parameters": { "AccountId": "000000000000", "AccountEmail": "example@email.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment": true } } Management Account | Update StackSets Stack (Review Required) Update an existing AWS CloudFormation (CFN) StackSets stack to deploy, or to update, the instances of the stack. Full classification: Management | Managed landing zone | Management account | Update StackSets stack (review required) Managed Landing Zone Version April 22, 2025 1658 AMS Advanced Change Type |
ams-ct-474 | ams-ct.pdf | 474 | the execution input parameters, see Schema for Change Type ct-0vdiy51oyrhhm. Example: Required Parameters { "RequestType": "OffboardingExecution", "Parameters": { "AccountId": "000000000000", "AccountEmail": "example@email.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment": true } } Example: All Parameters { "RequestType": "OffboardingExecution", "Parameters": { "AccountId": "000000000000", "AccountEmail": "example@email.com", "Confirmation": "confirm", "DeleteTransitGatewayAttachment": true } } Management Account | Update StackSets Stack (Review Required) Update an existing AWS CloudFormation (CFN) StackSets stack to deploy, or to update, the instances of the stack. Full classification: Management | Managed landing zone | Management account | Update StackSets stack (review required) Managed Landing Zone Version April 22, 2025 1658 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Type Details Change type ID ct-1v9g9n30woc8h Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Update a Stacksets stack Updating a Stacksets stack with the console Screenshot of this change type in the AMS console: 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. Managed Landing Zone Version April 22, 2025 1659 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Updating a Stacksets stack with the CLI 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. Managed Landing Zone Version April 22, 2025 1660 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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: Note Run this change type from your Management account. 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-1v9g9n30woc8h" --change-type-version "1.0" --title "Update StackSets Stack" --execution-parameters "{\"Name\": \"Stackset name\", \"Region\": \"us-east-1\", \"OuId"\: \"ou-cccc-00000000\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it UpdateStacksetsStackParams.json: aws amscm get-change-type-version --change-type-id "ct-1v9g9n30woc8h" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > UpdateStacksetsStackParams.json Managed Landing Zone Version April 22, 2025 1661 AMS Advanced Change Type Reference AMS Advanced Change Type Details 2. Modify and save the UpdateStacksetsStackParams file. For |
ams-ct-475 | ams-ct.pdf | 475 | 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-1v9g9n30woc8h" --change-type-version "1.0" --title "Update StackSets Stack" --execution-parameters "{\"Name\": \"Stackset name\", \"Region\": \"us-east-1\", \"OuId"\: \"ou-cccc-00000000\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it UpdateStacksetsStackParams.json: aws amscm get-change-type-version --change-type-id "ct-1v9g9n30woc8h" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > UpdateStacksetsStackParams.json Managed Landing Zone Version April 22, 2025 1661 AMS Advanced Change Type Reference AMS Advanced Change Type Details 2. Modify and save the UpdateStacksetsStackParams file. For example, you can replace the contents with something like this: { "CloudFormationTemplate": "CFN Template", "CloudFormationTemplateS3Endpoint": "S3 link to the template", "Description": "Update Test-Stackset", "Name": "test-stackset", "OuId": ["ou-cccc-00000000"], "Region": "us-east-1", "Parameters": [ { "Name": "test-value", "Value": "test-value" } ], "Tags": [ { "Key": "key1", "Value": "value1" }, { "Key": "key2", "Value": "value2" } ], "Priority": "High" } 3. Output the RFC template JSON file to a file; this example names it UpdateStacksetsStackRfc.json: aws amscm create-rfc --generate-cli-skeleton > UpdateStacksetsStackRfc.json 4. Modify and save the UpdateStacksetsStackRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1v9g9n30woc8h", "Title": "Update StackSets Stack" } Managed Landing Zone Version April 22, 2025 1662 AMS Advanced Change Type Reference AMS Advanced Change Type Details 5. Create the RFC, specifying the UpdateStacksetsStack Rfc file and the UpdateStacksetsStackParams file: aws amscm create-rfc --cli-input-json file://UpdateStacksetsStackRfc.json -- execution-parameters file://UpdateStacksetsStackParams.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. Tips • For AWS CloudFormation details, see Create a stack set • For general AWS CloudFormation information on stack sets, see StackSets concepts • To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1v9g9n30woc8h. Example: Required Parameters { "Name": "test-stackset", "OuId": ["ou-cccc-00000000"], "Region": "us-east-1", "Priority": "High" } Example: All Parameters { "CloudFormationTemplate": "template", "CloudFormationTemplateS3Endpoint": "https://s3.amazonaws.com/cf- templates-33kj7hiuwdk9-us-east-1/2017261mYA-stm-dynamic-sqs-no-params- sept-2017.template", "Description": "AMSTestCT - Update Test-Stackset", "Name": "test-stackset", Managed Landing Zone Version April 22, 2025 1663 AMS Advanced Change Type Reference AMS Advanced Change Type Details "OuId": ["ou-cccc-00000000"], "Region": "us-east-1", "Parameters": [ { "Name": "test-value", "Value": "test-value" } ], "Tags": [ { "Key": "key1", "Value": "value1" }, { "Key": "key2", "Value": "value2" } ], "Priority": "High" } Networking Account | Associate TGW Attachment Associate transit gateway (TGW) attachment to the transit gateway (TGW) route table. Use this change type for multi-account landing zone (MALZ) in Networking account only. Full classification: Management | Managed landing zone | Networking account | Associate TGW attachment Change Type Details Change type ID ct-3nmhh0qr338q6 Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1664 AMS Advanced Change Type Reference Additional Information Associate TGW attachment Networking account: Associate a TGW attachment with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Managed Landing Zone Version April 22, 2025 1665 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-476 | ams-ct.pdf | 476 | 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. Managed Landing Zone Version April 22, 2025 1665 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Networking account: Associate a TGW attachment with the CLI 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. Managed Landing Zone Version April 22, 2025 1666 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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-3nmhh0qr338q6" --change-type-version "1.0" --title "Associate Transit Gateway Attachment" --execution-parameters "{\"DocumentName \": \"AWSManagedServices-AssociateTGWAttachment\",\"Region\": \"us-east-1\", \"Parameters\": {\"TransitGatewayAttachmentId\": [\"tgw-attach-0878cf82a40721d19\"], \"TransitGatewayRouteTableId\": [\"tgw-rtb-06ddc751c0c0c881c\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it AssociateTgwAttachmentParams.json: aws amscm get-change-type-version --change-type-id "ct-3nmhh0qr338q6" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > AssociateTgwAttachmentParams.json 2. Modify and save the AssociateTgwAttachmentParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-AssociateTGWAttachment", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } } 3. Output the RFC template JSON file to a file; this example names it AssociateTgwAttachmentRfc.json: aws amscm create-rfc --generate-cli-skeleton > AssociateTgwAttachmentRfc.json 4. Modify and save the AssociateTgwAttachmentRfc.json file. For example, you can replace the contents with something like this: Managed Landing Zone Version April 22, 2025 1667 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3nmhh0qr338q6", "Title": "Associate Transit Gateway Attachment" } 5. Create the RFC, specifying the AssociateTgwAttachmentRfc file and the AssociateTgwAttachmentParams file: aws amscm create-rfc --cli-input-json file://AssociateTgwAttachmentRfc.json -- execution-parameters file://AssociateTgwAttachmentParams.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. Tips Note This Change Type is only valid in Multi-account Landing Zone (MALZ) Networking accounts. To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3nmhh0qr338q6. Example: Required Parameters { "DocumentName": "AWSManagedServices-AssociateTGWAttachment", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } Managed Landing Zone Version April 22, 2025 1668 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Example: All Parameters { "DocumentName": "AWSManagedServices-AssociateTGWAttachment", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } } Networking Account | Disable TGW Propagation Disable the Transit Gateway (TGW) attachment from propagating routes to the TGW route table. For multi-account landing zone (MALZ), use this change type in the Network account only. Full classification: Management | Managed landing zone | Networking account | Disable TGW propagation Change Type Details Change type ID ct-2pxyajek47am2 Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1669 AMS Advanced Change Type Reference Additional Information Disable |
ams-ct-477 | ams-ct.pdf | 477 | { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } } Networking Account | Disable TGW Propagation Disable the Transit Gateway (TGW) attachment from propagating routes to the TGW route table. For multi-account landing zone (MALZ), use this change type in the Network account only. Full classification: Management | Managed landing zone | Networking account | Disable TGW propagation Change Type Details Change type ID ct-2pxyajek47am2 Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1669 AMS Advanced Change Type Reference Additional Information Disable TGW propagation Networking account: Disable TGW propagation with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Managed Landing Zone Version April 22, 2025 1670 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Networking account: Disable TGW propagation with the CLI 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. Managed Landing Zone Version April 22, 2025 1671 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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-2pxyajek47am2" --change-type-version "1.0" --title "Disable Transit Gateway Propagation" --execution-parameters "{\"DocumentName \": \"AWSManagedServices-DisableTGWRouteTablePropagation\",\"Region\": \"us-east-1\", \"Parameters\": {\"TransitGatewayAttachmentId\": [\"tgw-attach-01234567890abcdef\"], \"TransitGatewayRouteTableId\": [\"tgw-rtb-01234567890abcdef\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it TgwPropagationDisableParams.json: aws amscm get-change-type-version --change-type-id "ct-2pxyajek47am2" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TgwPropagationDisableParams.json 2. Modify and save the TgwPropagationDisableParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-DisableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } } 3. Output the RFC template JSON file to a file; this example names it TgwPropagationDisableRfc.json: aws amscm create-rfc --generate-cli-skeleton > TgwPropagationDisableRfc.json 4. Modify and save the TgwPropagationDisableRfc.json |
ams-ct-478 | ams-ct.pdf | 478 | \"us-east-1\", \"Parameters\": {\"TransitGatewayAttachmentId\": [\"tgw-attach-01234567890abcdef\"], \"TransitGatewayRouteTableId\": [\"tgw-rtb-01234567890abcdef\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it TgwPropagationDisableParams.json: aws amscm get-change-type-version --change-type-id "ct-2pxyajek47am2" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TgwPropagationDisableParams.json 2. Modify and save the TgwPropagationDisableParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-DisableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } } 3. Output the RFC template JSON file to a file; this example names it TgwPropagationDisableRfc.json: aws amscm create-rfc --generate-cli-skeleton > TgwPropagationDisableRfc.json 4. Modify and save the TgwPropagationDisableRfc.json file. For example, you can replace the contents with something like this: Managed Landing Zone Version April 22, 2025 1672 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-2pxyajek47am2", "Title": "Disable Transit Gateway Propagation" } 5. Create the RFC, specifying the TgwPropagationDisableRfc file and the TgwPropagationDisableParams file: aws amscm create-rfc --cli-input-json file://TgwPropagationDisableRfc.json -- execution-parameters file://TgwPropagationDisableParams.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. Tips Note This Change Type is only valid in Multi-account Landing Zone (MALZ) Networking accounts. To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2pxyajek47am2. Example: Required Parameters { "DocumentName": "AWSManagedServices-DisableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } Managed Landing Zone Version April 22, 2025 1673 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Example: All Parameters { "DocumentName": "AWSManagedServices-DisableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } } Networking Account | Disassociate TGW Attachment Disassociate transit gateway (TGW) attachment from the transit gateway (TGW) route table. Use this change type for multi-account landing zone (MALZ) in Networking account only. Full classification: Management | Managed landing zone | Networking account | Disassociate TGW attachment Change Type Details Change type ID ct-3jo8yccbin4it Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1674 AMS Advanced Change Type Reference Additional Information Disassociate TGW attachment Networking account: Disassociate a TGW attachment with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Managed Landing Zone Version April 22, 2025 1675 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Networking account: Disassociate a TGW attachment with the CLI 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) |
ams-ct-479 | ams-ct.pdf | 479 | 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. Networking account: Disassociate a TGW attachment with the CLI 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. Managed Landing Zone Version April 22, 2025 1676 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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-3jo8yccbin4it" --change-type-version "1.0" --title "Disassociate a TGW attachment" --execution-parameters "{\"DocumentName \": \"AWSManagedServices-CreateRouteInTGWRouteTable\",\"Region\": \"us-east-1\", \"Parameters\": {\"TransitGatewayAttachmentId\": [\"tgw-attach-0878cf82a40721d19\"], \"TransitGatewayRouteTableId\": [\"tgw-rtb-06ddc751c0c0c881c\"], \"Blackhole\": [\"false"], \"DestinationCidrBlock\": [\"10.0.0.0/24\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it DisassociateTgwAttachmentParams.json: aws amscm get-change-type-version --change-type-id "ct-3jo8yccbin4it" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > DisassociateTgwAttachmentParams.json 2. Modify and save the DisassociateTgwAttachmentParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-DisassociateTGWAttachment", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } } 3. Output the RFC template JSON file to a file; this example names it DisassociateTgwAttachmentRfc.json: aws amscm create-rfc --generate-cli-skeleton > DisassociateTgwAttachmentRfc.json 4. Modify and save the DisassociateTgwAttachmentRfc.json file. For example, you can replace the contents with something like this: Managed Landing Zone Version April 22, 2025 1677 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3jo8yccbin4it", "Title": "Disassociate a TGW attachment" }} 5. Create the RFC, specifying the DisassociateTgwAttachmentRfc file and the DisassociateTgwAttachmentParams file: aws amscm create-rfc --cli-input-json file://DisassociateTgwAttachmentRfc.json -- execution-parameters file://DisassociateTgwAttachmentParams.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. Tips Note This Change Type is only valid in Multi-account Landing Zone (MALZ) Networking accounts. To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3jo8yccbin4it. Example: Required Parameters { "DocumentName": "AWSManagedServices-DisassociateTGWAttachment", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } Managed Landing Zone Version April 22, 2025 1678 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Example: All Parameters { "DocumentName": "AWSManagedServices-DisassociateTGWAttachment", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ], "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ] } } Networking Account | Enable TGW Propagation Enable the Transit Gateway (TGW) attachment to propagate routes to the TGW route table. For multi-account landing zone (MALZ), use this change type in the Network account only. Full classification: Management | Managed landing zone | Networking account | Enable TGW propagation Change Type Details Change type ID ct-1f9hi4bephqa9 Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1679 AMS Advanced Change Type Reference Additional Information Enable TGW propagation Networking account: enable TGW propagation with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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 |
ams-ct-480 | ams-ct.pdf | 480 | Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Managed Landing Zone Version April 22, 2025 1680 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Networking account: Enable TGW propagation with the CLI 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. Managed Landing Zone Version April 22, 2025 1681 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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-1f9hi4bephqa9" --change-type-version "1.0" --title "Enable Transit Gateway Propagation" --execution-parameters "{\"DocumentName \": \"AWSManagedServices-EnableTGWRouteTablePropagation\",\"Region\": \"us-east-1\", \"Parameters\": {\"TransitGatewayAttachmentId\": [\"tgw-attach-01234567890abcdef\"], \"TransitGatewayRouteTableId\": [\"tgw-rtb-01234567890abcdef\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it TgwPropagationEnableParams.json: aws amscm get-change-type-version --change-type-id "ct-1f9hi4bephqa9" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TgwPropagationEnableParams.json 2. Modify and save the TgwPropagationEnableParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-EnableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } } 3. Output the RFC template JSON file to a file; this example names it TgwPropagationEnableRfc.json: aws amscm create-rfc --generate-cli-skeleton > TgwPropagationEnableRfc.json 4. Modify and save the TgwPropagationEnableRfc.json file. For example, you can replace the contents with something like this: Managed Landing Zone Version April 22, 2025 1682 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1f9hi4bephqa9", "Title": "Enable Transit Gateway Propagation" } 5. Create the RFC, specifying the TgwPropagationEnableRfc file and the TgwPropagationEnableParams file: aws amscm create-rfc --cli-input-json file://TgwPropagationEnableRfc.json -- execution-parameters file://TgwPropagationEnableParams.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. Tips Note This Change Type is only valid in Multi-account Landing Zone |
ams-ct-481 | ams-ct.pdf | 481 | something like this: Managed Landing Zone Version April 22, 2025 1682 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1f9hi4bephqa9", "Title": "Enable Transit Gateway Propagation" } 5. Create the RFC, specifying the TgwPropagationEnableRfc file and the TgwPropagationEnableParams file: aws amscm create-rfc --cli-input-json file://TgwPropagationEnableRfc.json -- execution-parameters file://TgwPropagationEnableParams.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. Tips Note This Change Type is only valid in Multi-account Landing Zone (MALZ) Networking accounts. To learn more about AMS multi-account landing zone, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1f9hi4bephqa9. Example: Required Parameters { "DocumentName": "AWSManagedServices-EnableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } Managed Landing Zone Version April 22, 2025 1683 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Example: All Parameters { "DocumentName": "AWSManagedServices-EnableTGWRouteTablePropagation", "Region": "us-east-1", "Parameters": { "TransitGatewayAttachmentId": [ "tgw-attach-01234567890abcdef" ], "TransitGatewayRouteTableId": [ "tgw-rtb-01234567890abcdef" ] } } Networking Account | Remove TGW Static Route Remove the specified TGW static route from the specified transit gateway (TGW) route table. Use this multi-account landing zone (MALZ) change type only in a Networking account. Full classification: Management | Managed landing zone | Networking account | Remove TGW static route Change Type Details Change type ID ct-0rmgrnr9w8mzh Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Managed Landing Zone Version April 22, 2025 1684 AMS Advanced Change Type Reference Additional Information Remove TGW static route Networking account: Remove a TGW static route with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Managed Landing Zone Version April 22, 2025 1685 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Networking account: Remove a TGW static route with the CLI 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 |
ams-ct-482 | ams-ct.pdf | 482 | 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. Managed Landing Zone Version April 22, 2025 1686 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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-0rmgrnr9w8mzh" --change-type-version "1.0" --title "Remove TGW Static Route" --execution-parameters "{\"DocumentName \": \"AWSManagedServices-RemoveRouteFromTGWRouteTable\",\"Region\": \"us-east-1\", \"Parameters\": {\"TransitGatewayRouteTableId\": \"tgw-rtb-06ddc751c0c0c881c\", \"DestinationCidrBlock\": \"10.16.1.0/24\"}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it RemoveTgwStaticRouteParams.json: aws amscm get-change-type-version --change-type-id "ct-0rmgrnr9w8mzh" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > RemoveTgwStaticRouteParams.json 2. Modify and save the RemoveTgwStaticRouteParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-RemoveRouteFromTGWRouteTable", "Region": "us-east-1", "Parameters": { "TransitGatewayRouteTableId": "tgw-rtb-06ddc751c0c0c881c", "DestinationCidrBlock": "10.16.1.0/24" } } 3. Output the RFC template JSON file to a file; this example names it RemoveTgwStaticRouteRfc.json: aws amscm create-rfc --generate-cli-skeleton > RemoveTgwStaticRouteRfc.json 4. Modify and save the RemoveTgwStaticRouteRfc.json file. For example, you can replace the contents with something like this: Managed Landing Zone Version April 22, 2025 1687 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-0rmgrnr9w8mzh", "Title": "Remove TGW Static Route" } 5. Create the RFC, specifying the RemoveTgwStaticRouteRfc file and the RemoveTgwStaticRouteParams file: aws amscm create-rfc --cli-input-json file://RemoveTgwStaticRouteRfc.json -- execution-parameters file://RemoveTgwStaticRouteParams.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. Tips Note This Change Type is only valid in Multi-account Landing Zone (MALZ) Networking accounts. To learn more about AMS multi-account landing zones, see AWS Managed Services (AMS) Now Offers Managed Landing Zones. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0rmgrnr9w8mzh. Example: Required Parameters { "DocumentName": "AWSManagedServices-RemoveRouteFromTGWRouteTable", "Region": "us-east-1", "Parameters": { "TransitGatewayRouteTableId": ["tgw-rtb-06ddc751c0c0c881c"], "DestinationCidrBlock": ["10.16.1.0/24"] } Managed Landing Zone Version April 22, 2025 1688 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Example: All Parameters { "DocumentName": "AWSManagedServices-RemoveRouteFromTGWRouteTable", "Region": "us-east-1", "Parameters": { "TransitGatewayRouteTableId": ["tgw-rtb-06ddc751c0c0c881c"], "DestinationCidrBlock": ["10.16.1.0/24"] } } Monitoring and Notification Subcategory Change Type Items and Operations in the Monitoring and Notification Subcategory • CloudWatch | Enable Non-Root Volumes Monitoring • GuardDuty IP Set | Delete (Review Required) • GuardDuty IP Set | Update (Review Required) • GuardDuty Threat Intel Set | Delete (Review Required) • GuardDuty Threat Intel Set | Update (Review Required) • SNS | Subscribe To DirectCustomerAlerts • SNS | Update (Review Required) • SQS | Update CloudWatch | Enable Non-Root Volumes Monitoring Enable monitoring on non-root volumes of an EC2 instance. Full classification: Management | Monitoring and notification | CloudWatch | Enable Non-Root Volumes Monitoring Change Type Details Change type ID ct-0erkoad6uyvvg Current version 1.0 Monitoring and Notification Version April 22, 2025 1689 AMS Advanced Change Type Reference AMS Advanced Change Type Details Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Enable CloudWatch non-root volumes monitoring Enabling CloudWatch non-root volume monitoring with the console The following shows this change type in the AMS console. 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. Monitoring and Notification Version April 22, 2025 |
ams-ct-483 | ams-ct.pdf | 483 | 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. Monitoring and Notification Version April 22, 2025 1690 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Enabling CloudWatch non-root volume monitoring with the CLI 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 Monitoring and Notification Version April 22, 2025 1691 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-0erkoad6uyvvg" --change-type-version "1.0" --title "Enable Non-Root Volumes Monitoring" --execution-parameters "{\"DocumentName \":\"AWSManagedServices-DeployNonRootVolumeMonitoring\",\"Region\":\"us-east-1\", \"Parameters\":{\"InstanceId\":[\"i-1234567890abcdef0\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file in your current folder; this example names it CwNonRootVolumeMonitoringParams.json: aws amscm get-change-type-version --change-type-id "ct-0erkoad6uyvvg" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CwNonRootVolumeMonitoringParams.json 2. Modify and save the CwNonRootVolumeMonitoringParams.json file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-DeployNonRootVolumeMonitoring", "Region": "us-east-1", "Parameters": { "InstanceId": [ "i-1234567890abcdef0" ] } } 3. Output the JSON template for CreateRfc to a file in your current folder; this example names it CwNonRootVolumeMonitoringRfc.json: Monitoring and Notification Version April 22, 2025 1692 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --generate-cli-skeleton > CwNonRootVolumeMonitoringRfc.json 4. Modify and save the CwNonRootVolumeMonitoringRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-0erkoad6uyvvg", "Title": "CW-NON-ROOT-VOL-MONITORING-RFC" } 5. Create the RFC, specifying the CwNonRootVolumeMonitoringRfc file and the execution parameters file: aws amscm create-rfc --cli-input-json file://CwNonRootVolumeMonitoringRfc.json -- execution-parameters file://CwNonRootVolumeMonitoringParams.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. Tips To learn more about CloudWatch, see Enable or disable detailed monitoring for your instances. The EC2 instance alart Non-root volume usage is DISABLED by default. If you require alert generation based on this alarm, then you must enable it using this RFC. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0erkoad6uyvvg. Example: Required Parameters { "DocumentName": "AWSManagedServices-DeployNonRootVolumeMonitoring", "Region": "us-east-1", "Parameters": { "InstanceId": [ Monitoring and Notification Version April |
ams-ct-484 | ams-ct.pdf | 484 | use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start. Tips To learn more about CloudWatch, see Enable or disable detailed monitoring for your instances. The EC2 instance alart Non-root volume usage is DISABLED by default. If you require alert generation based on this alarm, then you must enable it using this RFC. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0erkoad6uyvvg. Example: Required Parameters { "DocumentName": "AWSManagedServices-DeployNonRootVolumeMonitoring", "Region": "us-east-1", "Parameters": { "InstanceId": [ Monitoring and Notification Version April 22, 2025 1693 AMS Advanced Change Type Reference AMS Advanced Change Type Details "i-1234567890abcdef0" ] } } Example: All Parameters { "DocumentName": "AWSManagedServices-DeployNonRootVolumeMonitoring", "Region": "us-east-1", "Parameters": { "InstanceId": [ "i-1234567890abcdef0" ] } } GuardDuty IP Set | Delete (Review Required) Use to delete an Amazon GuardDuty IPSet instance which is a list of trusted IP addresses that have been whitelisted for highly secure communication with your AWS environment. Full classification: Management | Monitoring and notification | GuardDuty IP set | Delete (review required) Change Type Details Change type ID ct-1b8fudnqq7m8r Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Monitoring and Notification Version April 22, 2025 1694 AMS Advanced Change Type Reference Additional Information Delete GuardDuty IP set (review required) Deleting an IP set for GuardDuty (review required) with the console The following shows this change type in the AMS console. AMS Advanced Change Type Details 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. Monitoring and Notification Version April 22, 2025 1695 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Deleting an IP set for GuardDuty (review required) with the CLI 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. Monitoring and Notification Version April 22, 2025 1696 AMS Advanced Change Type Reference AMS Advanced Change Type Details INLINE CREATE: Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution |
ams-ct-485 | ams-ct.pdf | 485 | 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. Monitoring and Notification Version April 22, 2025 1696 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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-1b8fudnqq7m8r" --change-type- version "1.0" --title "Delete Amazon GuardDuty IP Set" --execution-parameters "{\"DetectorId\": \"00000000000000000000000000000000\", \"IpSetId\": \"00000000000000000000000000000000\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it DeleteGdIpSetParams.json. aws amscm get-change-type-version --change-type-id "ct-08avsj2e9mc7g" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > DeleteGdIpSetParams.json 2. Modify and save the DeleteGdIpSetParams file. For example, you can replace the contents with something like this: { "DetectorId": "00000000000000000000000000000000", "IpSetId": "00000000000000000000000000000000", "Region": "us-east-1" } 3. Output the RFC template JSON file to a file named DeleteGdIpSetRfc.json: aws amscm create-rfc --generate-cli-skeleton > DeleteGdIpSetRfc.json 4. Modify and save the DeleteGdIpSetRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-08avsj2e9mc7g", "Title": "DELETE_GD_IP_SET" } 5. Create the RFC, specifying the DeleteGdIpSetRfc Rfc file and the DeleteGdIpSetParams file: Monitoring and Notification Version April 22, 2025 1697 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --cli-input-json file://DeleteGdIpSetRfc.json --execution- parameters file://DeleteGdIpSetParams.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. Tips For more information about Amazon GuardDuty, see Amazon GuardDuty. 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-1b8fudnqq7m8r. Example: Required Parameters { "IpSetId": "0cb0141ab9fbde177613ab9436212e90", "Region": "us-east-1" } Example: All Parameters { "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "IpSetId": "0cb0141ab9fbde177613ab9436212e90", "Region": "us-east-1", "Priority": "Medium" } Monitoring and Notification Version April 22, 2025 1698 AMS Advanced Change Type Reference AMS Advanced Change Type Details GuardDuty IP Set | Update (Review Required) Use to update an Amazon GuardDuty IPSet instance which is a list of trusted IP addresses that have been whitelisted for highly secure communication with your AWS environment. Full classification: Management | Monitoring and notification | GuardDuty IP set | Update (review required) Change Type Details Change type ID ct-07jzw8bzd2on7 Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Update GuardDuty IP set (review required) Updating an IP set for GuardDuty (review required) with the console The following shows this change type in the AMS console. Monitoring and Notification Version April 22, 2025 1699 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-486 | ams-ct.pdf | 486 | 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. Updating an IP set for GuardDuty (review required) with the CLI 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. Monitoring and Notification Version April 22, 2025 1700 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 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-07jzw8bzd2on7" --change-type-version "1.0" --title "Update Amazon GuardDuty IP Set" --execution-parameters "{\"Activate\": true, \"DetectorId\": \"00000000000000000000000000000000\", \"Name\": \"trusted-ips\", \"IpSet\": \"https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key\", \"IpSetId \": \"00000000000000000000000000000000\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it UpdateGdIpSetParams.json. aws amscm get-change-type-version --change-type-id "ct-07jzw8bzd2on7" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > UpdateGdIpSetParams.json Monitoring and Notification Version April 22, 2025 1701 AMS Advanced Change Type Reference AMS Advanced Change Type Details 2. Modify and save the UpdateGdIpSetParams file. For example, you can replace the contents with something like this: { "Activate": true, "DetectorId": "00000000000000000000000000000000", "Name": "trusted-ips", "IpSet": "https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key", "IpSetId": "00000000000000000000000000000000", "Region": "us-east-1" } 3. Output the RFC template JSON file to a file named UpdateGdIpSetRfc.json: aws amscm create-rfc --generate-cli-skeleton > UpdateGdIpSetRfc.json 4. Modify and save the UpdateGdIpSetRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-07jzw8bzd2on7", "Title": "UPDATE_GD_IP_SET" } 5. Create the RFC, specifying the UpdateGdIpSet Rfc file and the UpdateGdIpSetParams file: aws amscm create-rfc --cli-input-json file://UpdateGdIpSetRfc.json --execution- parameters file://UpdateGdIpSetParams.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. Tips 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. Monitoring and Notification Version April 22, 2025 1702 AMS Advanced Change Type Reference AMS Advanced Change Type Details For more information about Amazon GuardDuty and creating IP sets, see Amazon GuardDuty and CreateIPSet. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-07jzw8bzd2on7. Example: Required Parameters { "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "IpSetId": "0cb0141ab9fbde177613ab9436212e90", "Region": "us-east-1" } Example: All Parameters { "Activate": true, "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "IpSet": "https://s3.amazonaws.com/guarddutylists/sample.txt", "IpSetId": "0cb0141ab9fbde177613ab9436212e90", "Name": "Sample IPSet", "Region": "us-east-1", "Priority": "Medium" } GuardDuty Threat Intel Set | Delete |
ams-ct-487 | ams-ct.pdf | 487 | does not happen before the scheduled start time, the RFC is rejected automatically. Monitoring and Notification Version April 22, 2025 1702 AMS Advanced Change Type Reference AMS Advanced Change Type Details For more information about Amazon GuardDuty and creating IP sets, see Amazon GuardDuty and CreateIPSet. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-07jzw8bzd2on7. Example: Required Parameters { "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "IpSetId": "0cb0141ab9fbde177613ab9436212e90", "Region": "us-east-1" } Example: All Parameters { "Activate": true, "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "IpSet": "https://s3.amazonaws.com/guarddutylists/sample.txt", "IpSetId": "0cb0141ab9fbde177613ab9436212e90", "Name": "Sample IPSet", "Region": "us-east-1", "Priority": "Medium" } GuardDuty Threat Intel Set | Delete (Review Required) Use to delete an Amazon GuardDuty ThreatIntelSet instance which is a list of known malicious IP addresses. Full classification: Management | Monitoring and notification | GuardDuty threat intel set | Delete (review required) Change Type Details Change type ID ct-2qjqju7h67s7w Monitoring and Notification Version April 22, 2025 1703 AMS Advanced Change Type Reference AMS Advanced Change Type Details Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Delete GuardDuty Threat intel set (review required) Deleting a Threat intel set for GuardDuty (review required) with the console The following shows this change type in the AMS console. 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. Monitoring and Notification Version April 22, 2025 1704 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Deleting a Threat intel set for GuardDuty (review required) with the CLI 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 Monitoring and Notification Version April 22, 2025 1705 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 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-2qjqju7h67s7w" --change-type-version "1.0" --title "Delete Amazon GuardDuty Threat Intel Set" --execution-parameters "{\"DetectorId\": \"00000000000000000000000000000000\", \"ThreatIntelSetId\": \"00000000000000000000000000000000\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output |
ams-ct-488 | ams-ct.pdf | 488 | 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 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-2qjqju7h67s7w" --change-type-version "1.0" --title "Delete Amazon GuardDuty Threat Intel Set" --execution-parameters "{\"DetectorId\": \"00000000000000000000000000000000\", \"ThreatIntelSetId\": \"00000000000000000000000000000000\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it DeleteGdThreatIntelSetParams.json. aws amscm get-change-type-version --change-type-id "ct-2qjqju7h67s7w" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > DeleteGdThreatIntelSetParams.json 2. Modify and save the DeleteGdThreatIntelSetParams file. For example, you can replace the contents with something like this: { "DetectorId": "00000000000000000000000000000000", "ThreatIntelSetId": "00000000000000000000000000000000", "Region": "us-east-1" } 3. Output the RFC template JSON file to a file named DeleteGdThreatIntelSetRfc.json: Monitoring and Notification Version April 22, 2025 1706 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --generate-cli-skeleton > DeleteGdThreatIntelSetRfc.json 4. Modify and save the DeleteGdThreatIntelSetRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-2qjqju7h67s7w", "Title": "DELETE_GD_THREAT_INTEL_SET" } 5. Create the RFC, specifying the DeleteGdThreatIntelSet Rfc file and the DeleteGdThreatIntelSetParams file: aws amscm create-rfc --cli-input-json file://DeleteGdThreatIntelSetRfc.json -- execution-parameters file://DeleteGdThreatIntelSetParams.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. Tips 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. For more information about Amazon GuardDuty and Threat Intel sets, see Amazon GuardDuty. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2qjqju7h67s7w. Example: Required Parameters { "Region": "us-east-1", "ThreatIntelSetId": "0cb0141ab9fbde177613ab9436212e90" Monitoring and Notification Version April 22, 2025 1707 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Example: All Parameters { "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "Region": "us-east-1", "ThreatIntelSetId": "0cb0141ab9fbde177613ab9436212e90", "Priority": "Medium" } GuardDuty Threat Intel Set | Update (Review Required) Use to update an Amazon GuardDuty ThreatIntelSet instance which is a list of trusted IP addresses that have been whitelisted for highly secure communication with your AWS environment. Full classification: Management | Monitoring and notification | GuardDuty threat intel set | Update (review required) Change Type Details Change type ID ct-2rnjx5yd6jgpt Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Update GuardDuty Threat intel set (review required) Updating a Threat intel set for GuardDuty (review required) with the console THh following shows this change type in the AMS console. Monitoring and Notification Version April 22, 2025 1708 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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, |
ams-ct-489 | ams-ct.pdf | 489 | 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. Monitoring and Notification Version April 22, 2025 1709 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Updating a Threat intel set for GuardDuty (review required) with the CLI 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 quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this: Monitoring and Notification Version April 22, 2025 1710 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --change-type-id "ct-2rnjx5yd6jgpt" --change-type-version "1.0" --title "Update Amazon GuardDuty Threat Intel Set" --execution-parameters "{\"Activate\": true, \"DetectorId\": \"00000000000000000000000000000000\", \"Name\": \"blacklisted-ips\", \"ThreatIntelSet\": \"https://s3.us-west-2.amazonaws.com/bucket- name/my-object-key\", \"ThreatIntelSetId\": \"00000000000000000000000000000000\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it UpdateGdThreatIntelSetParams.json. aws amscm get-change-type-version --change-type-id "ct-2rnjx5yd6jgpt" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > UpdateGdThreatIntelSetParams.json 2. Modify and save the UpdateGdThreatIntelSetParams file. For example, you can replace the contents with something like this: { "Activate": true, "DetectorId": "00000000000000000000000000000000", "Name": "blacklisted-ips", "ThreatIntelSet": "https://s3.us-west-2.amazonaws.com/bucket-name/my-object-key", "ThreatIntelSetId": "00000000000000000000000000000000", "Region": "us-east-1" } 3. Output the RFC template JSON file to a file named UpdateGdThreatIntelSetRfc.json: aws amscm create-rfc --generate-cli-skeleton > UpdateGdThreatIntelSetRfc.json 4. Modify and save the UpdateGdThreatIntelSetRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-2rnjx5yd6jgpt", "Title": "CREATE_GD_IP_SET" } Monitoring and Notification Version April 22, 2025 1711 AMS Advanced Change Type Reference AMS Advanced Change Type Details 5. Create the RFC, specifying the UpdateGdThreatIntelSet Rfc file and the UpdateGdThreatIntelSetParams file: aws amscm create-rfc --cli-input-json file://UpdateGdThreatIntelSetRfc.json -- execution-parameters file://UpdateGdThreatIntelSetParams.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. Tips 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. For more information about Amazon GuardDuty and creating Threat Intel sets, see Amazon Guard Duty and CreateThreatIntelSet. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2rnjx5yd6jgpt. Example: Required Parameters { "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "ThreatIntelSetId": "0cb0141ab9fbde177613ab9436212e90", "Region": "us-east-1" } Example: All Parameters { "Activate": true, "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "ThreatIntelSet": "https://s3.amazonaws.com/guarddutylists/sample.txt", Monitoring and Notification Version April 22, 2025 1712 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ThreatIntelSetId": "0cb0141ab9fbde177613ab9436212e90", "Name": "Sample ThreatIntelSet", "Region": "us-east-1", "Priority": "Medium" } SNS | Subscribe To DirectCustomerAlerts Subscribe an email address to the Direct-Customer-Alerts SNS topic. Full classification: Management | Monitoring and notification |
ams-ct-490 | ams-ct.pdf | 490 | Amazon GuardDuty and creating Threat Intel sets, see Amazon Guard Duty and CreateThreatIntelSet. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2rnjx5yd6jgpt. Example: Required Parameters { "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "ThreatIntelSetId": "0cb0141ab9fbde177613ab9436212e90", "Region": "us-east-1" } Example: All Parameters { "Activate": true, "DetectorId": "12abc34d567e8fa901bc2d34e56789f0", "ThreatIntelSet": "https://s3.amazonaws.com/guarddutylists/sample.txt", Monitoring and Notification Version April 22, 2025 1712 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ThreatIntelSetId": "0cb0141ab9fbde177613ab9436212e90", "Name": "Sample ThreatIntelSet", "Region": "us-east-1", "Priority": "Medium" } SNS | Subscribe To DirectCustomerAlerts Subscribe an email address to the Direct-Customer-Alerts SNS topic. Full classification: Management | Monitoring and notification | SNS | Subscribe to DirectCustomerAlerts Change Type Details Change type ID ct-3rcl9u1k017wu Current version 1.0 Expected execution duration 10 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Subscribe to SNS DirectCustomerAlerts Subscribing to the Direct-Customer-Alerts SNS topic with the Console Screenshot of this change type in the AMS console: Monitoring and Notification Version April 22, 2025 1713 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Monitoring and Notification Version April 22, 2025 1714 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Subscribing to the Direct-Customer-Alerts SNS topic with the CLI 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 quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this: Monitoring and Notification Version April 22, 2025 1715 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --change-type-id "ct-3rcl9u1k017wu" --change-type-version "1.0" -- title "Subscribe-Direct-Customer-Alerts" --execution-parameters "{\"Email\": \"sample- email@example.com\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it SnsSubscribeParams.json. aws amscm get-change-type-version --change-type-id "ct-3rcl9u1k017wu" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > SnsSubscribeParams.json 2. Modify and save the SnsSubscribeParams file. For example, you can replace the contents with something like this: |
ams-ct-491 | ams-ct.pdf | 491 | submit the returned RFC ID. For example, you can replace the contents with something like this: Monitoring and Notification Version April 22, 2025 1715 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --change-type-id "ct-3rcl9u1k017wu" --change-type-version "1.0" -- title "Subscribe-Direct-Customer-Alerts" --execution-parameters "{\"Email\": \"sample- email@example.com\", \"Region\": \"us-east-1\"}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it SnsSubscribeParams.json. aws amscm get-change-type-version --change-type-id "ct-3rcl9u1k017wu" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > SnsSubscribeParams.json 2. Modify and save the SnsSubscribeParams file. For example, you can replace the contents with something like this: { "Description": "SnsTopicSub-Create", "VpcId": "VPC_ID", "Name": "My-SnsTopicSub", "Parameters":{ "TopicName": "mytopic-cli-all-params", "DisplayName": "testsns", "Subscription1Protocol": "email", "Subscription1Endpoint": "abc@xyz.com", "Subscription1RawMessageDelivery": "false", "Subscription2Protocol": "sms", "Subscription2Endpoint": "+61500444777", "Subscription2RawMessageDelivery": "false", "KmsMasterKeyId": "arn:aws:kms:us-east-1:123456789101:key/ cfe0542d-3be9-4166-9eac-d0cd6af61445" } } 3. Output the RFC template JSON file to a file named SnsSubscribeRfc.json: aws amscm create-rfc --generate-cli-skeleton > SnsSubscribeRfc.json 4. Modify and save the SnsSubscribeRfc.json file. For example, you can replace the contents with something like this: { Monitoring and Notification Version April 22, 2025 1716 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3rcl9u1k017wu", "Title": "Subscribe-Direct-Customer-Alerts-RFC" } 5. Create the RFC, specifying the SnsSubscribe Rfc file and the SnsSubscribeParams file: aws amscm create-rfc --cli-input-json file://SnsSubscribeRfc.json --execution- parameters file://SnsSubscribeParams.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. Tips To learn more about AWS Simple Notification Service (SNS), see Amazon Simple Notification Service. Also see Getting Started with Amazon SNS. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3rcl9u1k017wu. Example: Required Parameters Example not available. Example: All Parameters Example not available. SNS | Update (Review Required) Modify the properties of an existing Amazon Simple Notification Service (SNS) topic. Full classification: Management | Monitoring and notification | SNS | Update (Review Required) Change Type Details Change type ID ct-0zzf0fjz76jmb Monitoring and Notification Version April 22, 2025 1717 AMS Advanced Change Type Reference AMS Advanced Change Type Details Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Update SNS topic Update SNS topic with the Console Screenshot of this change type in the AMS console: 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. Monitoring and Notification Version April 22, 2025 1718 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Update SNS topic with the CLI 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 |
ams-ct-492 | ams-ct.pdf | 492 | 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. Update SNS topic with the CLI 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 Monitoring and Notification Version April 22, 2025 1719 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 (minimal parameters): 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-0zzf0fjz76jmb" --change-type-version "1.0" --title "Update SNS Topic" --execution-parameters "{\"TopicArn\": \"arn:aws:sns:us- east-1:123456789101:My-SNS-Topic\", \"Priority\": \"Medium\", \"Parameters\": {\"DisplayName\": \"My-SNS-Topic\", \"KmsMasterKeyId\": \"arn:aws:kms:us- east-1:123456789101:key/cfe0542d-3be9-4166-9eac-d0cd6af61445\"}}" TEMPLATE CREATE (all parameters): 1. Output the execution parameters JSON schema for this change type to a file; this example names it SnsUpdateParams.json. aws amscm get-change-type-version --change-type-id "ct-3rcl9u1k017wu" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > SnsUpdateParams.json 2. Modify and save the SnsUpdateParams file. For example, you can replace the contents with something like this: { "TopicArn": "arn:aws:sns:us-east-1:123456789101:Test-Stack", "Parameters": { "DisplayName": "My-Test-Stack", "DeliveryPolicy": "{\"http\":{\"defaultHealthyRetryPolicy\":{\"minDelayTarget \":20,\"maxDelayTarget\":20,\"numRetries\":3,\"numMaxDelayRetries\":0, \"numNoDelayRetries\":0,\"numMinDelayRetries\":0,\"backoffFunction\": Monitoring and Notification Version April 22, 2025 1720 AMS Advanced Change Type Reference AMS Advanced Change Type Details \"linear\"},\"disableSubscriptionOverrides\":false,\"defaultRequestPolicy\": {\"headerContentType\":\"text/plain; charset=UTF-8\"}}}", "DataProtectionPolicy": "{\"Name\":\"__example_data_protection_policy\", \"Description\":\"Exampledataprotectionpolicy\",\"Version\": \"2021-06-01\",\"Statement\":[{\"DataDirection\":\"Inbound\",\"Principal \":[\"arn:aws:iam::123456789101:user/ExampleUser\"],\"DataIdentifier\": [\"arn:aws:dataprotection::aws:data-identifier/CreditCardNumber\"],\"Operation\": {\"Deidentify\":{\"MaskConfig\":{\"MaskWithCharacter\":\"#\"}}}}]}", "KmsMasterKeyARN": "arn:aws:kms:ap-southeast-2:123456789101:key/ bb43bd18-3a75-482e-822d-d0d3a5544dc8", "TracingConfig": "Active" }, "Priority": "Medium" } 3. Output the RFC template JSON file to a file named SnsUpdateRfc.json: aws amscm create-rfc --generate-cli-skeleton > SnsUpdateRfc.json 4. Modify and save the SnsUpdateRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-0zzf0fjz76jmb", "Title": "Update-SNS-RFC" } 5. Create the RFC, specifying the SnsUpdate Rfc file and the SnsUpdateParams file: aws amscm create-rfc --cli-input-json file://SnsUpdateRfc.json --execution- parameters file://SnsUpdateParams.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. Tips To learn more about AWS Simple Notification Service (SNS), see Amazon Simple Notification Service. Also see Getting Started with Amazon SNS. Monitoring and Notification Version April 22, 2025 1721 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0zzf0fjz76jmb. Example: Required Parameters { "TopicArn": "arn:aws:sns:us-east-1:000000000000:Test-Stack" } Example: All Parameters { "TopicArn": "arn:aws:sns:us-east-1:000000000000:Test-Stack", "Parameters":{ "DisplayName": "Test-Stack", "DeliveryPolicy": "{\"http\":{\"defaultHealthyRetryPolicy\":{\"minDelayTarget \":20,\"maxDelayTarget\":20,\"numRetries\":3,\"numMaxDelayRetries\":0, \"numNoDelayRetries\":0,\"numMinDelayRetries\":0,\"backoffFunction\":\"linear\"}, \"disableSubscriptionOverrides\":false,\"defaultRequestPolicy\":{\"headerContentType\": \"text/plain; charset=UTF-8\"}}}", "DataProtectionPolicy": "{\"Name\":\"__example_data_protection_policy\", \"Description\":\"Exampledataprotectionpolicy\",\"Version\":\"2021-06-01\",\"Statement \":[{\"DataDirection\":\"Inbound\",\"Principal\":[\"arn:aws:iam::123456789012:user/ ExampleUser\"],\"DataIdentifier\":[\"arn:aws:dataprotection::aws:data-identifier/ CreditCardNumber\"],\"Operation\":{\"Deidentify\":{\"MaskConfig\":{\"MaskWithCharacter \":\"#\"}}}}]}", "KmsMasterKeyARN": "arn:aws:kms:ap-southeast-2:123456789023:key/ bb43bd18-3a75-482e-822d-d0d3a5544dc8", "TracingConfig": "Active" }, "Priority": "Medium" } SQS | Update Use to modify the properties of an existing Amazon Simple Queue Service instance. Full classification: Management | Monitoring and notification | SQS | Update Monitoring and Notification Version April 22, 2025 1722 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Type Details Change type ID ct-0hi7z7tyikjf6 Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Update SQS queue Updating an SQS queue with the Console Screenshot of this change type in the AMS console: 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. Monitoring and Notification Version April 22, 2025 1723 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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 |
ams-ct-493 | ams-ct.pdf | 493 | popular change type (CT) in the default Browse change types view, or select a CT in the Choose by category view. Monitoring and Notification Version April 22, 2025 1723 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Updating an SQS queue with the CLI 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: Monitoring and Notification Version April 22, 2025 1724 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 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-0hi7z7tyikjf6" --change-type-version "1.0" --title "Update Amazon SQS Queue" --execution-parameters "{\"VpcId\": \"VPC_ID\", \"StackId\": \"STACK_ID\", \"Parameters\": {\"SQSDelaySeconds\": 0, \"SQSMaximumMessageSize\": 262144, \"SQSMessageRetentionPeriod\": 345600, \"SQSQueueName\": \"MyQueueName\", \"SQSReceiveMessageWaitTimeSeconds\": 0, \"SQSVisibilityTimeout\": 60}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it UpdateSqsInstanceParams.json. aws amscm get-change-type-version --change-type-id "ct-0hi7z7tyikjf6" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > UpdateSqsInstanceParams.json 2. Modify and save the UpdateSqsInstanceParams file. For example, you can replace the contents with something like this: { Monitoring and Notification Version April 22, 2025 1725 AMS Advanced Change Type Reference AMS Advanced Change Type Details "VpcId": "VPC_ID", "StackId": "STACK_ID", "Parameters": { "SQSDelaySeconds": 0, "SQSMaximumMessageSize": 262144, "SQSMessageRetentionPeriod": 345600, "SQSQueueName": "MyQueueName", "SQSReceiveMessageWaitTimeSeconds": 0, "SQSVisibilityTimeout": 60 } } 3. Output the RFC template JSON file to a file named UpdateSqsInstanceRfc.json: aws amscm create-rfc --generate-cli-skeleton > UpdateSqsInstanceRfc.json 4. Modify and save the UpdateSqsInstanceRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-0hi7z7tyikjf6", "Title": "Sqs-Instance-Update-RFC" } 5. Create the RFC, specifying the UpdateSqsTopicSub Rfc file and the UpdateSqsTopicSubParams file: aws amscm create-rfc --cli-input-json file://UpdateSqsInstanceRfc.json -- execution-parameters file://UpdateSqsInstanceParams.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. Tips To learn more about Amazon Simple Queue Service (SQS), see Amazon Simple Queue Service. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0hi7z7tyikjf6. Monitoring and Notification Version April 22, 2025 1726 AMS Advanced Change Type Reference AMS Advanced Change Type Details Example: Required Parameters { "VpcId": "vpc-01234567890abcdef", |
ams-ct-494 | ams-ct.pdf | 494 | aws amscm create-rfc --cli-input-json file://UpdateSqsInstanceRfc.json -- execution-parameters file://UpdateSqsInstanceParams.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. Tips To learn more about Amazon Simple Queue Service (SQS), see Amazon Simple Queue Service. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0hi7z7tyikjf6. Monitoring and Notification Version April 22, 2025 1726 AMS Advanced Change Type Reference AMS Advanced Change Type Details Example: Required Parameters { "VpcId": "vpc-01234567890abcdef", "StackId": "stack-a1b2c3d4e5f67890e", "Parameters": { "SQSQueueName": "mytestsqs" } } Example: All Parameters { "VpcId": "vpc-12345678", "StackId": "stack-a1b2c3d4e5f67890e", "Parameters": { "SQSDelaySeconds": 0, "SQSMaximumMessageSize": 262144, "SQSMessageRetentionPeriod": 345600, "SQSQueueName": "mytestsqs", "SQSReceiveMessageWaitTimeSeconds": 0, "SQSVisibilityTimeout": 0 } } Other Subcategory Change Type Items and Operations in the Other Subcategory • Other | Create (Review Required) • Other | Update (Review Required) Other | Create (Review Required) Use to request manual creation of a resource. Full classification: Management | Other | Other | Create (review required) Change Type Details Change type ID ct-1e1xtak34nx76 Other Version April 22, 2025 1727 AMS Advanced Change Type Reference AMS Advanced Change Type Details Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Create Other Other CTs Creating an Other Other Create RFC with the Console Screenshot of this change type in the AMS console: 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. Other Version April 22, 2025 1728 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Creating an Other Other Create RFC with the CLI 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: Other Version April 22, 2025 1729 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with |
ams-ct-495 | ams-ct.pdf | 495 | 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 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-1e1xtak34nx76" --change-type-version "1.0" -- title "TITLE" --execution-parameters "{\"Comment\": \"WHAT_TO_CREATE\"}" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file named OtherCreateParams.json. aws amscm get-change-type-version --change-type-id "ct-1e1xtak34nx76" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > OtherCreateParams.json 2. Modify and save the OtherCreateParams file (example includes optional Priority parameter). For example, you can replace the contents with something like this: { "Comment": "WHAT-TO-CREATE", "Priority": "Medium" } Other Version April 22, 2025 1730 AMS Advanced Change Type Reference AMS Advanced Change Type Details 3. Output the RFC template to a file in your current folder; this example names it OtherCreateRfc.json: aws amscm create-rfc --generate-cli-skeleton > OtherCreateRfc.json 4. Modify and save the OtherCreateRfc.json file. For example, you can replace the contents with something like this:. { "ChangeTypeId": "ct-1e1xtak34nx76", "ChangeTypeVersion": "1.0", "Title": "TITLE" } 5. Create the RFC, specifying the OtherCreateRfc file and the OtherCreateParams file: aws amscm create-rfc --cli-input-json file://OtherCreateRfc.json --execution- parameters file://OtherCreateParams.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. Tips Note To update an existing resource, use Update Other Other CTs. 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. Use this CT when you can't find a change type for what you want; however, if you are unsure about specifying parameters in an existing CT, it is better to submit a service request for help. For information on submitting service requests, see Service Request Examples. To update an existing resource, use Update Other Other CTs. Other Version April 22, 2025 1731 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1e1xtak34nx76. Example: Required Parameters { "Comment": "This is a test comment" } Example: All Parameters { "Comment": "This is a test comment", "Priority": "High", "RelatedIds": ["foo", "bar", "baz"] } Other | Update (Review Required) Use to request a manual update to a resource. Full classification: Management | Other | Other | Update (review required) Change Type Details Change type ID ct-0xdawir96cy7k Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Other Version April 22, 2025 1732 AMS Advanced Change Type Reference Additional Information Update Other Other CTs Creating an Other Other Update RFC with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Other Version April 22, 2025 1733 AMS Advanced Change Type Reference AMS Advanced Change Type Details 3. On the Run RFC page, open the CT name area to see the CT details box. A Subject |
ams-ct-496 | ams-ct.pdf | 496 | 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. Other Version April 22, 2025 1733 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Creating an Other Other Update RFC with the CLI 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 Other Version April 22, 2025 1734 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 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-0xdawir96cy7k" --change-type-version "1.0" --title "TITLE" --execution-parameters "{\"Comment\": \"What you want changed\", \"Priority\": \"Medium\" \"RelatedIds\":[\"RESOURCE_ID\",\"RESOURCE_ID\"]}}"}" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file named OtherUpdateParams.json. aws amscm get-change-type-version --change-type-id "ct-0xdawir96cy7k" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > OtherUpdateParams.json 2. Modify and save the OtherUpdateParams file. For example, you can replace the contents with something like this: { "Comment": "WHAT-TO-UPDATE", "Priority": "Medium", "RelatedIds": ["RESOURCE_ID", "RESOURCE_ID"] } 3. Output the RFC template to a file in your current folder; this example names it OtherUpdateRfc.json: aws amscm create-rfc --generate-cli-skeleton > OtherUpdateRfc.json 4. Modify and save the OtherUpdateRfc.json file. For example, you can replace the contents with something like this:. { Other Version April 22, 2025 1735 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ChangeTypeId": "ct-0xdawir96cy7k", "ChangeTypeVersion": "1.0", "Title": "TITLE" } 5. Create the RFC, specifying the OtherUpdateRfc file and the OtherUpdateParams file: aws amscm create-rfc --cli-input-json file://OtherUpdateRfc.json --execution- parameters file://OtherUpdateParams.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. Tips Important Updating or Deleting stacks can have unwanted and unanticipated consequences. AMS prefers to *not* update or delete stacks or stack resources on behalf of customers for this reason. Note, that AMS will only update or delete resources on your behalf (through a submitted Mangement | Other | Other | Update change type) that are not possible to update or delete using the appropriate, automated, change type to delete. 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. Use this CT when you can't find a change type for what you want; however, if |
ams-ct-497 | ams-ct.pdf | 497 | or delete using the appropriate, automated, change type to delete. 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. Use this CT when you can't find a change type for what you want; however, if you are unsure about specifying parameters in an existing CT, it is better to submit a service request for help. For information on submitting service requests, see Service Request Examples. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0xdawir96cy7k. Other Version April 22, 2025 1736 AMS Advanced Change Type Reference AMS Advanced Change Type Details Example: Required Parameters { "Comment": "This is a test comment" } Example: All Parameters { "Comment": "This is a test comment", "Priority": "High", "RelatedIds": ["foo", "bar", "baz"] } Patching Subcategory Change Type Items and Operations in the Patching Subcategory • On Demand Patching | Run • Patch Window | Set Status • Patch Window | Update On Demand Patching | Run Run on-demand SSM patching on specified instances; either a list of instances or instances with the specified tag/key pair. Full classification: Management | Patching | On demand patching | Run Change Type Details Change type ID ct-3oy53m1qzl2s5 Current version 1.0 Expected execution duration 3600 minutes AWS approval Required Patching Version April 22, 2025 1737 AMS Advanced Change Type Reference AMS Advanced Change Type Details Customer approval Not required Execution mode Automated Additional Information Run on-demand patching Running Patching On Demand with the Console Screenshot of this change type in the AMS console: 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. Patching Version April 22, 2025 1738 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Running Patching On Demand with the CLI 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 |
ams-ct-498 | ams-ct.pdf | 498 | 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 Patching Version April 22, 2025 1739 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 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 --title my-test-patchbaseline --change-type- id ct-3oy53m1qzl2s5 --change-type-version 1.0 --execution-parameters '{"Name":"test-ODP","PatchingTargets":[{"Key":"tag:Patch Group","Values":"[test- odp]"}],"StartInactiveInstances":"True", "BackupVaultName":"test-backup-vault-name", "BackupIamRole":"test-backup-iam-role", "BackupRetentionInDays":"10"}' TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a JSON file; this example names it RunOndemandPatchParams.json: aws amscm get-change-type-version --change-type-id "ct-3oy53m1qzl2s5" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > RunOndemandPatchParams.json 2. Modify and save the RunOndemandPatchParams file. { "Name": "test-ODP", "PatchingTargets": [ { "Key": "InstanceIds", "Values": ["INSTANCE_ID"] } ], "StartInactiveInstances": "True", "BackupVaultName": "test-backup-vault-name", "BackupIamRole": "test-backup-iam-role", "BackupRetentionInDays": "10" } Patching Version April 22, 2025 1740 AMS Advanced Change Type Reference AMS Advanced Change Type Details 3. Output the RFC template to a file in your current folder; this example names it RunOndemandPatchRfc.json: aws amscm create-rfc --generate-cli-skeleton > RunOndemandPatchRfc.json 4. Modify and save the RunOndemandPatchRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3oy53m1qzl2s5", "Title": "Run-Ondemand-Patch-RFC" } 5. Create the RFC, specifying the RunOndemandPatchRfc file and the RunOndemandPatchParams file: aws amscm create-rfc --cli-input-json file://RunOndemandPatchRfc.json --execution- parameters file://RunOndemandPatchParams.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. Tips Inactive instances If you set StartInactiveInstances to True, inactive instances are started, patched, and returned to their original stopped state after patching is completed. Concurrency limits Any concurrently running maintenance windows will impact the safe limit execution of this RFC. This is because SSM automation is limited to 100 concurrent runs per account. Automations exceeding the concurrency limit are added to a queue of up to 1,000 executions. If a maintenance window is running on 50 instances, that leaves room for only Patching Version April 22, 2025 1741 AMS Advanced Change Type Reference AMS Advanced Change Type Details 50 more to be concurrent runs for on-demand patching, adding any additional instances to the queue to be run once the in-progress executions are complete. To learn more about AMS Patch Orchestrator and setting up SSM patch baseline and patch window, see Patch Orchestrator in the AMS Multi-account landing zone User Guide. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3oy53m1qzl2s5. Example: Required Parameters Example not available. Example: All Parameters { "Description": "description", "Name": "Test1", "PatchingTargets": [ { "Key": "tag:Patch Group", "Values": [ "testGroup" ] } ], "StartInactiveInstances": "True", "BackupVaultName": "backup-vault-name", "BackupIamRole": "backup-iam-role", "BackupRetentionInDays": "1" } Patch Window | Set Status Enable or disable an existing AWS Systems Manager (SSM) patch window. If the window is enabled, any task associated with it runs on the next occurrence of the maintenance window. If disabled, Patching Version April 22, 2025 1742 AMS Advanced Change Type Reference AMS Advanced Change Type Details any future occurrences of the window no longer run. Occurrences of the window that are already running continue to run until completion. Full classification: Management | Patching | Patch window | Set status Change Type Details Change type ID ct-3vfxkiudtovm9 Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Set SSM Patch window status Set SSM Patch window status with the console The following shows this change type in the AMS console. Patching Version April 22, 2025 1743 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-499 | ams-ct.pdf | 499 | following shows this change type in the AMS console. Patching Version April 22, 2025 1743 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Set SSM Patch window status with the CLI 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. Patching Version April 22, 2025 1744 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-3vfxkiudtovm9" --change-type-version "1.0" --title "Set patch window status" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-SetPatchenanceWindowStatus\",\"Region\":\"us-east-1\",\"Parameters \":{\"MaintenanceWindowId\":[\"mw-1234567890abcdef0\"],\"Enabled\":[true]}}" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file; this example names it SetPatchWinStatusParams.json: aws amscm get-change-type-version --change-type-id "ct-3vfxkiudtovm9" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > SetPatchWinStatusParams.json Patching Version April 22, 2025 1745 AMS Advanced Change Type Reference AMS Advanced Change Type Details 2. Modify and save the SetPatchWinStatusParams file, retaining only the parameters that you want to change. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-SetPatchenanceWindowStatus", "Region": "us-east-1", "Parameters": { "MaintenanceWindowId": [ "mw-1234567890abcdef0" ], "Enabled": [ true ] } } 3. Output the RFC template to a file in your current folder; this example names it SetPatchWinStatusRfc.json: aws amscm create-rfc --generate-cli-skeleton > SetPatchWinStatusRfc.json 4. Modify and save the SetPatchWinStatusRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3vfxkiudtovm9", "Title": "Set patch window status" } 5. Create the RFC, specifying the SetPatchWinStatusRfc file and the SetPatchWinStatusParams file: aws amscm create-rfc --cli-input-json file://SetPatchWinStatusRfc.json -- execution-parameters file://SetPatchWinStatusParams.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. Patching Version April 22, 2025 1746 AMS Advanced Change Type Reference AMS Advanced Change Type Details Tips To learn |
ams-ct-500 | ams-ct.pdf | 500 | the SetPatchWinStatusRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3vfxkiudtovm9", "Title": "Set patch window status" } 5. Create the RFC, specifying the SetPatchWinStatusRfc file and the SetPatchWinStatusParams file: aws amscm create-rfc --cli-input-json file://SetPatchWinStatusRfc.json -- execution-parameters file://SetPatchWinStatusParams.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. Patching Version April 22, 2025 1746 AMS Advanced Change Type Reference AMS Advanced Change Type Details Tips To learn more about doing this, see AWS Systems Manager Maintenance Windows. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3vfxkiudtovm9. Example: Required Parameters { "DocumentName" : "AWSManagedServices-SetSsmMaintenanceWindowStatus", "Region" : "us-east-1", "Parameters" : { "MaintenanceWindowId" : [ "mw-1234567890abcdef0" ], "Enabled" : [ true ] } } Example: All Parameters { "DocumentName" : "AWSManagedServices-SetSsmMaintenanceWindowStatus", "Region" : "us-east-1", "Parameters" : { "MaintenanceWindowId" : [ "mw-1234567890abcdef0" ], "Enabled" : [ true ] } } Patch Window | Update Modify patch maintenance window settings created using version 1 of change type ct-0el2j07llrxs7. Patching Version April 22, 2025 1747 AMS Advanced Change Type Reference AMS Advanced Change Type Details Full classification: Management | Patching | Patch window | Update Change Type Details Change type ID ct-2utx36abv83pv Current version 2.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Update SSM Patch Window Updating a patch window with the Console Screenshot of this change type in the AMS console: 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. Patching Version April 22, 2025 1748 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Updating a patch window with the CLI 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: Patching Version April 22, 2025 1749 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 quotes when |
ams-ct-501 | ams-ct.pdf | 501 | 2025 1749 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 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-2utx36abv83pv" --change-type-version "2.0" --title "Patch-Window-Update-RFC" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-UpdateMaintenanceWindow\",\"Region\":\"us-east-1\",\"Parameters\": {\"Duration\":[\"3\"],\"NotificationEmails\":[\"example@email.com\"],\"PatchGroupName \":[\"MyApp\"],\"Schedule\":[\"cron(0 15 ? 9 TUE *)\"],\"ScheduleTimezone\":[\"UTC\"], \"EmailAction\":[\"Add\"],\"OnlyCheckForMaintenanceWindowDrift\":[\"False\"],\"WindowId \":[\"mw-012345678910abcef\"],\"BypassDriftDetection\":[\"False\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a JSON file; this example names it UpdatePatchWindowParams.json: aws amscm get-change-type-version --change-type-id "ct-2utx36abv83pv" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > UpdatePatchWindowParams.json 2. Modify and save the UpdatePatchWindowParams file. { Patching Version April 22, 2025 1750 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName": "AWSManagedServices-UpdateMaintenanceWindow", "Region": "us-east-1", "Parameters": { "Duration": [ "3" ], "NotificationEmails": [ "example@email.com" ], "PatchGroupName": [ "MyApp" ], "Schedule": [ "cron(0 15 ? 9 TUE *)" ], "ScheduleTimezone": [ "UTC" ], "EmailAction": [ "Add" ], "OnlyCheckForMaintenanceWindowDrift": [ "False" ], "WindowId": [ "mw-012345678910abcef" ], "BypassDriftDetection": [ "False" ] } } 3. Output the RFC template to a file in your current folder; this example names it UpdatePatchWindowRfc.json: aws amscm create-rfc --generate-cli-skeleton > UpdatePatchWindowRfc.json 4. Modify and save the UpdatePatchWindowRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "2.0", Patching Version April 22, 2025 1751 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ChangeTypeId": "ct-2utx36abv83pv", "Title": "Patch-Window-Update-RFC" } 5. Create the RFC, specifying the UpdatePatchWindowRfc file and the UpdatePatchWindowParams file: aws amscm create-rfc --cli-input-json file://UpdatePatchWindowRfc.json --execution- parameters file://UpdatePatchWindowParams.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. 6. To view the SSM patch baseline, look in the execution output: Use the stack_id to view the patch baseline in the Systems Manager console. Tips • This solution uses custom logic to detect drift in AWS resources not yet supported by CloudFormation (AWS::SSM::MaintenanceWindow & AWS::SSM::MaintenanceWindowTarget). We recommend executing this change type with the parameter OnlyCheckForMaintenanceWindowDrift=True for the most accurate report of drifted AMS Patch maintance window resources. • To learn more about AWS SSM patch windows, see "Maintenance Window" at Patching your Windows EC2 instances using AWS Systems Manager Patch Manager. • To delete a custom Maintenance Window, see Delete stack. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2utx36abv83pv. Example: Required Parameters { "DocumentName": "AWSManagedServices-UpdateMaintenanceWindow", "Region": "us-east-1", "Parameters": { "EmailAction": [ "None" ], Patching Version April 22, 2025 1752 AMS Advanced Change Type Reference AMS Advanced Change Type Details "OnlyCheckForMaintenanceWindowDrift": [ "True" ], "WindowId": [ "mw-012345678910abcef" ], "BypassDriftDetection": [ "False" ] } } Example: All Parameters { "DocumentName": "AWSManagedServices-UpdateMaintenanceWindow", "Region": "us-east-1", "Parameters": { "Duration": [ "2" ], "EmailAction": [ "Add" ], "NotificationEmails": [ "nobody@amazon.com" ], "OnlyCheckForMaintenanceWindowDrift": [ "False" ], "PatchGroupName": [ "Test" ], "Schedule": [ "cron(0 17 * * ? *)" ], "ScheduleTimezone": [ "UTC" ], "WindowId": [ "mw-012345678910abcef" ], "BypassDriftDetection": [ "False" ] } } Standalone Resources Subcategory Change Type Items and Operations in the Standalone Resources Subcategory • EC2 Instance | Terminate • Load Balancer | Delete • RDS Instance | Terminate EC2 Instance | Terminate Terminate up to fifty EC2 instances. The automation checks that none of the instances are part of an Auto Scaling group and none have termination protection enabled. Instances meeting either of those criteria are not terminated. Standalone resources for testing purposes are created by AMS upon your request, they are not part of a stack and can't be deleted with ct-0q0bic0ywqk6c. Full classification: Management | Standalone resources | EC2 instance | Terminate Standalone Resources Version April 22, 2025 1753 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Type Details Change type ID ct-3dfubbpesm2v9 Current version 1.0 Expected execution duration 150 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Terminate instances Terminating standalone EC2 instances with the console The following shows this change type in the AMS console. 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 |
ams-ct-502 | ams-ct.pdf | 502 | Type Reference AMS Advanced Change Type Details Change Type Details Change type ID ct-3dfubbpesm2v9 Current version 1.0 Expected execution duration 150 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Terminate instances Terminating standalone EC2 instances with the console The following shows this change type in the AMS console. 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. Standalone Resources Version April 22, 2025 1754 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Terminating standalone EC2 instances with the CLI 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: Standalone Resources Version April 22, 2025 1755 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Only specify the parameters you want to change. Absent parameters retain the existing values. 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 --change-type-id "ct-3dfubbpesm2v9" --change-type-version "1.0" --title "Terminate standalone instances" --execution-parameters "{\"DocumentName \": \"AWSManagedServices-TerminateStandaloneInstances\",\"Region\": \"us-east-1\", \"Confirmation\": \"terminate instances\",\"Parameters\": {\"InstanceIds\": [\"i-1234567890abcdef0\"]}}" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file; this example names it TerminateStandaloneEc2sParams.json: aws amscm get-change-type-version --change-type-id "ct-3dfubbpesm2v9" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TerminateStandaloneEc2sParams.json 2. Modify and save the TerminateStandaloneEc2sParams file, retaining only the parameters that you want to change. For example, you can replace the contents with something like this: { Standalone Resources Version April 22, 2025 1756 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName": "AWSManagedServices-TerminateStandaloneInstances", "Region": "us-east-1", "Confirmation": "terminate instances", "Parameters": { "InstanceIds": [ "i-1234567890abcdef0" ] } } 3. Output the RFC template to a file in your current folder; this example names it TerminateStandaloneEc2sRfc.json: aws amscm create-rfc --generate-cli-skeleton > TerminateStandaloneEc2sRfc.json 4. Modify and save the TerminateStandaloneEc2sRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-3dfubbpesm2v9", "ChangeTypeVersion": "1.0", "Title": "Terminate standalone EC2 instance" } 5. Create the RFC, specifying the TerminateStandaloneEc2sRfc file and the TerminateStandaloneEc2sParams |
ams-ct-503 | ams-ct.pdf | 503 | with something like this: { Standalone Resources Version April 22, 2025 1756 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName": "AWSManagedServices-TerminateStandaloneInstances", "Region": "us-east-1", "Confirmation": "terminate instances", "Parameters": { "InstanceIds": [ "i-1234567890abcdef0" ] } } 3. Output the RFC template to a file in your current folder; this example names it TerminateStandaloneEc2sRfc.json: aws amscm create-rfc --generate-cli-skeleton > TerminateStandaloneEc2sRfc.json 4. Modify and save the TerminateStandaloneEc2sRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-3dfubbpesm2v9", "ChangeTypeVersion": "1.0", "Title": "Terminate standalone EC2 instance" } 5. Create the RFC, specifying the TerminateStandaloneEc2sRfc file and the TerminateStandaloneEc2sParams file: aws amscm create-rfc --cli-input-json file://TerminateStandaloneEc2sRfc.json -- execution-parameters file://TerminateStandaloneEc2sParams.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. Tips To learn more about termination protection, see How do I protect my data against accidental EC2 instance termination?. Standalone Resources Version April 22, 2025 1757 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3dfubbpesm2v9. Example: Required Parameters { "DocumentName": "AWSManagedServices-TerminateStandaloneInstances", "Region": "us-east-1", "Confirmation": "terminate instances", "Parameters": { "InstanceIds": [ "i-1234567890abcdef0" ] } } Example: All Parameters { "DocumentName": "AWSManagedServices-TerminateStandaloneInstances", "Region": "us-east-1", "Confirmation": "terminate instances", "Parameters": { "InstanceIds": ["i-1234567890abcdef0"] } } Load Balancer | Delete Delete a standalone load balancer (application or network). The deletion includes comprehensive validation of deletion protection, CloudFormation stack association, and the AMS Infrastructure tag, and only proceeds if all checks pass. Standalone resources for testing purposes are created by AMS upon your request, they are not part of a stack and they can't be deleted with ct-0q0bic0ywqk6c. Full classification: Management | Standalone resources | Load Balancer | Delete Standalone Resources Version April 22, 2025 1758 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Type Details Change type ID ct-2fuzb2l7hckrj Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Delete standalone load balancer Deleting a standalone load balancer with the Console Screenshot of this change type in the AMS console: 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. Standalone Resources Version April 22, 2025 1759 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Deleting a standalone load balancer with the CLI 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 |
ams-ct-504 | ams-ct.pdf | 504 | the top of the page. Deleting a standalone load balancer with the CLI 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: Standalone Resources Version April 22, 2025 1760 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-2fuzb2l7hckrj" --change-type-version "1.0" --title "Delete Load Balancer" --execution-parameters "{ \"DocumentName \": \"AWSManagedServices-DeleteLoadBalancer\", \"Region\": \"us-east-1\", \"Parameters\": { \"LoadBalancerArn\": \"arn:aws:elasticloadbalancing:us- east-1:123456789012:loadbalancer/app/alb/630abcd\", \"DryRun\": true } }" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file named DeleteStandaloneLoadBalancerParams.json. aws amscm get-change-type-version --change-type-id "ct-2fuzb2l7hckrj" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > DeleteStandaloneLoadBalancerParams.json 2. Modify and save the execution parameters JSON file. For example, you can replace the contents with something like this: All parameters example: { Standalone Resources Version April 22, 2025 1761 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName": "AWSManagedServices-DeleteLoadBalancer", "Region": "us-east-1", "Parameters": { "LoadBalancerArn": "arn:aws:elasticloadbalancing:us- east-1:123456789012:loadbalancer/app/alb/630abcd", "DryRun": true } } Only required parameters example: { "DocumentName": "AWSManagedServices-DeleteLoadBalancer", "Region": "us-east-1", "Parameters": { "LoadBalancerArn": "arn:aws:elasticloadbalancing:us- east-1:123456789012:loadbalancer/app/alb/630abcd" } } 3. Output the JSON template to a file in your current folder; this example names it DeleteStandaloneLoadBalancerRfc.json: aws amscm create-rfc --generate-cli-skeleton > DeleteStandaloneLoadBalancerRfc.json 4. Modify and save the DeleteStandaloneLoadBalancerRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-2fuzb2l7hckrj", "Title": "Delete standalone load balancer" } 5. Create the RFC, specifying the execution parameters file and the DeleteStandaloneLoadBalancerRfc file: aws amscm create-rfc --cli-input-json file://DeleteStandaloneLoadBalancerRfc.json --execution-parameters file://DeleteStandaloneLoadBalancerParams.json Standalone Resources Version April 22, 2025 1762 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Tips • In AMS Advanced standalone load balancers are created by AMS Support engineers at your request, or by you using the Developer role or through the AMS Self-service Provisioning service. • Important considerations: • Before deleting, make sure that no traffic is currently being routed through the load balancer • Deleting a load balancer does not automatically delete the target groups associated with it • If you have a DNS record for your domain pointing to the load balancer, update it to point to a new location before deleting the load balancer Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2fuzb2l7hckrj. Example: Required Parameters Example not available. Example: All Parameters { "DocumentName": "AWSManagedServices-DeleteLoadBalancer", "Region": "us-east-1", "Parameters": { "LoadBalancerArn": "arn:aws:elasticloadbalancing:us- east-1:123456789101:loadbalancer/app/pivkulxf-custom-alb/630aaaaad7a41c37", "DryRun": true } } RDS Instance | Terminate Terminate a standalone DB instance or cluster. The automation checks that the DB instance, or cluster, is not part of a CloudFormation stack and does not have termination protection enabled. Standalone Resources Version April 22, 2025 1763 AMS Advanced Change Type Reference AMS Advanced Change Type Details Please note that deleting the DB cluster deletes all the automated backups for that DB cluster and those backups can't be recovered. Standalone resources for testing purposes are created by AMS upon your request, they are not part of a stack and they can't be deleted with ct-0q0bic0ywqk6c. Full classification: Management | Standalone resources | RDS instance | Terminate Change Type Details Change type ID ct-3glr80c15rp7z Current version 1.0 Expected execution duration 150 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Terminate Standalone RDS instance or cluster Terminating standalone RDS instance or cluster with the console The following shows this change type in the AMS console. Standalone Resources Version April 22, 2025 1764 AMS Advanced Change Type Reference AMS Advanced Change Type Details How it works: 1. Navigate to the Create |
ams-ct-505 | ams-ct.pdf | 505 | not part of a stack and they can't be deleted with ct-0q0bic0ywqk6c. Full classification: Management | Standalone resources | RDS instance | Terminate Change Type Details Change type ID ct-3glr80c15rp7z Current version 1.0 Expected execution duration 150 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Terminate Standalone RDS instance or cluster Terminating standalone RDS instance or cluster with the console The following shows this change type in the AMS console. Standalone Resources Version April 22, 2025 1764 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Terminating standalone RDS instance or cluster with the CLI 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. Standalone Resources Version April 22, 2025 1765 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Only specify the parameters you want to change. Absent parameters retain the existing values. 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 --change-type-id "ct-3glr80c15rp7z" --change-type-version "1.0" --title "Terminate Standalone DB Instance Or Cluster" --execution- parameters "{\"DocumentName\": \"TerminateStandaloneDBInstanceOrCluster\", \"Region\": \"us-east-1\",\"Parameters\": {\"DBIdentifierArn\": [\"arn:aws:rds:us- east-1:123456789101:db:testdb-instance-1\"]}}" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file; this example names it TerminateStandaloneDBParameters.json: Standalone Resources Version April 22, 2025 1766 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm get-change-type-version --change-type-id "ct-3glr80c15rp7z" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TerminateStandaloneDBParameters.json 2. Modify and save the TerminateStandaloneDBParameters.json file, retaining only the parameters that you want to change. For example, you can replace the contents with something like this: TerminateStandaloneDBParameters.json { "DocumentName": "TerminateStandaloneDBInstanceOrCluster", "Region": "us-east-1", "DBIdentifierArn": [ "arn:aws:rds:us-east-1:123456789101:db:testdb-instance-1" ] } 3. Output the RFC template to a file in your current folder; this example names it TerminateStandaloneDB.json: aws amscm create-rfc --generate-cli-skeleton > TerminateStandaloneDB.json 4. Modify and save the TerminateStandaloneDB.json file. For example, you can replace the contents with something like this: { |
ams-ct-506 | ams-ct.pdf | 506 | Advanced Change Type Reference AMS Advanced Change Type Details aws amscm get-change-type-version --change-type-id "ct-3glr80c15rp7z" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TerminateStandaloneDBParameters.json 2. Modify and save the TerminateStandaloneDBParameters.json file, retaining only the parameters that you want to change. For example, you can replace the contents with something like this: TerminateStandaloneDBParameters.json { "DocumentName": "TerminateStandaloneDBInstanceOrCluster", "Region": "us-east-1", "DBIdentifierArn": [ "arn:aws:rds:us-east-1:123456789101:db:testdb-instance-1" ] } 3. Output the RFC template to a file in your current folder; this example names it TerminateStandaloneDB.json: aws amscm create-rfc --generate-cli-skeleton > TerminateStandaloneDB.json 4. Modify and save the TerminateStandaloneDB.json file. For example, you can replace the contents with something like this: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-3glr80c15rp7z", "Title": "Terminate Standalone DB Instance Or Cluster" } 5. Create the RFC, specifying the TerminateStandaloneDB.json file and the TerminateStandaloneDBParameters file: aws amscm create-rfc --cli-input-json file://TerminateStandaloneDB.json -- execution-parameters file://TerminateStandaloneDBParameters.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. Standalone Resources Version April 22, 2025 1767 AMS Advanced Change Type Reference AMS Advanced Change Type Details Tips To learn more about RDS deletion protection, see Deletion Protection. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3glr80c15rp7z. Example: Required Parameters { "DocumentName": "AWSManagedServices-TerminateStandaloneDBInstanceOrCluster", "Region": "us-east-1", "Confirmation": "permanently delete", "Parameters": { "DBIdentifierArn": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance" } } Example: All Parameters { "DocumentName": "AWSManagedServices-TerminateStandaloneDBInstanceOrCluster", "Region": "us-east-1", "Confirmation": "permanently delete", "Parameters": { "DBIdentifierArn": "arn:aws:rds:us-east-1:123456789012:db:my-db-instance", "CreateFinalSnapshot": true, "DeleteAutomatedBackups": false, "FinalDBSnapshotIdentifier": "final-db-snapshot" } } Standard Stacks Subcategory Change Type Items and Operations in the Standard Stacks Subcategory • Stack | Delete • Stack | Reboot • Stack | Remediate Drift Standard Stacks Version April 22, 2025 1768 AMS Advanced Change Type Reference AMS Advanced Change Type Details • Stack | Remediate Drift (Review Required) • Stack | Start • Stack | Stop • Stack | Update Termination Protection Stack | Delete Delete an existing stack and its resources from your account. The effects of deleting a resource vary. For details, see the appropriate AWS documentation for the resource. Note that termination protection on a resource in the stack causes the RFC to fail. To check for a resource's termination protection status, see the corresponding AWS console. Full classification: Management | Standard stacks | Stack | Delete Change Type Details Change type ID ct-0q0bic0ywqk6c Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Delete stack Deleting a Stack with the Console Screenshot of this change type in the AMS console: Standard Stacks Version April 22, 2025 1769 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Standard Stacks Version April 22, 2025 1770 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Deleting a Stack with the CLI How it works: 1. Use either the Inline Create (you issue a create-rfc command |
ams-ct-507 | ams-ct.pdf | 507 | April 22, 2025 1770 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Deleting a Stack with the CLI 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: Standard Stacks Version April 22, 2025 1771 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-0q0bic0ywqk6c" --change-type-version "1.0" -- title "Delete My Stack" --execution-parameters "{\"StackId\":\"STACK_ID\"}" TEMPLATE CREATE: 1. Output the RFC template to a file in your current folder; this example names it DeleteStackRfc.json: aws amscm create-rfc --generate-cli-skeleton > DeleteStackRfc.json 2. Modify and save the DeleteStackRfc.json file. The internal quotation marks in the ExecutionParameters JSON extension must be escaped with a backslash (\). Example without start and end time: { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-0q0bic0ywqk6c", "Title": "Delete-My-Stack-RFC" "ExecutionParameters": "{ \"StackId\":\"STACK_ID\"}" } 3. Create the RFC: aws amscm create-rfc --cli-input-json file://DeleteStackRfc.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. Tips Note If deleting an S3 bucket, it must be emptied of objects first. Standard Stacks Version April 22, 2025 1772 AMS Advanced Change Type Reference AMS Advanced Change Type Details Important Deleting stacks can have unwanted and unanticipated consequences. For important caveats, see RFC Troubleshooting section RFCs for Delete Stack. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-0q0bic0ywqk6c. Example: Required Parameters Example not available. Example: All Parameters { "StackId": "stack-a1b2c3d4e5f67890e", "TimeoutInMinutes": 720 } Stack | Reboot Use to reboot all running EC2 and RDS DB instances in the specified stack. Full classification: Management | Standard stacks | Stack | Reboot Change Type Details Change type ID ct-02u0hoaa9grat Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Standard Stacks Version April 22, 2025 1773 AMS Advanced Change Type Reference Additional Information Reboot stack Rebooting a Stack with the Console Screenshot of this change type in the AMS console: AMS Advanced Change Type Details 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. Standard Stacks Version April 22, 2025 1774 AMS Advanced Change Type Reference AMS Advanced Change Type Details 3. On the Run RFC page, open the CT |
ams-ct-508 | ams-ct.pdf | 508 | 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. Standard Stacks Version April 22, 2025 1774 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Rebooting a Stack with the CLI 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 Standard Stacks Version April 22, 2025 1775 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-02u0hoaa9grat" --change-type-version "1.0" -- title "Reboot My Stack" --execution-parameters "{\"StackId\":\"STACK_ID\"}" TEMPLATE CREATE: 1. Output the RFC template to a file in your current folder. This example names it RebootStackRfc.json. Note that since there is only one execution parameter for stopping (rebooting, or starting) an instance, the execution parameter can be in the schema JSON file itself and there is no need to create a separate execution parameters JSON file. aws amscm create-rfc --generate-cli-skeleton > StopInstanceRfc.json 2. Modify and save the RebootStackRfc.json file. The internal quotation marks in the ExecutionParameters JSON extension must be escaped with a backslash (\). Example: { "ChangeTypeId": "ct-02u0hoaa9grat", "Title": "Reboot-My-EC2-RFC", "TimeoutInMinutes": 60, "ExecutionParameters": "{ \"StackId\":\"STACK_ID\" }" } 3. Create the RFC: aws amscm create-rfc --cli-input-json file://RebootStackRfc.json Standard Stacks Version April 22, 2025 1776 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Tips For information about Application Load Balancers, see Application Load Balancers. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-02u0hoaa9grat. Example: Required Parameters Example not available. Example: All Parameters { "StackId": "stack-f16bbbeea61df041f" } Stack | Remediate Drift Remediate the drift (out-of-band changes) in a stack, bringing the stack in sync and enabling you to perform future updates using the available Update CTs. Note: up to 10 drifted resources will be remediated per RFC. Full classification: Management | Standard stacks | Stack | Remediate drift Change Type Details Change type ID ct-3kinq0u4l33zf Current version 1.0 Expected execution duration 60 minutes Standard Stacks Version April 22, 2025 1777 AMS Advanced Change Type Reference AMS Advanced Change Type Details AWS approval Required Customer approval Not required Execution mode Automated Additional Information Remediate stack drift Drift remediation supported resources (ct-3kinq0u4l33zf) These are the resources that are supported by the drift remediation change type, (ct-3kinq0u4l33zf). For remediation of any resource, use the "review required" (ct-34sxfo53yuzah) |
ams-ct-509 | ams-ct.pdf | 509 | Update CTs. Note: up to 10 drifted resources will be remediated per RFC. Full classification: Management | Standard stacks | Stack | Remediate drift Change Type Details Change type ID ct-3kinq0u4l33zf Current version 1.0 Expected execution duration 60 minutes Standard Stacks Version April 22, 2025 1777 AMS Advanced Change Type Reference AMS Advanced Change Type Details AWS approval Required Customer approval Not required Execution mode Automated Additional Information Remediate stack drift Drift remediation supported resources (ct-3kinq0u4l33zf) These are the resources that are supported by the drift remediation change type, (ct-3kinq0u4l33zf). For remediation of any resource, use the "review required" (ct-34sxfo53yuzah) change type instead. AWS::EC2::Instance AWS::EC2::SecurityGroup AWS::EC2::VPC AWS::EC2::Subnet AWS::EC2::NetworkInterface AWS::EC2::EIP AWS::EC2::InternetGateway AWS::EC2::NatGateway AWS::EC2::NetworkAcl AWS::EC2::RouteTable AWS::EC2::Volume AWS::AutoScaling::AutoScalingGroup AWS::AutoScaling::LaunchConfiguration AWS::AutoScaling::LifecycleHook AWS::AutoScaling::ScalingPolicy AWS::AutoScaling::ScheduledAction AWS::ElasticLoadBalancing::LoadBalancer AWS::ElasticLoadBalancingV2::Listener AWS::ElasticLoadBalancingV2::ListenerRule AWS::ElasticLoadBalancingV2::LoadBalancer AWS::CloudWatch::Alarm Remediating Stack Drift with the Console Screenshot of this change type in the AMS console: Standard Stacks Version April 22, 2025 1778 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Standard Stacks Version April 22, 2025 1779 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Remediating Stack Drift with the CLI 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: Standard Stacks Version April 22, 2025 1780 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --change-type-id "ct-3kinq0u4l33zf" --change-type-version "1.0" -- title "Remediate Stack Drift, no ops review" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-StartDriftRemediation\", \"Region\": \"us-east-1\", \"Parameters \": {\"StackName\": [\"stack-xxxxxxxxxxxxxxxxx\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it RemediateDriftNrrParams.json: aws amscm create-rfc --generate-cli-skeleton > RemediateDriftNrrParams.json 2. Modify and save the RemediateDriftNrrParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-StartDriftRemediation", "Region": "us-east-1", "Parameters": { "StackName": [ "stack-xxxxxxxxxxxxxxxxx" ] } } 3. Output the RFC template |
ams-ct-510 | ams-ct.pdf | 510 | 22, 2025 1780 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --change-type-id "ct-3kinq0u4l33zf" --change-type-version "1.0" -- title "Remediate Stack Drift, no ops review" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-StartDriftRemediation\", \"Region\": \"us-east-1\", \"Parameters \": {\"StackName\": [\"stack-xxxxxxxxxxxxxxxxx\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it RemediateDriftNrrParams.json: aws amscm create-rfc --generate-cli-skeleton > RemediateDriftNrrParams.json 2. Modify and save the RemediateDriftNrrParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-StartDriftRemediation", "Region": "us-east-1", "Parameters": { "StackName": [ "stack-xxxxxxxxxxxxxxxxx" ] } } 3. Output the RFC template JSON file to a file; this example names it RemediateDriftNrrRfc.json: aws amscm create-rfc --generate-cli-skeleton > RemediateDriftNrrRfc.json 4. Modify and save the RemediateDriftNrrRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-3kinq0u4l33zf", "ChangeTypeVersion": "1.0", "Title": "Remediate stack drift, no ops review" } 5. Create the RFC, specifying the RemediateDriftNrrRfc file and the RemediateDriftNrrParams file: Standard Stacks Version April 22, 2025 1781 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --cli-input-json file://RemediateDriftNrrRfc.json -- execution-parameters file://RemediateDriftNrrParams.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. Tips Important Stack remediation modifies the stack template and/or parameter values. Once remediation is complete, you must update your local template repositories, or any automation, that would be updating the remediated stack, with the latest template and parameters provided in the RFC summary of the remeditation. It is very important to do this, because using the old template and/or parameters can cause destructive changes on the stack resources. For more details, including a list of Limitations, see Drift remediation FAQs. Note When using "review required" CTs, AMS recommends that you use the ASAP Scheduling option (choose ASAP in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, 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-3kinq0u4l33zf. Example: Required Parameters Example not available. Standard Stacks Version April 22, 2025 1782 AMS Advanced Change Type Details AMS Advanced Change Type Reference Example: All Parameters { "DocumentName": "AWSManagedServices-StartDriftRemediation", "Region": "us-east-1", "Parameters": { "StackName": ["stack-a1b2c3d4e5f678900"], "DryRun": ["true"] } } Stack | Remediate Drift (Review Required) Remediate the drift (out-of-band changes) in a stack, bringing the stack in sync and enabling you to perform future updates using the available Update CTs. Drift remediation can be performed on EC2 resource types. Full classification: Management | Standard stacks | Stack | Remediate drift (review required) Change Type Details Change type ID ct-34sxfo53yuzah Current version 1.0 Expected execution duration 240 minutes AWS approval Required Customer approval Not required if submitter Execution mode Manual Additional Information Remediate stack drift (review required) Remediating Stack Drift (review required) with the Console Screenshot of this change type in the AMS console: Standard Stacks Version April 22, 2025 1783 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-511 | ams-ct.pdf | 511 | 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. Standard Stacks Version April 22, 2025 1784 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Remediating Stack Drift (review required) with the CLI 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: Standard Stacks Version April 22, 2025 1785 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-34sxfo53yuzah" --change-type-version "1.0" --title "Remediate stack drift" --execution-parameters '{"StackName":"stack- a1b2c3d4e5f67890e","DryRun":false}' TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it RemediateDriftParams.json: aws amscm create-rfc --generate-cli-skeleton > RemediateDriftParams.json 2. Modify and save the RemediateDriftParams file. For example, you can replace the contents with something like this: { "StackName" : "stack-a1b2c3d4e5f67890e", "DryRun" : false } 3. Output the RFC template JSON file to a file; this example names it RemediateDriftRfc.json: aws amscm create-rfc --generate-cli-skeleton > RemediateDriftRfc.json 4. Modify and save the RemediateDriftRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-34sxfo53yuzah", "ChangeTypeVersion": "1.0", "Title": "Remediate stack drift" } 5. Create the RFC, specifying the RemediateDriftRfc file and the RemediateDriftParams file: aws amscm create-rfc --cli-input-json file://RemediateDriftRfc.json --execution- parameters file://RemediateDriftParams.json Standard Stacks Version April 22, 2025 1786 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Tips 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. Note When using "review required" CTs, AMS recommends that you use the ASAP Scheduling option (choose ASAP in the console, leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. • There is an automated version of this change type that runs more quickly, though there are some limitations. For more details, see Stack | Remediate Drift. • Stack remediation modifies the stack template and/or parameter values. Once remediation is |
ams-ct-512 | ams-ct.pdf | 512 | leave start and end time blank in the API/CLI) as these CTs require an AMS operator to examine the RFC, and possibly communicate with you before it can be approved and run. If you schedule these RFCs, be sure to allow at least 24 hours. If approval does not happen before the scheduled start time, the RFC is rejected automatically. • There is an automated version of this change type that runs more quickly, though there are some limitations. For more details, see Stack | Remediate Drift. • Stack remediation modifies the stack template and/or parameter values. Once remediation is complete, you must update your local template repositories, or any automation, that would be updating the remediated stack, with the latest template and parameters provided in the RFC summary of the remeditation. It is very important to do this, because using the old template and/or parameters can cause destructive changes on the stack resources. For more details, see Drift remediation FAQs. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-34sxfo53yuzah. Standard Stacks Version April 22, 2025 1787 AMS Advanced Change Type Reference AMS Advanced Change Type Details Example: Required Parameters { "StackName": "stack-a1b2c3d4e5f678900" } Example: All Parameters { "StackName": "stack-a1b2c3d4e5f678900", "DryRun": false, "Priority": "Medium" } Stack | Start Use to start all stopped EC2 instances in the specified stack. Full classification: Management | Standard stacks | Stack | Start Change Type Details Change type ID ct-1h5xgl9cr4bzy Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Start stack Starting a Stack with the Console Screenshot of this change type in the AMS console: Standard Stacks Version April 22, 2025 1788 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Standard Stacks Version April 22, 2025 1789 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Starting a Stack with the CLI 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. |
ams-ct-513 | ams-ct.pdf | 513 | 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: Standard Stacks Version April 22, 2025 1790 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-1h5xgl9cr4bzy" --change-type-version "1.0" -- title "Start My Stack" --execution-parameters "{\"StackId\":\"STACK_ID\"}" TEMPLATE CREATE: 1. Output the RFC template to a file in your current folder. This example names it StartInstanceRfc.json. Note that since there is only one execution parameter for starting a stack, the execution parameter can be in the schema JSON file itself and there is no need to create a separate execution parameters JSON file. aws amscm create-rfc --generate-cli-skeleton > StartStackRfc.json 2. Modify and save the StartStackRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-1h5xgl9cr4bzy", "Title": "Start-My-EC2-RFC", "TimeoutInMinutes": 60, "ExecutionParameters": "{ \"StackId\":\"STACK_ID\" }" } 3. Create the RFC: aws amscm create-rfc --cli-input-json file://StartStackRfc.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. Tips For information about Application Load Balancers, see Application Load Balancers. Standard Stacks Version April 22, 2025 1791 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1h5xgl9cr4bzy. Example: Required Parameters Example not available. Example: All Parameters { "StackId": "stack-f16bbbeea61df041f" } Stack | Stop Use to stop all running EC2 instances in the specified stack. Full classification: Management | Standard stacks | Stack | Stop Change Type Details Change type ID ct-3dgbnh6gpst4d Current version 1.0 Expected execution duration 60 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Stop stack Stopping an EC2 instance with the console The following shows this change type in the AMS console. Standard Stacks Version April 22, 2025 1792 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Standard Stacks Version April 22, 2025 1793 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Stopping an EC2 instance with the CLI How it works: 1. Use either the Inline |
ams-ct-514 | ams-ct.pdf | 514 | 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. Standard Stacks Version April 22, 2025 1793 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Stopping an EC2 instance with the CLI 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: Standard Stacks Version April 22, 2025 1794 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm create-rfc --change-type-id "ct-3mvvt2zkyveqj" --change-type-version "3.0" --title "Stop EC2 Instances" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-StopInstances\",\"Region\":\"us-east-1\",\"Parameters\": {\"InstanceIds\":[\"i-1234567890abcdef0\", \"i-1234567890abcdef1\"],\"ForceStop\": [\"false\"],\"StopASGInServiceInstances\":[\"false\"]}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a JSON file; this example names it StopEC2Params.json: aws amscm get-change-type-version --change-type-id "ct-3mvvt2zkyveqj" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > StopEC2Params.json 2. Modify and save the StopEC2Params file. { "DocumentName" : "AWSManagedServices-StopInstances", "Region" : "us-east-1", "Parameters" : { "InstanceIds" : [ "i-1234567890abcdef0", "i-1234567890abcdef1" ], "ForceStop": [ "false" ], "StopASGInServiceInstances": [ "false" ] } } 3. Output the RFC template to a file in your current folder; this example names it StopEC2Rfc.json: aws amscm create-rfc --generate-cli-skeleton > StopEC2Rfc.json 4. Modify and save the StopEC2Rfc.json file. For example, you can replace the contents with something like this: Standard Stacks Version April 22, 2025 1795 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "ChangeTypeVersion": "3.0", "ChangeTypeId": "ct-3mvvt2zkyveqj", "Title": "Stop EC2 Instances" } 5. Create the RFC, specifying the StopEC2Rfc file and the StopEC2Params file: aws amscm create-rfc --cli-input-json file://StopEC2Rfc.json --execution-parameters file://StopEC2Params.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. Tips Note This change type is now at version 3.0. The schema has been changed so you can stop up to fifty instances. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3dgbnh6gpst4d. Example: Required Parameters Example not available. Example: All Parameters { "StackId": "stack-f16bbbeea61df041f" } Standard Stacks Version April 22, 2025 1796 AMS Advanced Change Type Reference AMS Advanced Change Type Details Stack | Update Termination Protection Update existing defined termination protection for stacks. Full classification: Management | Standard stacks | Stack | Update termination protection Change Type Details Change type ID ct-2uzbqr7x7mekd Current version 1.0 Expected execution duration 10 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Update AWS CloudFormation stacks termination protection Updating an AWS CloudFormation termination protection stack with the console The following shows this change type in the AMS console. How it works: Standard Stacks Version April 22, 2025 1797 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-515 | ams-ct.pdf | 515 | 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. Updating an AWS CloudFormation stack termination protection with the CLI 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. Standard Stacks Version April 22, 2025 1798 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Only specify the parameters you want to change. Absent parameters retain the existing values. 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 \ --change-type-id "ct-2uzbqr7x7mekd" \ --change-type-version "1.0" \ --title "Enable termination protection on CFN stack" \ --execution-parameters "{\"DocumentName\":\"AWSManagedServices- ManageResourceTerminationProtection\",\"Region\":\"us-east-1\",\"Parameters\": {\"ResourceId\":[\"stack-psvnq6cupymio3enl\"],\"TerminationProtectionDesiredState\": [\"enabled\"]}}" TEMPLATE CREATE: 1. Output the execution parameters for this change type to a JSON file; this example names it EnableTermProCFNParams.json: Standard Stacks Version April 22, 2025 1799 AMS Advanced Change Type Reference AMS Advanced Change Type Details aws amscm get-change-type-version --change-type-id "ct-2uzbqr7x7mekd" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > EnableTermProCFNParams.json 2. Modify and save the EnableTermProCFNParams file, retaining only the parameters that you want to change. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-ManageResourceTerminationProtection", "Region": "us-east-1", "Parameters": { "ResourceId": ["stack-psvnq6cupymio3enl"], "TerminationProtectionDesiredState": ["enabled"] } } 3. Output the RFC template to a file in your current folder; this example names it EnableTermProCFNRfc.json: aws amscm create-rfc --generate-cli-skeleton > EnableTermProCFNRfc.json 4. Modify and save the EnableTermProCFNRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-2uzbqr7x7mekd", "ChangeTypeVersion": "1.0", "Title": "Enable termination protection on CFN instance" } 5. Create the RFC, specifying the EnableTermProCFNRfc file and the EnableTermProCFNParams file: aws amscm create-rfc --cli-input-json file://EnableTermProCFNRfc.json --execution- parameters file://EnableTermProCFNParams.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. Standard Stacks Version April 22, 2025 1800 AMS Advanced Change Type Reference AMS Advanced Change Type Details Tips Note There is a related CT for Amazon EC2, EC2 stack: Updating termination protection. To learn more about termination protection, see Protecting a stack |
ams-ct-516 | ams-ct.pdf | 516 | instance" } 5. Create the RFC, specifying the EnableTermProCFNRfc file and the EnableTermProCFNParams file: aws amscm create-rfc --cli-input-json file://EnableTermProCFNRfc.json --execution- parameters file://EnableTermProCFNParams.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. Standard Stacks Version April 22, 2025 1800 AMS Advanced Change Type Reference AMS Advanced Change Type Details Tips Note There is a related CT for Amazon EC2, EC2 stack: Updating termination protection. To learn more about termination protection, see Protecting a stack from being deleted. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-2uzbqr7x7mekd. Example: Required Parameters Example not available. Example: All Parameters { "DocumentName": "AWSManagedServices-ManageResourceTerminationProtection", "Region": "eu-west-1", "Parameters": { "ResourceId": ["stack-1234567890abcd"], "TerminationProtectionDesiredState": ["enabled"] } } Trusted Remediator Subcategory Change Type Items and Operations in the Trusted Remediator Subcategory • Finding | Remediate • Remediation Configuration | Update • State | Enable or Disable Finding | Remediate Run the SSM automation document associated with an OpsItem to remediate a Trusted Advisor finding. This change type only supports OpsItems created by the Trusted Remediator service. The Trusted Remediator Version April 22, 2025 1801 AMS Advanced Change Type Reference AMS Advanced Change Type Details OpsItem must have been created within the last 90 days. For OpsItems older than 90 days, use a Management/Other/Other/Update change type. Full classification: Management | Trusted Remediator | Finding | Remediate Change Type Details Change type ID ct-1c7ch8z5phrjp Current version 1.0 Expected execution duration 360 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Remediate Trusted Remediator finding Remediate Trusted Remediator finding with the Console Screenshot of this change type in the AMS console: How it works: Trusted Remediator Version April 22, 2025 1802 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Remediate Trusted Remediator finding with the CLI 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. Trusted Remediator Version April 22, 2025 1803 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 |
ams-ct-517 | ams-ct.pdf | 517 | --rfc-id ID command with the returned RFC ID. Trusted Remediator Version April 22, 2025 1803 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-1c7ch8z5phrjp" --change-type-version "1.0" --title "Remediate TA finding" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-RemediateTrustedRemediatorFinding\",\"Region\":\"us-east-1\", \"Parameters\":{\"OpsItemId\":\"oi-1234567890ab\"}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it TRFindingRemediateParams.json: aws amscm get-change-type-version --change-type-id "ct-1c7ch8z5phrjp" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TRFindingRemediateParams.json Trusted Remediator Version April 22, 2025 1804 AMS Advanced Change Type Reference AMS Advanced Change Type Details Modify and save the TRFindingRemediateParams file. For example, you can replace the contents with something like this: { "DocumentName" : "AWSManagedServices-RemediateTrustedRemediatorFinding", "Region" : "us-east-1", "Parameters" : { "OpsItemId" : "oi-1234567890ab" } } 2. Output the RFC template to a file in your current folder; this example names it TFindingRemediateRfc.json: aws amscm create-rfc --generate-cli-skeleton > TRFindingRemediateRfc.json 3. Modify and save the TRFindingRemediateRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-1c7ch8z5phrjp", "ChangeTypeVersion": "1.0", "Title": Remediate Trusted Remediator Finding" } 4. Create the RFC, specifying the TRFindingRemediateRfc file and the TRFindingRemediateParams file: aws amscm create-rfc --cli-input-json file://TRFindingRemediateRfc.json -- execution-parameters file://TRFindingRemediateParams.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. Tips To learn more about Trusted Remediator see Trusted Remediator in AMS. Trusted Remediator Version April 22, 2025 1805 AMS Advanced Change Type Reference AMS Advanced Change Type Details Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-1c7ch8z5phrjp. Example: Required Parameters { "DocumentName" : "AWSManagedServices-RemediateTrustedRemediatorFinding", "Region" : "us-east-1", "Parameters" : { "OpsItemId" : "oi-1234567890ab" } } Example: All Parameters { "DocumentName" : "AWSManagedServices-RemediateTrustedRemediatorFinding", "Region" : "us-east-1", "Parameters" : { "OpsItemId" : "oi-1234567890ab", "RemediationDocumentName" : "AWSManagedServices-DeleteUnusedEBSVolume", "RemediationParameters" : "{\"Parameter1\":\"Value1\",\"Parameter2\":\"Value2\"}" } } Remediation Configuration | Update Request a Trusted Remediator configuration update. Use this change type in the Trusted Remediator delegated administrator account. The updated configuration is used for all member accounts. Full classification: Management | Trusted Remediator | Remediation configuration | Update Change Type Details Change type ID ct-3kl2d1u40lrj8 Current version 1.0 Trusted Remediator Version April 22, 2025 1806 AMS Advanced Change Type Reference AMS Advanced Change Type Details Expected execution duration 30 minutes AWS approval Required Customer approval Not required Execution mode Automated Additional Information Update Trusted Remediator remediation configuration Updating Trusted Remediator remediation configuration with the Console Screenshot of this change type in the AMS console: 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. Trusted Remediator Version April 22, 2025 1807 AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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, |
ams-ct-518 | ams-ct.pdf | 518 | AMS Advanced Change Type Reference AMS Advanced Change Type Details • 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. Updating Trusted Remediator configuration with the CLI 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 Trusted Remediator Version April 22, 2025 1808 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-3kl2d1u40lrj8" --change-type-version "1.0" --title "Configure Trusted Remediator" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-UpdateTrustedRemediatorConfiguration\",\"Region\":\"us-east-1\", \"Parameters\":{\"TACheckIDs\":[\"DAvU99Dc4C\",\"Hs4Ma3G104\"],\"ExecutionMode\": \"Manual\",\"AutomatedForTaggedOnly\":\"{\\\"tag_key1\\\":\\\"tag_value1\\\",\\ \"tag_key2\\\":\\\"tag_value2\\\"}\",\"ManualForTaggedOnly\":\"{\\\"tag_key3\\\":\\ \"tag_value3\\\"}\",\"UpdateOnlyIfNoFindings\":true}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it TrustedRemediatorConfigUpdateParams.json: aws amscm get-change-type-version --change-type-id "ct-0qyuzz7hbonc1" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TrustedRemediatorConfigUpdateParams.json Modify and save the TrustedRemediatorConfigUpdateParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-UpdateTrustedRemediatorConfiguration", "Region": "us-east-1", "Parameters": { "TACheckIDs": ["DAvU99Dc4C", "Hs4Ma3G104"], "ExecutionMode": "Manual", "AutomatedForTaggedOnly": "{\"tag_key1\":\"tag_value1\",\"tag_key2\": \"tag_value2\"}", Trusted Remediator Version April 22, 2025 1809 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ManualForTaggedOnly": "{\"tag_key3\":\"tag_value3\"}", "UpdateOnlyIfNoFindings": true } } 2. Output the RFC template to a file in your current folder; this example names it TrustedRemediatorConfigUpdateRfc.json: aws amscm create-rfc --generate-cli-skeleton > TrustedRemediatorConfigUpdateRfc.json 3. Modify and save the TrustedRemediatorConfigUpdateRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-3kl2d1u40lrj8", "ChangeTypeVersion": "1.0", "Title": "Update Trusted Remediator Configuration" } 4. Create the RFC, specifying the TrustedRemediatorConfigUpdateRfc file and the TrustedRemediatorConfigUpdateParams file: aws amscm create-rfc --cli-input-json file://TrustedRemediatorConfigUpdateRfc.json --execution-parameters file://TrustedRemediatorConfigUpdateParams.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. Tips To learn more about Trusted Remediator see Trusted Remediator in AMS. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-3kl2d1u40lrj8. Example: Required Parameters { Trusted Remediator Version April 22, 2025 1810 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName": "AWSManagedServices-UpdateTrustedRemediatorConfiguration", "Region": "us-east-1", "Parameters": { "TACheckIDs": ["DAvU99Dc4C", "Hs4Ma3G104"], "ExecutionMode": "Manual", "UpdateOnlyIfNoFindings": true } } Example: All Parameters { "DocumentName": "AWSManagedServices-UpdateTrustedRemediatorConfiguration", "Region": "us-east-1", "Parameters": { "TACheckIDs": ["DAvU99Dc4C", "Hs4Ma3G104"], "ExecutionMode": "Manual", "AutomatedForTaggedOnly": "{\"key1\":\"value1\",\"key2\":\"value2\"}", "ManualForTaggedOnly": "{\"key3\":\"key4\"}", "UpdateOnlyIfNoFindings": true } } State | Enable or Disable Enable or disable the Trusted Remediator service. Can only be used in the Trusted Remediator delegated administrator account. When disabled, remediations are not performed in all member accounts. Full classification: Management | Trusted Remediator | State | Enable or disable Change Type Details Change type ID ct-10nh4ztyxu8kz Current version 1.0 Expected execution duration 30 minutes AWS approval Required Trusted Remediator Version April 22, 2025 1811 AMS Advanced Change Type Reference AMS Advanced Change Type Details Customer approval Not required Execution mode Automated Additional Information |
ams-ct-519 | ams-ct.pdf | 519 | "Hs4Ma3G104"], "ExecutionMode": "Manual", "AutomatedForTaggedOnly": "{\"key1\":\"value1\",\"key2\":\"value2\"}", "ManualForTaggedOnly": "{\"key3\":\"key4\"}", "UpdateOnlyIfNoFindings": true } } State | Enable or Disable Enable or disable the Trusted Remediator service. Can only be used in the Trusted Remediator delegated administrator account. When disabled, remediations are not performed in all member accounts. Full classification: Management | Trusted Remediator | State | Enable or disable Change Type Details Change type ID ct-10nh4ztyxu8kz Current version 1.0 Expected execution duration 30 minutes AWS approval Required Trusted Remediator Version April 22, 2025 1811 AMS Advanced Change Type Reference AMS Advanced Change Type Details Customer approval Not required Execution mode Automated Additional Information Enable or disable Trusted Remediator Enable or disable Trusted Remediator with the Console Screenshot of this change type in the AMS console: 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. Trusted Remediator Version April 22, 2025 1812 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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. Enable or disable Trusted Remediator with the CLI 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 Trusted Remediator Version April 22, 2025 1813 AMS Advanced Change Type Reference AMS Advanced Change Type Details 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 --change-type-id "ct-10nh4ztyxu8kz" --change-type-version "1.0" --title "Stop Trusted Remediator" --execution-parameters "{\"DocumentName\": \"AWSManagedServices-EnableOrDisableTrustedRemediator\",\"Region\":\"us-east-1\", \"Parameters\":{\"ServiceState\":\"DISABLE\"}}" TEMPLATE CREATE: 1. Output the execution parameters JSON schema for this change type to a file; this example names it TRDisableParams.json: aws amscm get-change-type-version --change-type-id "ct-10nh4ztyxu8kz" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TRDisableParams.json Modify and save the TRDisableParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-EnableOrDisableTrustedRemediator", "Region": "us-east-1", "Parameters": { "ServiceState": "DISABLE" } } 2. Output the RFC template to a file in your current folder; this example names it TRDisableRfc.json: aws amscm create-rfc --generate-cli-skeleton > TRDisableRfc.json Trusted Remediator Version April 22, 2025 1814 AMS Advanced Change Type Reference AMS Advanced Change Type Details 3. Modify and save |
ams-ct-520 | ams-ct.pdf | 520 | the execution parameters JSON schema for this change type to a file; this example names it TRDisableParams.json: aws amscm get-change-type-version --change-type-id "ct-10nh4ztyxu8kz" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > TRDisableParams.json Modify and save the TRDisableParams file. For example, you can replace the contents with something like this: { "DocumentName": "AWSManagedServices-EnableOrDisableTrustedRemediator", "Region": "us-east-1", "Parameters": { "ServiceState": "DISABLE" } } 2. Output the RFC template to a file in your current folder; this example names it TRDisableRfc.json: aws amscm create-rfc --generate-cli-skeleton > TRDisableRfc.json Trusted Remediator Version April 22, 2025 1814 AMS Advanced Change Type Reference AMS Advanced Change Type Details 3. Modify and save the TRDisableRfc.json file. For example, you can replace the contents with something like this: { "ChangeTypeId": "ct-10nh4ztyxu8kz", "ChangeTypeVersion": "1.0", "Title": Stop Trusted Remediator" } 4. Create the RFC, specifying the TRDisableRfc file and the TRDisableParams file: aws amscm create-rfc --cli-input-json file://TRDisableRfc.json --execution- parameters file://TRDisableParams.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. Tips To learn more about Trusted Remediator see Trusted Remediator in AMS. Execution Input Parameters For detailed information about the execution input parameters, see Schema for Change Type ct-10nh4ztyxu8kz. Example: Required Parameters { "DocumentName" : "AWSManagedServices-EnableOrDisableTrustedRemediator", "Region" : "us-east-1", "Parameters" : { "ServiceState" : "DISABLE" } } Example: All Parameters { "DocumentName" : "AWSManagedServices-EnableOrDisableTrustedRemediator", "Region" : "us-east-1", Trusted Remediator Version April 22, 2025 1815 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Parameters" : { "ServiceState" : "DISABLE" } } Trusted Remediator Version April 22, 2025 1816 AMS Advanced Change Type Reference AMS Advanced Change Type Details Change Type Schemas Change type schemas specify the execution input parameters for a change type. Schema for Change Type ct-00tlkda4242x7 Classifications: • Deployment | Applications | CodeDeploy deployment group | Create (for EC2 instance) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create CodeDeploy deployment group for EC2 instance as target.", "description": "Create an AWS CodeDeploy application deployment group specifically for an EC2 instance as target. Tags you create in the EC2 instances, and specify here (EC2FilterTag1, 2, and 3), mark the instances as targets for the deployment group. A name for the deployment group is automatically generated.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource.", "type": "array", ct-00tlkda4242x7 Version April 22, 2025 1817 AMS Advanced Change Type Reference AMS Advanced Change Type Details "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 50, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-n3hsoirgqeqqdbpk2", "type": "string", "enum": [ "stm-n3hsoirgqeqqdbpk2" ], "default": "stm-n3hsoirgqeqqdbpk2" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, ct-00tlkda4242x7 Version April 22, 2025 1818 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maximum": 60, "default": 60 }, "Parameters": { "type": "object", "properties": { "ApplicationName": { "type": "string", "description": "The name of an existing AWS CodeDeploy application within your AMS account.", "pattern": "^[a-zA-Z0-9._+=,@-]{1,100}$" }, "DeploymentConfigName": { "type": "string", "description": "The configuration for deployment operations. To deploy as many instances as possible at once, use CodeDeployDefault.AllAtOnce. To deploy half of the instances at a time, use CodeDeployDefaultHalfAtATime. To deploy only one instance at a time, use CodeDeployDefault.OneAtATime.", "enum": [ "CodeDeployDefault.AllAtOnce", "CodeDeployDefault.HalfAtATime", "CodeDeployDefault.OneAtATime" ], "default": "CodeDeployDefault.OneAtATime" }, "AutoRollbackEnabled": { "type": "string", "description": "True to enable an automatic rollback of a deployment if it fails; if that happens, CodeDeploy redeploys the last known good revision as a new deployment. False to not enable the automatic rollback.", "enum": [ "True", "False" ], "default": "False" }, "EC2FilterTag": { "type": "string", "description": "Key=Value pair tag for CodeDeploy to filter EC2 instances; for example Name=Application01. The specified tag is used to identify instances as targets for the deployment group.", "pattern": "^([a-zA-Z0-9\\s_.=+/:-]{0,127})=([a-zA-Z0-9\\s_.=+/:-]{0,255})$" }, "EC2FilterTag2": { ct-00tlkda4242x7 Version April 22, 2025 1819 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "Second Key=Value pair tag for CodeDeploy to filter EC2 instances; for example Environment=Test01. The specified tag is used to identify instances as targets for the deployment group.", "pattern": "^([a-zA-Z0-9\\s_.=+/:-]{0,127})=([a-zA-Z0-9\\s_.=+/:-]{0,255})$|^ |
ams-ct-521 | ams-ct.pdf | 521 | deployment. False to not enable the automatic rollback.", "enum": [ "True", "False" ], "default": "False" }, "EC2FilterTag": { "type": "string", "description": "Key=Value pair tag for CodeDeploy to filter EC2 instances; for example Name=Application01. The specified tag is used to identify instances as targets for the deployment group.", "pattern": "^([a-zA-Z0-9\\s_.=+/:-]{0,127})=([a-zA-Z0-9\\s_.=+/:-]{0,255})$" }, "EC2FilterTag2": { ct-00tlkda4242x7 Version April 22, 2025 1819 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "Second Key=Value pair tag for CodeDeploy to filter EC2 instances; for example Environment=Test01. The specified tag is used to identify instances as targets for the deployment group.", "pattern": "^([a-zA-Z0-9\\s_.=+/:-]{0,127})=([a-zA-Z0-9\\s_.=+/:-]{0,255})$|^ $", "default": "" }, "EC2FilterTag3": { "type": "string", "description": "Third Key=Value pair tag for CodeDeploy to filter EC2 instances; for example Version=Latest. The specified tag is used to identify instances as targets for the deployment group.", "pattern": "^([a-zA-Z0-9\\s_.=+/:-]{0,127})=([a-zA-Z0-9\\s_.=+/:-]{0,255})$|^ $", "default": "" }, "ServiceRoleArn": { "type": "string", "description": "The Amazon Resource Name (ARN) of an existing CodeDeploy service role that grants permission to make calls to AWS services on your behalf, in the form arn:aws:iam::ACCOUNT_ID:role/aws-codedeploy-role. If blank arn:aws:iam::ACCOUNT_ID:role/aws-codedeploy-role is used.", "pattern": "^$|^arn:aws:iam::[0-9]{12}:role/[\\w-]+$", "default": "" } }, "metadata": { "ui:order": [ "ApplicationName", "DeploymentConfigName", "AutoRollbackEnabled", "EC2FilterTag", "EC2FilterTag2", "EC2FilterTag3", "ServiceRoleArn" ] }, "required": [ "ApplicationName", "EC2FilterTag" ], "additionalProperties": false } ct-00tlkda4242x7 Version April 22, 2025 1820 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "metadata": { "ui:order": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } Schema for Change Type ct-00zr0b0ozlcn3 Classifications: • Management | Advanced stack components | S3 storage | Receive replication replica { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Receive Replication Replica", "description": "Receive S3 object replicas in the destination bucket.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-ReceiveReplicationReplica.", "type": "string", "enum": [ "AWSManagedServices-ReceiveReplicationReplica" ], "default": "AWSManagedServices-ReceiveReplicationReplica" ct-00zr0b0ozlcn3 Version April 22, 2025 1821 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "Region": { "description": "The AWS Region in which the destination account is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "DestinationBucketName": { "description": "The destination S3 bucket name.", "type": "array", "items": { "type": "string", "pattern": "^[a-z0-9]([-.a-z0-9]+)[a-z0-9]$", "minLength": 3, "maxLength": 63 }, "maxItems": 1 }, "SourceBucketName": { "description": "The source S3 bucket name.", "type": "array", "items": { "type": "string", "pattern": "^[a-z0-9]([-.a-z0-9]+)[a-z0-9]$", "minLength": 3, "maxLength": 63 }, "maxItems": 1 }, "ReplicationRole": { "description": "The ARN of the role that allows S3 to perform the replication on your behalf.", "type": "array", "items": { "type": "string", "pattern": "^arn:aws:iam::[0-9]{12}:role/[A-Za-z0-9_\\-/]+$" }, "maxItems": 1 }, "EncryptReplicaKMSKey": { "description": "The KMS key used to encrypt destination objects.", ct-00zr0b0ozlcn3 Version April 22, 2025 1822 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "pattern": "^(arn:aws:kms:[a-z0-9-]+:[0-9]{12}:key/){0,1}[a-f0-9]{8}-[a- f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}$|^$", "default": "" }, "maxItems": 1 }, "OwnerTranslation": { "description": "True to change replica ownership to the AWS account that owns the destination bucket, false to not change replica ownership. This parameter cannot be left blank.", "type": "array", "items": { "type": "string", "enum": [ "true", "false" ], "default": "false" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "DestinationBucketName", "SourceBucketName", "ReplicationRole", "EncryptReplicaKMSKey", "OwnerTranslation" ] }, "additionalProperties": false, "required": [ "DestinationBucketName", "SourceBucketName", "ReplicationRole" ] } }, "metadata": { ct-00zr0b0ozlcn3 Version April 22, 2025 1823 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0176f0n99vcps Classifications: • Deployment | Advanced stack components | Tag | Create (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Resource Tags (Review Required)", "description": "Add tags to existing, supported resources except those in AMS infrastructure stacks (stacks named mc-*). Tags simplify categorization, identification and targeting AWS resources. For Autoscaling, EC2, Elastic Load Balancing, RDS resources and S3 buckets, use the automated CT ct-3cx7we852p3af.", "type": "object", "properties": { "Resources": { "description": "Parameters for up to fifty resources that you want to tag.", "type": "array", "items": { "type": "object", "properties": { "ResourceArn": { "description": "The ARN or the resource ID of the resource to be tagged. Resource ID is allowed only for these resource types: EC2 instance, EBS volume, EBS snapshot, AMI, and security group. All other resource types must be provided with the full ARN.", "type": "string", ct-0176f0n99vcps Version April 22, 2025 1824 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^arn:aws:(|[a-z][a-z0-9-]+):(|[a-z]{2}((-gov)|(-iso(b?)))?-[a- z]+-\\d{1}):(|[0-9]{12}):([^,\\s]+)$|^(ami|i|vol|sg|snap)-([a-f0-9]{8}|[a-f0-9]{17})$" }, "AddOrUpdateTags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource. If the tag exists, the value for it is overwritten. If the tag does not exist, it is added to the resource. Characters allowed in tags can vary by AWS service. For information about what characters can be used to tag resources in a particular AWS service, please refer to its documentation. In general, allowed characters in |
ams-ct-522 | ams-ct.pdf | 522 | types must be provided with the full ARN.", "type": "string", ct-0176f0n99vcps Version April 22, 2025 1824 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^arn:aws:(|[a-z][a-z0-9-]+):(|[a-z]{2}((-gov)|(-iso(b?)))?-[a- z]+-\\d{1}):(|[0-9]{12}):([^,\\s]+)$|^(ami|i|vol|sg|snap)-([a-f0-9]{8}|[a-f0-9]{17})$" }, "AddOrUpdateTags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource. If the tag exists, the value for it is overwritten. If the tag does not exist, it is added to the resource. Characters allowed in tags can vary by AWS service. For information about what characters can be used to tag resources in a particular AWS service, please refer to its documentation. In general, allowed characters in tags are letters, numbers, spaces and the following characters: _ . : / = + - @.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^(?![aA][mMwW][sS]:)[a-zA-Z0-9\\s_.:/=+\\\\\\-@\\]*]+$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_.:/=+\\\\\\-@\\]*]+$", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 50, "uniqueItems": true } ct-0176f0n99vcps Version April 22, 2025 1825 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "additionalProperties": false, "metadata": { "ui:order": [ "ResourceArn", "AddOrUpdateTags" ] }, "required": [ "ResourceArn", "AddOrUpdateTags" ] }, "minItems": 1, "maxItems": 50, "uniqueItems": true }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "Resources", "Priority" ] }, "required": [ "Resources" ] } ct-0176f0n99vcps Version April 22, 2025 1826 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-01zl37gmuk4q2 Classifications: • Management | Advanced stack components | Identity and Access Management (IAM) | Delete SAML identity provider { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete SAML Identity Provider", "description": "Delete a SAML identity provider (IdP). The given IdP must not be referenced in any IAM role and must not be the only IdP in the account.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-HandleDeleteSamlProvider-Admin", "type": "string", "enum": [ "AWSManagedServices-HandleDeleteSamlProvider-Admin" ], "default": "AWSManagedServices-HandleDeleteSamlProvider-Admin" }, "Region": { "description": "The AWS Region of the account, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "Name": { "description": "The name of the SAML IdP.", "type": "array", "items": { "type": "string", "pattern": "^[\\w._-]{1,128}$" }, "minItems": 1, "maxItems": 1 }, "MetadataBackup": { ct-01zl37gmuk4q2 Version April 22, 2025 1827 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "True for a backup of the SAML provider metadata to be taken before deleting, False for no backup to be taken. Default is True.", "type": "array", "items": { "type": "string", "default": "True", "enum": [ "True", "False" ] }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "Name", "MetadataBackup" ] }, "required": [ "Name" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } ct-01zl37gmuk4q2 Version April 22, 2025 1828 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-02ocqy2i0jx3t Classifications: • Management | Advanced stack components | RDS database stack | Start Aurora cluster { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Start Aurora DB Cluster", "description": "Start an Aurora DB cluster, which is a provisioned capacity type and does not have cross-region read replicas. The cluster must be in the 'stopped' state.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-StartDBCluster.", "type": "string", "enum": [ "AWSManagedServices-StartDBCluster" ], "default": "AWSManagedServices-StartDBCluster" }, "Region": { "description": "The AWS Region where the cluster is.", "type": "string", "enum": [ "us-east-1", "us-east-2", "us-west-1", "us-west-2", "eu-west-1", "eu-west-2", "eu-west-3", "eu-south-1", "eu-north-1", "eu-central-1", "ca-central-1", "ap-southeast-1", "ap-southeast-2", "ap-southeast-3", "ap-south-1", "ap-northeast-1", ct-02ocqy2i0jx3t Version April 22, 2025 1829 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ap-northeast-2", "ap-northeast-3", "ap-east-1", "sa-east-1", "me-south-1", "af-south-1", "us-gov-west-1", "us-gov-east-1", "cn-northwest-1", "cn-north-1" ] }, "Parameters": { "type": "object", "properties": { "DBClusterIdentifier": { "description": "The unique RDS DB cluster identifier.", "type": "string", "pattern": "^[a-zA-Z]{1}(?!.*--)(?!.*-$)[A-Za-z0-9-]{0,62}$|^$" } }, "metadata": { "ui:order": [ "DBClusterIdentifier" ] }, "additionalProperties": false, "required": [ "DBClusterIdentifier" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ct-02ocqy2i0jx3t Version April 22, 2025 1830 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] } Schema for Change Type ct-02u0hoaa9grat Classifications: • Management | Standard stacks | Stack | Reboot { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Reboot stack", "description": "Use to reboot all running EC2 and RDS DB instances in the specified stack.", "additionalProperties": false, "type": "object", "properties": { "StackId": { "pattern": "^stack-[a-z0-9]{17}$", "description": "The ID of the stack to reboot, in the form stack- a1b2c3d4e5f67890e. All running EC2 and RDS DB instances in the stack are rebooted.", "type": "string" } }, "required": [ "StackId" ] } Schema for Change Type ct-03ms1d7xrck8w Classifications: • Management | |
ams-ct-523 | ams-ct.pdf | 523 | Advanced Change Type Reference AMS Advanced Change Type Details ] } Schema for Change Type ct-02u0hoaa9grat Classifications: • Management | Standard stacks | Stack | Reboot { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Reboot stack", "description": "Use to reboot all running EC2 and RDS DB instances in the specified stack.", "additionalProperties": false, "type": "object", "properties": { "StackId": { "pattern": "^stack-[a-z0-9]{17}$", "description": "The ID of the stack to reboot, in the form stack- a1b2c3d4e5f67890e. All running EC2 and RDS DB instances in the stack are rebooted.", "type": "string" } }, "required": [ "StackId" ] } Schema for Change Type ct-03ms1d7xrck8w Classifications: • Management | Advanced stack components | EC2 instance stack | Update termination protection { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Termination Protection", "description": "Update existing defined termination protection for EC2 instances.", ct-02u0hoaa9grat Version April 22, 2025 1831 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices- ManageResourceTerminationProtection.", "type": "string", "enum": [ "AWSManagedServices-ManageResourceTerminationProtection" ], "default": "AWSManagedServices-ManageResourceTerminationProtection" }, "Region": { "description": "The AWS Region in which the EC2 instance is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "ResourceId": { "description": "EC2 instance ID.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-z0-9]{8,17}$" }, "maxItems": 1 }, "TerminationProtectionDesiredState": { "description": "Enabled to protect your instance against elimination. Disabled to allow your instance to be eliminated.", "type": "array", "items": { "type": "string", "enum": [ "enabled", "disabled" ] }, "maxItems": 1 } }, "metadata": { ct-03ms1d7xrck8w Version April 22, 2025 1832 AMS Advanced Change Type Details AMS Advanced Change Type Reference "ui:order": [ "ResourceId", "TerminationProtectionDesiredState" ] }, "additionalProperties": false, "required": [ "ResourceId", "TerminationProtectionDesiredState" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-03t7kvuwx6rgr Classifications: • Management | Advanced stack components | EC2 instance stack | Start { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Start EC2 Instances", "description": "Start up to 50 stopped EC2 instances.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-StartInstances.", "type": "string", ct-03t7kvuwx6rgr Version April 22, 2025 1833 AMS Advanced Change Type Reference AMS Advanced Change Type Details "enum": [ "AWSManagedServices-StartInstances" ], "default": "AWSManagedServices-StartInstances" }, "Region": { "description": "The AWS Region where the instances are, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "InstanceIds": { "description": "A list of up to 50 EC2 instance IDs, in the form i-1234567890abcdef0 or i-b188560f.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-f0-9]{8}$|^i-[a-f0-9]{17}$" }, "minItems": 1, "maxItems": 50, "uniqueItems": true } }, "metadata": { "ui:order": [ "*" ] }, "additionalProperties": false, "required": [ "InstanceIds" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, ct-03t7kvuwx6rgr Version April 22, 2025 1834 AMS Advanced Change Type Reference AMS Advanced Change Type Details "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-03ytgoevfebjr Classifications: • Management | Directory Service | DNS | Update cluster permissions { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Cluster Permissions", "description": "Grants full control to the Cluster object on the Listener object to bring the SQL Server Listener object online. For multi-account landing zone (MALZ), use this change type in the shared services account.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-UpdateClusterDNSPermission-Admin.", "type": "string", "enum": [ "AWSManagedServices-UpdateClusterDNSPermission-Admin" ], "default": "AWSManagedServices-UpdateClusterDNSPermission-Admin" }, "Region": { "description": "The AWS Region where the Microsoft AD in Directory Service is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "ClusterName": { "description": "The name of the Cluster record in DNS.", "type": "array", ct-03ytgoevfebjr Version April 22, 2025 1835 AMS Advanced Change Type Reference "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\-\\_\\-]{1,15}$" }, "minItems": 1, "maxItems": 1 }, "ClusterNodeComputerName": { AMS Advanced Change Type Details "description": "The name of the Cluster object that is granted permissions to the Cluster DNS record.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\-\\_\\-]{1,15}$" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "ClusterName", "ClusterNodeComputerName" ] }, "additionalProperties": false, "required": [ "ClusterName", "ClusterNodeComputerName" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ct-03ytgoevfebjr Version April 22, 2025 1836 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] } Schema for Change Type ct-042luqo63j4mx Classifications: • Management | AMS Resource Scheduler | Period | Delete { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete Resource Scheduler Period", "description": "Delete an existing period used in AMS Resource Scheduler.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-DeleteScheduleOrPeriod.", "type": "string", "enum": [ "AWSManagedServices-DeleteScheduleOrPeriod" ], "default": "AWSManagedServices-DeleteScheduleOrPeriod" }, "Region": { "description": "The AWS Region of the account where the AMS Resource Scheduler solution is, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "ConfigurationType": { "description": "Specify the value: period. This explicitly requests that the Resource |
ams-ct-524 | ams-ct.pdf | 524 | Details ] } Schema for Change Type ct-042luqo63j4mx Classifications: • Management | AMS Resource Scheduler | Period | Delete { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete Resource Scheduler Period", "description": "Delete an existing period used in AMS Resource Scheduler.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-DeleteScheduleOrPeriod.", "type": "string", "enum": [ "AWSManagedServices-DeleteScheduleOrPeriod" ], "default": "AWSManagedServices-DeleteScheduleOrPeriod" }, "Region": { "description": "The AWS Region of the account where the AMS Resource Scheduler solution is, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "ConfigurationType": { "description": "Specify the value: period. This explicitly requests that the Resource Scheduler period be deleted. The option cannot be left blank; it must be period.", "type": "array", "items": { "type": "string", "enum": [ "period" ], ct-042luqo63j4mx Version April 22, 2025 1837 AMS Advanced Change Type Reference AMS Advanced Change Type Details "default": "period" }, "maxItems": 1, "minItems": 1 }, "Name": { "description": "The name of the period to delete.", "type": "array", "items": { "type": "string", "pattern": "(?!^[-_, +=.:#/@])^[A-Za-z0-9-_, +=.:#/@]{1,64}$" }, "maxItems": 1, "minItems": 1 } }, "metadata": { "ui:order": [ "ConfigurationType", "Name" ] }, "required": [ "ConfigurationType", "Name" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } ct-042luqo63j4mx Version April 22, 2025 1838 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-046aizcwg5idf Classifications: • Deployment | Advanced stack components | AMI | Copy { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Copy AMI", "description": "Copy an Amazon Machine Image (AMI) in your AMS account.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-CopyAMI.", "type": "string", "enum": [ "AWSManagedServices-CopyAMI" ], "default": "AWSManagedServices-CopyAMI" }, "Region": { "description": "The AWS Region to copy the AMI to, in the form us-east-1. This must be the account's default AWS Region.", "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "Name": { "description": "A name for the new AMI.", "type": "array", "items": { "type": "string", "pattern": "^[A-Za-z0-9\\-\\/\\(\\)_.\\ ]{3,128}$" }, "minItems": 1, "maxItems": 1 }, "SourceImageId": { "description": "The ID of the AMI to copy.", "type": "array", ct-046aizcwg5idf Version April 22, 2025 1839 AMS Advanced Change Type Reference "items": { "type": "string", "pattern": "^ami-[a-f0-9]{8}$|^ami-[a-f0-9]{17}$" AMS Advanced Change Type Details }, "minItems": 1, "maxItems": 1 }, "SourceRegion": { "description": "The ID of the AWS Region that contains the source AMI, in the form us-east-1.", "type": "array", "items": { "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "minItems": 1, "maxItems": 1 }, "Encrypted": { "description": "True to encrypt the snapshot of the destination AMI. The default customer master key (CMK) for Amazon Elastic Block Store (EBS) is used unless you specify a non-default AWS Key Management Service (KMS) CMK using the KmsKeyId parameter. False to not encrypt the snapshot. Default is False.", "type": "array", "items": { "type": "string", "default": "False", "enum": [ "True", "False" ] }, "minItems": 1, "maxItems": 1 }, "KmsKeyId": { "description": "The KMS key to encrypt the snapshot of the destination AMI. Specify the KMS Key ARN or the KMS key identifier. If left blank and the snapshot of the source AMI is encrypted, the snapshot of the target AMI is encrypted using the default EBS KMS key.", "type": "array", "items": { "type": "string", "default": "", ct-046aizcwg5idf Version April 22, 2025 1840 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^(arn:aws:kms:[a-z0-9-]+:[0-9]{12}:key/){0,1}[a-f0-9]{8}-[a- f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}$|^$" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "Name", "SourceImageId", "SourceRegion", "Encrypted", "KmsKeyId" ] }, "additionalProperties": false, "required": [ "Name", "SourceImageId", "SourceRegion" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } ct-046aizcwg5idf Version April 22, 2025 1841 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-04gzyy008v1bg Classifications: • Management | Advanced stack components | KMS alias | Delete { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete KMS Alias", "description": "Delete an alias of an AWS Key Management Service (KMS) customer master key (CMK).", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-DeleteKMSAlias.", "type": "string", "enum": [ "AWSManagedServices-DeleteKMSAlias" ], "default": "AWSManagedServices-DeleteKMSAlias" }, "Region": { "description": "The AWS Region in which the AWS resource is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "AliasName": { "description": "Name of the alias to be deleted. Do not specify the prefix alias/, it will be added during the execution.", "type": "array", "items": { "type": "string", "pattern": "^(?!alias/)(?!aws/)[a-zA-Z0-9/_-]{1,250}$" }, "minItems": 1, "maxItems": 1 } }, ct-04gzyy008v1bg Version April 22, 2025 1842 AMS Advanced Change Type Reference AMS Advanced Change Type Details "metadata": { "ui:order": [ "AliasName" ] }, "required": [ "AliasName" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-059ewa92tc2i1 Classifications: • Management | Advanced stack |
ams-ct-525 | ams-ct.pdf | 525 | "properties": { "AliasName": { "description": "Name of the alias to be deleted. Do not specify the prefix alias/, it will be added during the execution.", "type": "array", "items": { "type": "string", "pattern": "^(?!alias/)(?!aws/)[a-zA-Z0-9/_-]{1,250}$" }, "minItems": 1, "maxItems": 1 } }, ct-04gzyy008v1bg Version April 22, 2025 1842 AMS Advanced Change Type Reference AMS Advanced Change Type Details "metadata": { "ui:order": [ "AliasName" ] }, "required": [ "AliasName" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-059ewa92tc2i1 Classifications: • Management | Advanced stack components | EBS snapshot | Archive { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Archive EBS Snapshots", "description": "Archive Elastic Block Store (EBS) snapshots. The maximum number of EBS snapshots that can be archived concurrently depends on the 'In-progress snapshot archives per account' AWS Service Quota. Snapshots that are in the 'completed' state, storage tier is 'standard', or belonging to the current owner account, can be archived. Snapshots created by the AWS Backup service, used by AMIs, or shared with other accounts, cannot be archived. If you specify snapshots that are invalid, or the archival in-progress quota limit is reached, the RFC fails.", ct-059ewa92tc2i1 Version April 22, 2025 1843 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-ArchiveEBSSnapshots.", "type": "string", "enum": [ "AWSManagedServices-ArchiveEBSSnapshots" ], "default": "AWSManagedServices-ArchiveEBSSnapshots" }, "Region": { "description": "The AWS Region to use, in the form us-east-1.", "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "SnapshotIds": { "description": "A comma-separated list of the EBS snapshots to archive. The maximum number of in-progress snapshot archives per account can be checked through the AWS Service Quotas console (search: In-progress snapshot archives per account).", "type": "array", "items": { "type": "string", "pattern": "^snap-[0-9a-f]{8}$|^snap-[0-9a-f]{17}$" }, "minItems": 1, "maxItems": 100 } }, "metadata": { "ui:order": [ "SnapshotIds" ] }, "additionalProperties": false, "required": [ "SnapshotIds" ] } }, "metadata": { "ui:order": [ ct-059ewa92tc2i1 Version April 22, 2025 1844 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-05muqzievnxk5 Classifications: • Deployment | Advanced stack components | Database Migration Service (DMS) | Create target endpoint (S3) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create DMS target endpoint for S3", "description": "Use to create a Database Migration Service (DMS) target endpoint for S3.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { ct-05muqzievnxk5 Version April 22, 2025 1845 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to 40 tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 40, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-knghtmmgefafdq89u", "type": "string", ct-05muqzievnxk5 Version April 22, 2025 1846 AMS Advanced Change Type Reference AMS Advanced Change Type Details "enum": [ "stm-knghtmmgefafdq89u" ], "default": "stm-knghtmmgefafdq89u" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 60, "default": 60 }, "Parameters": { "type": "object", "properties": { "EndpointIdentifier": { "type": "string", "description": "The identifier to be used for the target endpoint. This is a label for the endpoint to help you identify it. It must be unique for all endpoints owned by your AWS account in the current region. It must begin with a letter, must contain only ASCII letters, digits and hyphens and must not end with a hyphen or contain two consecutive hyphens.", "pattern": "^$|(?!.*--)[a-zA-Z][a-zA-Z0-9-]*[a-zA-Z0-9]$", "default": "" }, "EngineName": { "type": "string", "description": "Must be S3.", "enum": [ "s3" ], "default": "s3" }, "ExtraConnectionAttributes": { "type": "string", "description": "Additional attributes associated with the connection. For example, to specify a maximum file size of 512 KB of any CSV file created while migrating to S3 specify maxFileSize=512. See 'Targets for Data Migration' in AWS DMS documentation.", "default": "" }, "S3BucketFolder": { ct-05muqzievnxk5 Version April 22, 2025 1847 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The folder name in the S3 bucket. If provided, tables are created in the |
ams-ct-526 | ams-ct.pdf | 526 | "pattern": "^$|(?!.*--)[a-zA-Z][a-zA-Z0-9-]*[a-zA-Z0-9]$", "default": "" }, "EngineName": { "type": "string", "description": "Must be S3.", "enum": [ "s3" ], "default": "s3" }, "ExtraConnectionAttributes": { "type": "string", "description": "Additional attributes associated with the connection. For example, to specify a maximum file size of 512 KB of any CSV file created while migrating to S3 specify maxFileSize=512. See 'Targets for Data Migration' in AWS DMS documentation.", "default": "" }, "S3BucketFolder": { ct-05muqzievnxk5 Version April 22, 2025 1847 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The folder name in the S3 bucket. If provided, tables are created in the path <bucketFolder>/<schema_name>/<table_name>/ instead of <schema_name>/<table_name>/ within the bucket.", "default": "" }, "S3BucketName": { "type": "string", "description": "The name of the S3 bucket for the target endpoint. Must be in the same region as the DMS replication instance you are using to migrate data." }, "S3CompressionType": { "type": "string", "description": "If, and how, target files should be compressed. Use GZIP to compress the target files in the target endpoint. Use NONE for no file compression.", "enum": [ "GZIP", "NONE" ], "default": "NONE" }, "S3CsvDelimiter": { "type": "string", "description": "The delimiter used to separate columns in the target files. Leave blank to use the default comma (,) delimiter.", "default": "" }, "S3CsvRowDelimiter": { "type": "string", "description": "The delimiter used to separate rows in the source files. Leave blank to use the default carriage return (\\n) delimiter.", "default": "" }, "S3ServiceAccessRoleArn": { "type": "string", "description": "The Amazon Resource Name (ARN) of the service access IAM role.", "pattern": "^$|^arn:aws:iam::[0-9]{12}:role/[\\w-]+$" } }, "metadata": { "ui:order": [ "EndpointIdentifier", "EngineName", ct-05muqzievnxk5 Version April 22, 2025 1848 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ExtraConnectionAttributes", "S3BucketFolder", "S3BucketName", "S3CompressionType", "S3CsvDelimiter", "S3CsvRowDelimiter", "S3ServiceAccessRoleArn" ] }, "required": [ "EngineName", "S3BucketName", "S3ServiceAccessRoleArn" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Name", "Description", "VpcId", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } ct-05muqzievnxk5 Version April 22, 2025 1849 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-05yb337abq3x5 Classifications: • Management | Advanced stack components | KMS key | Share (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Share KMS Key", "description": "Allow cross-account access to a KMS key by adding a statement to the key policy with encrypt and decrypt permissions.", "type": "object", "properties": { "KMSKeyArn": { "description": "The Amazon Resource Name (ARN) of the KMS key, in the form arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab.", "type": "string", "pattern": "^(arn:aws:kms:[a-z0-9-]+:[0-9]{12}:key/){0,1}[a-f0-9]{8}-[a-f0-9]{4}- [a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}$" }, "TargetAccountId": { "description": "The ID of the AWS account that you want to share the KMS key with.", "type": "string", "pattern": "^[0-9]{12}$" }, "IncludeKeyGrantPermissions": { "description": "Add permissions for managing grants of the KMS key. These are required for performing tasks such as copying an encrypted AMI or snapshot.", "type": "boolean", "default": false }, "IAMUserOrRoleARN": { "description": "The ARN of an IAM Role or User in the target account to grant permission to. If no value is provided, the root principal of the target account is used.", "type": "string", "pattern": "^arn:(aws|aws-cn|aws-us-gov):iam::[0-9]{12}:(role|user)/[A-Za- z0-9_-]+$|^$", "default": "" }, "Priority": { ct-05yb337abq3x5 Version April 22, 2025 1850 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "KMSKeyArn", "IncludeKeyGrantPermissions", "TargetAccountId", "IAMUserOrRoleARN", "Priority" ] }, "required": [ "KMSKeyArn", "TargetAccountId" ] } Schema for Change Type ct-063qsm82cfxu6 Classifications: • Deployment | Advanced stack components | EBS Volume | Create from backup { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create EBS From Backup", "description": "Create an AWS Elastic Block Store (EBS) stack from backup.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-StartRestoreJobEBS.", "type": "string", "enum": [ ct-063qsm82cfxu6 Version April 22, 2025 1851 AMS Advanced Change Type Reference AMS Advanced Change Type Details "AWSManagedServices-StartRestoreJobEBS" ], "default": "AWSManagedServices-StartRestoreJobEBS" }, "Region": { "description": "The AWS Region in which the EBS snapshot is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "AvailabilityZone": { "description": "The Availability Zone in which to restore the EBS snapshot, in the form us-east-1a.", "type": "array", "items": { "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-[0-9]{1}[a-z]{1})$" }, "maxItems": 1 }, "BackupVaultName": { "description": "The name of a logical container where backups are stored. The backup vault name is case sensitive and must contain from 2 to 50 alphanumeric characters or hyphens.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\_\\-]{2,50}$" }, "maxItems": 1 }, "IOPS": { "description": "The requested number of I/O operations per second that the new EBS volume can support if VolumeType is io1, io2 or gp3. This value is ignored for other volume types. If VolumeType is gp3, then the IOPS should be between 3000 and 16000, else it should be between 100 and 64000. The IOPS |
ams-ct-527 | ams-ct.pdf | 527 | }, "BackupVaultName": { "description": "The name of a logical container where backups are stored. The backup vault name is case sensitive and must contain from 2 to 50 alphanumeric characters or hyphens.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\_\\-]{2,50}$" }, "maxItems": 1 }, "IOPS": { "description": "The requested number of I/O operations per second that the new EBS volume can support if VolumeType is io1, io2 or gp3. This value is ignored for other volume types. If VolumeType is gp3, then the IOPS should be between 3000 and 16000, else it should be between 100 and 64000. The IOPS must respect the max ratio of 50 IOPS per GiB.", "type": "array", "items": { "type": "string", ct-063qsm82cfxu6 Version April 22, 2025 1852 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^$|^([1-9][0-9]{2}|[1-9][0-9]{3}|[1-5][0-9][0-9]{3}|[6][0-3] [0-9]{3}|64000)$" }, "maxItems": 1 }, "Throughput": { "description": "The Throughput to use for the restored volume if VolumeType is gp3. If VolumeType is not gp3, any value provided here is ignored. The Throughput should be between 125 and 1000.", "type": "array", "items": { "type": "string", "pattern": "^$|^([1][2][5-9]$|[1][3-9][0-9]$|[2-9][0-9][0-9]$|1000)$" }, "maxItems": 1 }, "RecoveryPointArn": { "description": "The Amazon Resource Name (ARN) that uniquely identifies the recovery point to restore.", "type": "array", "items": { "type": "string", "pattern": "^arn:aws:([a-z][a-z0-9-]+):([a-z]{2}((-gov))?-[a-z]+-\\d{1}): [0-9]{0,12}:[a-zA-Z0-9\\_\\-\\/\\:]+$" }, "maxItems": 1 }, "VolumeSize": { "description": "The size of the volume, in GiBs. The volume size must be equal to or larger than the snapshot size. If not specified, the default will be the snapshot size. Valid values are between 1 and 16384.", "type": "array", "items": { "type": "string", "pattern": "^([1-9]|[1-8][0-9]|9[0-9]|[1-8][0-9]{2}|9[0-8][0-9]|99[0-9]| [1-8][0-9]{3}|9[0-8][0-9]{2}|99[0-8][0-9]|999[0-9]|1[0-5][0-9]{3}|16[0-2][0-9]{2}| 163[0-7][0-9]|1638[0-4])$" }, "maxItems": 1 }, "VolumeType": { "description": "The volume type for the restored volume. Choose io1, io2, gp2 or gp3 for SSD-backed volumes optimized for transactional workloads. Choose sc1 or st1 for HDD-backed volumes optimized for large streaming workloads. Choose standard for ct-063qsm82cfxu6 Version April 22, 2025 1853 AMS Advanced Change Type Reference AMS Advanced Change Type Details HDD-backed volumes suitable for workloads where data is infrequently accessed. If not specified gp3 will be used as default.", "type": "array", "items": { "type": "string", "default": "gp3", "pattern": "^(standard|io1|io2|gp2|gp3|sc1|st1)$" }, "maxItems": 1 } }, "metadata": { "ui:order": [ "AvailabilityZone", "BackupVaultName", "IOPS", "Throughput", "RecoveryPointArn", "VolumeSize", "VolumeType" ] }, "additionalProperties": false, "required": [ "AvailabilityZone", "BackupVaultName", "RecoveryPointArn" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] ct-063qsm82cfxu6 Version April 22, 2025 1854 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Schema for Change Type ct-06bwg93ukgg8t Classifications: • Deployment | Advanced stack components | VPC | Add static route (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Add Static Route", "description": "Create a static route on your route table inside a VPC.", "type": "object", "properties": { "RouteTableId": { "description": "The ID of the route table for the route, in the form of rtb-01234567890abcdef.", "type": "string", "pattern": "^rtb-[a-z0-9]{8,17}$" }, "Destination": { "description": "The IPv4 CIDR address block in the form 192.168.10.0/24 or the ID of a prefix list in the form pl-01234567890abcdef used for the destination match.", "type": "string", "pattern": "^(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])\\.){3}([0-9]|[1-9] [0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])(/(3[0-2]|[1-2][0-9]|[0-9]))$|^pl-[a-z0-9]{8,17}$" }, "RouteTableTarget": { "description": "The ID of the resource that will serve as the route table target. You must specify one of the following targets: internet gateway or virtual private gateway, NAT gateway or VPC peering connection.", "type": "string", "pattern": "^(vgw|igw|nat|tgw|pcx)-[a-z0-9]{8,17}$" }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ct-06bwg93ukgg8t Version April 22, 2025 1855 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] } }, "metadata": { "ui:order": [ "RouteTableId", "Destination", "RouteTableTarget", "Priority" ] }, "required": [ "RouteTableId", "Destination", "RouteTableTarget" ], "additionalProperties": false } Schema for Change Type ct-06mjngx5flwto Classifications: • Deployment | Standard stacks | High availability two-tier stack | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create high availability two-tier stack", "description": "Creates a stack consisting of an Auto Scaling group, an RDS DB instance, and a load balancer (ELB). Optionally allows for application deployment with CodeDeploy by also creating a CodeDeploy application and deployment group both named the value given for ApplicationName. All resource parameters can be configured.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "TimeoutInMinutes": { ct-06mjngx5flwto Version April 22, 2025 1856 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "default": 360 }, "VpcId": { "description": "The ID of the VPC to create the Auto Scaling group in, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": |
ams-ct-528 | ams-ct.pdf | 528 | information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "TimeoutInMinutes": { ct-06mjngx5flwto Version April 22, 2025 1856 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "default": 360 }, "VpcId": { "description": "The ID of the VPC to create the Auto Scaling group in, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack; this becomes the searchable stack name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to forty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,255}$", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "required": [ "Key", "Value" ] }, "minItems": 0, ct-06mjngx5flwto Version April 22, 2025 1857 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maxItems": 40, "uniqueItems": true }, "AutoScalingGroup": { "description": "Specifications for the application tier.", "type": "object", "properties": { "AmiId": { "description": "The AMI ID for the Auto Scaling Group to utilize, in the form ami-0123abcd or ami-01234567890abcdef.", "type": "string", "pattern": "^ami-[a-z0-9]{8}$|^ami-[a-z0-9]{17}$" }, "Cooldown": { "description": "The number of seconds after a scaling activity is completed before any further scaling activities can start.", "type": "integer", "minimum": 120, "maximum": 600, "default": 300 }, "DesiredCapacity": { "description": "The number of EC2 instances you want running in the group. This number must be greater than or equal to the MinInstances setting and less than or equal to the MaxInstances setting.", "type": "integer", "minimum": 1, "maximum": 1000, "default": 2 }, "EBSOptimized": { "description": "True to create EBS-optimized instances, false to not. EBS-optimization provides dedicated throughput to Amazon EBS and optimal EBS I/O performance.", "type": "boolean", "default": false }, "HealthCheckGracePeriod": { "description": "The amount of time, in seconds, that Auto Scaling waits before checking the health status of an EC2 instance that has come into service. During this time, any health check failures for the instance are ignored.", "type": "integer", "minimum": 600, "maximum": 1800, ct-06mjngx5flwto Version April 22, 2025 1858 AMS Advanced Change Type Reference AMS Advanced Change Type Details "default": 1800 }, "IAMInstanceProfile": { "description": "The IAM instance profile for the Auto Scaling group. EC2 instances launched with an IAM role automatically have AWS security credentials available.", "type": "string", "default": "customer-mc-ec2-instance-profile" }, "InstanceDetailedMonitoring": { "description": "True to enable detailed monitoring on the instances in the Auto Scaling group, false to use only basic monitoring.", "type": "boolean", "default": true }, "InstanceRootVolumeIops": { "description": "The Iops to use for the root volume if io1 volume type is specified.", "type": "integer", "minimum": 0, "maximum": 20000, "default": 0 }, "InstanceRootVolumeName": { "description": "The name of the root volume to use. Defaults to /dev/xvda for Linux, and /dev/sda for Windows.", "type": "string" }, "InstanceRootVolumeSize": { "description": "The size of the root volume for the instance. Defaults to 20 GiB for Linux, and 60 GiB for Windows.", "type": "integer", "minimum": 8, "maximum": 16000 }, "InstanceRootVolumeType": { "description": "Choose io1 or gp2 for SSD-backed volumes optimized for transactional workloads; choose standard for HDD-backed volumes optimized for large streaming workloads.", "type": "string", "enum": [ "standard", "io1", "gp2" ct-06mjngx5flwto Version April 22, 2025 1859 AMS Advanced Change Type Reference AMS Advanced Change Type Details ], "default": "standard" }, "InstanceType": { "description": "The instance type for the Auto Scaling group to use when creating new EC2 instances.", "type": "string", "default": "m4.large" }, "MaxInstances": { "description": "The maximum number of instances you want in the Auto Scaling group at any time.", "type": "integer", "minimum": 1, "maximum": 1000, "default": 2 }, "MinInstances": { "description": "The minimum number of instances you want in the Auto Scaling group at any time.", "type": "integer", "minimum": 1, "maximum": 1000, "default": 2 }, "ScaleDownPolicyCooldown": { "description": "The number of seconds after a scale-down activity is completed before any further scaling activities can start.", "type": "integer", "minimum": 120, "maximum": 600, "default": 300 }, "ScaleDownPolicyEvaluationPeriods": { "description": "The number of periods over which data is compared to the specified ScaleMetricName threshold.", "type": "integer", "minimum": 2, "default": 4 }, "ScaleDownPolicyPeriod": { "description": "The time over which the specified ScaleDownPolicyStatistic is applied. You must specify a time in seconds that is a multiple of 60.", "type": "integer", ct-06mjngx5flwto Version April 22, 2025 1860 AMS Advanced Change Type Reference AMS Advanced Change Type Details "multipleOf": 60, "minimum": 60, "default": 60 }, "ScaleDownPolicyScalingAdjustment": { "description": "The number of instances by which to scale down.", "type": "integer", "maximum": 0, "default": -1 }, "ScaleDownPolicyStatistic": { "description": "The statistic to apply to the alarm's ScaleMetricName.", "type": "string", "enum": [ "SampleCount", "Average", "Sum", "Minimum", "Maximum" |
ams-ct-529 | ams-ct.pdf | 529 | the specified ScaleMetricName threshold.", "type": "integer", "minimum": 2, "default": 4 }, "ScaleDownPolicyPeriod": { "description": "The time over which the specified ScaleDownPolicyStatistic is applied. You must specify a time in seconds that is a multiple of 60.", "type": "integer", ct-06mjngx5flwto Version April 22, 2025 1860 AMS Advanced Change Type Reference AMS Advanced Change Type Details "multipleOf": 60, "minimum": 60, "default": 60 }, "ScaleDownPolicyScalingAdjustment": { "description": "The number of instances by which to scale down.", "type": "integer", "maximum": 0, "default": -1 }, "ScaleDownPolicyStatistic": { "description": "The statistic to apply to the alarm's ScaleMetricName.", "type": "string", "enum": [ "SampleCount", "Average", "Sum", "Minimum", "Maximum" ], "default": "Average" }, "ScaleDownPolicyThreshold": { "description": "The value against which the specified ASGScaleDownPolicyStatistic is compared.", "type": "number", "default": 35 }, "ScaleMetricName": { "description": "The metric to use in a scaling event. Exceeding the metric triggers an alarm.", "type": "string", "enum": [ "CPUCreditUsage", "CPUCreditBalance", "CPUUtilization", "DiskReadOps", "DiskWriteOps", "DiskReadBytes", "DiskWriteBytes", "NetworkIn", "NetworkOut", "StatusCheckFailed", "StatusCheckFailed_Instance", ct-06mjngx5flwto Version April 22, 2025 1861 AMS Advanced Change Type Reference AMS Advanced Change Type Details "StatusCheckFailed_System" ], "default": "CPUUtilization" }, "ScaleUpPolicyCooldown": { "description": "The amount of time, in seconds, after a scale-up activity is completed before any further trigger-related scaling activities can start.", "type": "integer", "minimum": 60, "default": 60 }, "ScaleUpPolicyEvaluationPeriods": { "description": "The number of periods over which data is compared to the specified ScaleMetricName threshold.", "type": "integer", "minimum": 2, "default": 2 }, "ScaleUpPolicyPeriod": { "description": "The time over which the specified ScaleUpPolicyStatistic is applied. You must specify a time in seconds that is a multiple of 60.", "type": "integer", "multipleOf": 60, "minimum": 60, "default": 60 }, "ScaleUpPolicyScalingAdjustment": { "description": "The number of instances by which to scale up.", "type": "integer", "minimum": 0, "default": 2 }, "ScaleUpPolicyStatistic": { "description": "The statistic to apply to the alarm's ScaleMetricName.", "type": "string", "enum": [ "SampleCount", "Average", "Sum", "Minimum", "Maximum" ], "default": "Average" }, ct-06mjngx5flwto Version April 22, 2025 1862 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ScaleUpPolicyThreshold": { "description": "The value against which the specified ScaleUpPolicyStatistic is compared.", "type": "number", "default": 75 }, "SubnetIds": { "description": "One or more subnets for the Auto Scaling group to launch instances into (scale up) or remove instances from (scale down), in the form subnet-0123abcd or subnet-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 1, "maxItems": 2, "uniqueItems": true }, "UserData": { "description": "A comma-delimited list where each element is a line of script to be run on boot.", "type": "array", "items": { "type": "string" }, "minItems": 1, "default": [ "" ] } }, "additionalProperties": false, "required": [ "AmiId", "SubnetIds" ] }, "LoadBalancer": { "description": "Specifications for the load-balancing tier.", "type": "object", "properties": { "SubnetIds": { ct-06mjngx5flwto Version April 22, 2025 1863 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "One or more subnet IDs for the load balancer, in the form subnet-0123abcd or subnet-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 1, "uniqueItems": true }, "HealthCheckInterval": { "description": "The approximate interval, in seconds, between health checks.", "type": "number", "minimum": 5, "maximum": 300, "default": 30 }, "HealthCheckTarget": { "description": "Specifies the instance being checked. The protocol can be TCP, HTTP, HTTPS, or SSL. The range of valid ports is 1 through 65535. For example, HTTP:80/", "type": "string", "pattern": "^(HTTP|HTTPS):[0-9]{1,5}[/][a-zA-Z0-9/_.-]*$|^(SSL|TCP):[0-9] {1,5}$" }, "HealthCheckTimeout": { "description": "The amount of time, in seconds, to wait for a response to a health check. Must be less than the value for HealthCheckInterval.", "type": "number", "minimum": 2, "maximum": 60, "default": 5 }, "Public": { "description": "True if the load balancer endpoint is public, false if it is not. Default is false. Set to true if you choose a public subnet for the load balancer.", "type": "boolean", "default": false }, "AccessCIDRRange": { "default": "0.0.0.0/0", ct-06mjngx5flwto Version April 22, 2025 1864 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "IPv4 CIDR block that the load balancer can receive traffic from.", "type": "string" } }, "additionalProperties": false, "required": [ "SubnetIds" ] }, "Database": { "description": "Specifications for the RDS DB instance.", "type": "object", "properties": { "AllocatedStorage": { "description": "The amount of storage (in gigabytes) to be initially allocated for the database (DB) instance.", "type": "number", "minimum": 5, "maximum": 6144 }, "BackupRetentionPeriod": { "description": "The number of days for which automatic DB snapshots are retained. Setting this to a positive number enables backups. Setting this to 0 disables automated backups.", "type": "number", "minimum": 0, "maximum": 35, "default": 7 }, "Backups": { "description": "True if the RDS instance should have automatic backups, false if it should not. Default is true.", "type": "boolean", "default": true }, "DBEngine": { "description": "The name of the database engine for the DB instance. Not every database engine is available for every AWS region.", "type": "string", "enum": [ "MySQL", "oracle-se1", "oracle-se", ct-06mjngx5flwto Version April 22, 2025 1865 AMS Advanced Change Type Reference AMS Advanced |
ams-ct-530 | ams-ct.pdf | 530 | days for which automatic DB snapshots are retained. Setting this to a positive number enables backups. Setting this to 0 disables automated backups.", "type": "number", "minimum": 0, "maximum": 35, "default": 7 }, "Backups": { "description": "True if the RDS instance should have automatic backups, false if it should not. Default is true.", "type": "boolean", "default": true }, "DBEngine": { "description": "The name of the database engine for the DB instance. Not every database engine is available for every AWS region.", "type": "string", "enum": [ "MySQL", "oracle-se1", "oracle-se", ct-06mjngx5flwto Version April 22, 2025 1865 AMS Advanced Change Type Reference AMS Advanced Change Type Details "oracle-ee", "sqlserver-ee", "sqlserver-se", "sqlserver-ex", "sqlserver-web", "postgres" ] }, "DBName": { "default": "main", "description": "A name for the database. The meaning of this parameter differs according to the database engine you use.", "type": "string", "minLength": 1 }, "EngineVersion": { "description": "The version number of the database engine to use.", "type": "string" }, "InstanceType": { "description": "The compute and memory capacity for the DB instance.", "type": "string", "enum": [ "db.m3.medium", "db.m3.large", "db.m3.xlarge", "db.m3.2xlarge", "db.r3.large", "db.r3.xlarge", "db.r3.2xlarge", "db.r3.4xlarge", "db.r3.8xlarge", "db.t2.micro", "db.t2.small", "db.t2.medium", "db.t3.large", "db.t3.xlarge", "db.t3.2xlarge" ], "default": "db.m3.medium" }, "IOPS": { "description": "The provisioned IOPS for RDS storage. Must be a multiple between 3 and 10 of the storage amount for the DB instance. Must also be an integer ct-06mjngx5flwto Version April 22, 2025 1866 AMS Advanced Change Type Reference AMS Advanced Change Type Details multiple of 1000. For example, if the size of your DB instance is 500 GB, then your Iops value can be 2000, 3000, 4000, or 5000.", "type": "number", "default": 0 }, "LicenseModel": { "description": "License model information for this DB instance.", "type": "string", "enum": [ "bring-your-own-license", "general-public-license", "license-included", "postgresql-license" ] }, "MasterUsername": { "description": "The username that you will use with the configured MasterUserPassword to log in to your DB instance. Must begin with a letter and contain only alphanumeric characters.", "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9]{1,127}$" }, "MasterUserPassword": { "description": "The password that you will use with the configured MasterUserName to log in to your DB instance. Must contain from 8 to 30 printable ASCII alphanumeric characters (excluding backslash, double quotes, and at sign).", "type": "string", "pattern": "^[!#-.0-?A-~]{8,30}$", "metadata": { "ams:sensitive": true } }, "MultiAZ": { "description": "True to have a standby replica of your DB instance created in another Availability Zone for failover support, false to not have a standby replica. Default is true.", "type": "boolean", "default": true }, "PreferredBackupWindow": { "description": "The daily time range during which automated backups are created if BackupRetentionPeriod is set to a positive number. Must be in the format hh:mm-hh:mm (24-hour format), in Universal Coordinated Time (UTC). Must not conflict with the PreferredMaintenanceWindow setting, and must be at least 30 minutes.", ct-06mjngx5flwto Version April 22, 2025 1867 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "default": "22:00-23:00", "pattern": "^(0[0-9]|1[0-9]|2[0-3]):[0-5][0-9]-(0[0-9]|1[0-9]|2[0-3]):[0-5] [0-9]$" }, "Port": { "description": "The port number on which the database accepts connections. Defaults vary by DB engine.", "type": "number" }, "PreferredMaintenanceWindow": { "description": "The weekly time range (in UTC) during which system maintenance can occur.", "type": "string", "default": "wed:03:32-wed:04:02", "pattern": "^(mon|tues|wed|thurs|fri|sat|sun):(0[0-9]|1[0-9]|2[0-3]):[0-5] [0-9]-(mon|tues|wed|thurs|fri|sat|sun):(0[0-9]|1[0-9]|2[0-3]):[0-5][0-9]$" }, "StorageEncrypted": { "description": "True to enable database encryption, false to not. Default is false.", "type": "boolean", "default": false }, "StorageEncryptionKey": { "description": "The ARN of the custom KMS key to encrypt the database if StorageEncrypted = true. If StorageEncrypted = true and you do not specify a StorageEncryptionKey, RDS uses your default encryption key, which AWS KMS creates. Your AWS account has a different default encryption key for each AWS region.", "type": "string", "default": "" }, "StorageType": { "description": "Storage type for the RDS instance. If you specify io1, you must also include a value for the IOPS parameter.", "type": "string", "enum": [ "standard", "gp2", "io1" ], "default": "gp2" }, "SubnetIds": { ct-06mjngx5flwto Version April 22, 2025 1868 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Subnet IDs for the RDS instance, in the form subnet-0123abcd or subnet-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 2, "maxItems": 20, "uniqueItems": true } }, "additionalProperties": false, "required": [ "DBName", "DBEngine", "EngineVersion", "LicenseModel", "MasterUsername", "MasterUserPassword", "SubnetIds" ] }, "Application": { "description": "Optional parameters for including an application to deploy with CodeDeploy. Given a unique ID if none is provided.", "type": "object", "properties": { "ApplicationName": { "description": "The name of an AWS CodeDeploy application.", "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[a-zA-Z0-9._+=,@-]{1,100}$" }, "DeploymentConfigName": { "description": "The configuration for deployment operations: as many instances as possible at once, half of the instances at a time, or only one instance at a time.", "type": "string", "enum": [ "CodeDeployDefault.AllAtOnce", "CodeDeployDefault.HalfAtATime", "CodeDeployDefault.OneAtATime" ct-06mjngx5flwto Version April 22, 2025 1869 AMS Advanced Change Type Reference AMS Advanced Change Type Details ], "default": "CodeDeployDefault.OneAtATime" } }, "additionalProperties": false }, "EnforceIMDSv2": { "description": "For the instance |
ams-ct-531 | ams-ct.pdf | 531 | deploy with CodeDeploy. Given a unique ID if none is provided.", "type": "object", "properties": { "ApplicationName": { "description": "The name of an AWS CodeDeploy application.", "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[a-zA-Z0-9._+=,@-]{1,100}$" }, "DeploymentConfigName": { "description": "The configuration for deployment operations: as many instances as possible at once, half of the instances at a time, or only one instance at a time.", "type": "string", "enum": [ "CodeDeployDefault.AllAtOnce", "CodeDeployDefault.HalfAtATime", "CodeDeployDefault.OneAtATime" ct-06mjngx5flwto Version April 22, 2025 1869 AMS Advanced Change Type Reference AMS Advanced Change Type Details ], "default": "CodeDeployDefault.OneAtATime" } }, "additionalProperties": false }, "EnforceIMDSv2": { "description": "For the instance to be launched with only Instance Metadata Service Version 2 (IMDSv2), use required; if IMDSv2 is not required, use optional. Default is optional.", "type": "string", "default": "optional" } }, "additionalProperties": false, "required": [ "Description", "Name", "LoadBalancer", "AutoScalingGroup", "Database", "VpcId", "TimeoutInMinutes" ] } Schema for Change Type ct-07jzw8bzd2on7 Classifications: • Management | Monitoring and notification | GuardDuty IP set | Update (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update GuardDuty IPSet", "description": "Use to update an Amazon GuardDuty IPSet instance which is a list of trusted IP addresses that have been whitelisted for highly secure communication with your AWS environment.", "type": "object", "properties": { "Activate": { "description": "Specified whether the IPSet is active or not.", ct-07jzw8bzd2on7 Version April 22, 2025 1870 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "boolean", "default": true }, "DetectorId": { "description": "The detector ID that specifies the GuardDuty service to which you want to update an IPSet. Leave this blank to use the only detector in the selected region (this will not succeed if there is more than one detector in the selected region).", "pattern": "^[a-fA-F0-9]{32}$|^$", "type": "string" }, "IpSet": { "description": "The URI of the file that contains the IPSet.", "minLength": 1, "type": "string" }, "IpSetId": { "description": "The unique ID that specifies the IPSet that you want to update.", "type": "string", "minLength": 1 }, "Name": { "description": "The friendly name to identify the IPSet. This name is displayed in all findings that are triggered by activity that involves IP addresses included in this IPSet.", "minLength": 1, "type": "string" }, "Region": { "description": "The region containing the GuardDuty detector to use; in the form of us-east-1.", "minLength": 1, "type": "string" }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] ct-07jzw8bzd2on7 Version April 22, 2025 1871 AMS Advanced Change Type Reference AMS Advanced Change Type Details } }, "metadata": { "ui:order": [ "Region", "IpSetId", "Name", "IpSet", "Activate", "DetectorId", "Priority" ] }, "additionalProperties": false, "required": [ "IpSetId", "Region" ] } Schema for Change Type ct-08avsj2e9mc7g Classifications: • Deployment | Monitoring and notification | GuardDuty IP set | Create (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create GuardDuty IPSet", "description": "Use to create an Amazon GuardDuty IPSet instance which is a list of trusted IP addresses that have been whitelisted for highly secure communication with your AWS environment.", "type": "object", "properties": { "Activate": { "description": "Specified whether the IPSet is active or not.", "type": "boolean", "default": true }, "DetectorId": { ct-08avsj2e9mc7g Version April 22, 2025 1872 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The detector ID that specifies the GuardDuty service to which you want to add an IPSet. Leave this blank to use the only detector in the selected region (this will not succeed if there is more than one detector in the selected region).", "pattern": "^[a-fA-F0-9]{32}$|^$", "type": "string" }, "Format": { "default": "TXT", "description": "The format of the file that contains the IPSet.", "enum": [ "TXT", "STIX", "OTX_CSV", "ALIEN_VAULT", "PROOF_POINT", "FIRE_EYE" ], "type": "string" }, "Name": { "description": "The friendly name to identify the IPSet. This name is displayed in all findings that are triggered by activity that involves IP addresses included in this IPSet.", "minLength": 1, "type": "string" }, "IpSet": { "description": "The URI of the file that contains the IPSet.", "minLength": 1, "type": "string" }, "Region": { "description": "The region containing the GuardDuty detector to use; in the form of us-east-1.", "minLength": 1, "type": "string" }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", ct-08avsj2e9mc7g Version April 22, 2025 1873 AMS Advanced Change Type Reference AMS Advanced Change Type Details "High" ] } }, "metadata": { "ui:order": [ "Region", "Name", "IpSet", "Format", "Activate", "DetectorId", "Priority" ] }, "additionalProperties": false, "required": [ "Name", "IpSet", "Region" ] } Schema for Change Type ct-08sgdn5zowyyl Classifications: • Management | Host security | Trend Micro DSM | Scan and get results (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Trend Micro Scan Report", "description": "Request a Trend Micro on-demand scan on all, or specified, Amazon Elastic Compute Cloud (EC2) instances |
ams-ct-532 | ams-ct.pdf | 532 | a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", ct-08avsj2e9mc7g Version April 22, 2025 1873 AMS Advanced Change Type Reference AMS Advanced Change Type Details "High" ] } }, "metadata": { "ui:order": [ "Region", "Name", "IpSet", "Format", "Activate", "DetectorId", "Priority" ] }, "additionalProperties": false, "required": [ "Name", "IpSet", "Region" ] } Schema for Change Type ct-08sgdn5zowyyl Classifications: • Management | Host security | Trend Micro DSM | Scan and get results (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Trend Micro Scan Report", "description": "Request a Trend Micro on-demand scan on all, or specified, Amazon Elastic Compute Cloud (EC2) instances in the account and get scan results in the form of a PDF attached in the response.", "type": "object", "properties": { "Region": { "description": "The AWS Region where the EC2 instances are located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" ct-08sgdn5zowyyl Version April 22, 2025 1874 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "Parameters": { "type": "object", "properties": { "InstanceIds": { "description": "The instance IDs to scan for the report, in the form i- ab12cd34 or i-ab12cd3456789efgh. To scan all instances in the account, use ALL.", "type": "array", "items": { "type": "string", "pattern": "^ALL$|^i-[a-zA-Z0-9]{8}$|^i-[a-zA-Z0-9]{17}$" }, "minItems": 1, "maxItems": 50, "uniqueItems": true } }, "metadata": { "ui:order": [ "InstanceIds" ] }, "additionalProperties": false, "required": [ "InstanceIds" ] }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "metadata": { "ui:order": [ "Region", "Parameters", "Priority" ] ct-08sgdn5zowyyl Version April 22, 2025 1875 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "additionalProperties": false, "required": [ "Region" ] } Schema for Change Type ct-09qbhy7kvtxqw Classifications: • Management | Advanced stack components | EC2 instance stack | Reboot { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Reboot EC2 instance", "description": "Use to reboot an EC2 instance.", "additionalProperties": false, "type": "object", "properties": { "InstanceId": { "pattern": "^i-[a-zA-Z0-9]{8}$|^i-[a-zA-Z0-9]{17}$", "description": "ID of the instance to reboot, in the form i-12345678901234567 or i-1234567.", "type": "string" } }, "required": [ "InstanceId" ] } Schema for Change Type ct-09t6q7j9v5hrn Classifications: • Deployment | Standard stacks | High availability one-tier stack | Create { ct-09qbhy7kvtxqw Version April 22, 2025 1876 AMS Advanced Change Type Reference AMS Advanced Change Type Details "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create high availability one-tier stack", "description": "Use to create an Application Load Balancer and an Auto Scaling Group.", "type": "object", "properties": { "DatabaseStackId": { "description": "Stack ID of the database to use, in the form stack-1ab2cd3456789101.", "type": "string", "pattern": "^stack-[0-9a-z]{17}$" }, "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to forty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,255}$", "minLength": 1, "maxLength": 255 } }, ct-09t6q7j9v5hrn Version April 22, 2025 1877 AMS Advanced Change Type Reference AMS Advanced Change Type Details "additionalProperties": false, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 40, "uniqueItems": true }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "default": 360 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "ApplicationLoadBalancer": { "description": "Specifications for the ALB.", "type": "object", "properties": { "HealthCheckHealthyThreshold": { "description": "The number of consecutive health check successes required to declare an EC2 instance healthy.", "type": "number", "minimum": 2, "maximum": 10, "default": 2 }, "HealthCheckIntervalInSeconds": { "description": "The amount of time, in seconds, between health checks.", "type": "number", "minimum": 5, "maximum": 300, "default": 10 }, "HealthCheckTargetPath": { "default": "/", ct-09t6q7j9v5hrn Version April 22, 2025 1878 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The ping path destination on the application hosts where the load balancer sends health check requests.", "type": "string" }, "HealthCheckTargetPort": { "description": "The port the load balancer uses when performing health checks on targets. The default is traffic-port, which indicates the port on which each target receives traffic from the load balancer.", "type": "number", "minimum": 1, "maximum": 65535 }, "HealthCheckTargetProtocol": { "default": "HTTP", "description": "The protocol the load balancer uses when performing health checks on targets.", "type": "string", "enum": [ "HTTP", "HTTPS" ] }, "HealthCheckTimeoutSeconds": { "description": "The amount of time, in seconds, to wait for a response to a health check. Must be less than the value for HealthCheckIntervalInSeconds.", "type": "number", "minimum": 2, "maximum": 60, "default": 5 |
ams-ct-533 | ams-ct.pdf | 533 | }, "HealthCheckTargetPort": { "description": "The port the load balancer uses when performing health checks on targets. The default is traffic-port, which indicates the port on which each target receives traffic from the load balancer.", "type": "number", "minimum": 1, "maximum": 65535 }, "HealthCheckTargetProtocol": { "default": "HTTP", "description": "The protocol the load balancer uses when performing health checks on targets.", "type": "string", "enum": [ "HTTP", "HTTPS" ] }, "HealthCheckTimeoutSeconds": { "description": "The amount of time, in seconds, to wait for a response to a health check. Must be less than the value for HealthCheckIntervalInSeconds.", "type": "number", "minimum": 2, "maximum": 60, "default": 5 }, "HealthCheckUnhealthyThreshold": { "description": "The number of consecutive health check failures required to declare an EC2 instance unhealthy.", "type": "number", "minimum": 2, "maximum": 10, "default": 2 }, "InstancePort": { "default": 80, "description": "The TCP port the listener uses to send traffic to the target instance.", "type": "number", "minimum": 1, ct-09t6q7j9v5hrn Version April 22, 2025 1879 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maximum": 65535 }, "InstanceProtocol": { "default": "HTTP", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "type": "string", "enum": [ "HTTP", "HTTPS", "TCP" ] }, "LoadBalancerCookieExpirationPeriodInSeconds": { "description": "The time period, in seconds, after which the cookie is considered stale. If this parameter isn't specified, the sticky session lasts for the duration of the browser session.", "type": "number" }, "LoadBalancerPort": { "default": 80, "description": "The port number for the load balancer to use when routing external incoming traffic.", "type": "number", "minimum": 1, "maximum": 65535 }, "LoadBalancerAccessCIDRRange": { "default": "0.0.0.0/0", "description": "IPv4 CIDR block that the load balancer can receive traffic from.", "type": "string" }, "LoadBalancerProtocol": { "default": "HTTP", "description": "The transport protocol to use for routing front-end connections (client to load balancer).", "type": "string", "enum": [ "HTTP", "HTTPS" ] }, "LoadBalancerSslPolicy": { ct-09t6q7j9v5hrn Version April 22, 2025 1880 AMS Advanced Change Type Reference AMS Advanced Change Type Details "default": "ELBSecurityPolicy-2016-08", "description": "The security policy that defines the ciphers and protocols that the load balancer supports. Only applies if ALBLoadBalancerProtocol = HTTPS.", "type": "string", "enum": [ "ELBSecurityPolicy-2016-08", "ELBSecurityPolicy-FS-2018-06", "ELBSecurityPolicy-TLS-1-2-2017-01", "ELBSecurityPolicy-TLS-1-2-Ext-2018-06", "ELBSecurityPolicy-TLS-1-1-2017-01", "ELBSecurityPolicy-2015-05", "ELBSecurityPolicy-TLS-1-0-2015-04", "ELBSecurityPolicy-FS-1-1-2019-08", "ELBSecurityPolicy-FS-1-2-2019-08", "ELBSecurityPolicy-FS-1-2-Res-2019-08", "ELBSecurityPolicy-FS-1-2-Res-2020-10" ] }, "Public": { "description": "True if the load balancer endpoint is public, false if it is not. Default is false.", "type": "boolean", "default": false }, "SSLCertificateId": { "description": "The Amazon Resource Name (ARN) of the SSL certificate to use, in the form arn:aws:acm:us-east-1:ACCOUNT- ID:certificate/12345678-1234-1234-1234-123456789012.", "type": "string" }, "SubnetIds": { "description": "Two or more subnet IDs for the load balancer, in the form subnet-0123abcd or subnet-01234567890abcdef, spanning at least two Availability Zones.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 2, "uniqueItems": true }, "ValidHTTPCode": { "default": "200", ct-09t6q7j9v5hrn Version April 22, 2025 1881 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The HTTP codes that a healthy target application server must use when responding to a health check, such as 200, 202 or 200-399.", "type": "string", "pattern": "^[1-5][0-9]{2}(-[1-5][0-9]{2})?$" } }, "additionalProperties": false, "required": [ "SubnetIds" ] }, "AutoScalingGroup": { "description": "Specifications for the ASG.", "type": "object", "properties": { "AmiId": { "description": "ID of the AMI for the Auto Scaling group to use when creating new instances, in the form ami-0123abcd or ami-01234567890abcdef.", "type": "string", "pattern": "^ami-[a-z0-9]{8}$|^ami-[a-z0-9]{17}$" }, "CooldownInSeconds": { "description": "The number of seconds after a scaling activity is complete before any further scaling activities can start.", "type": "integer", "minimum": 120, "maximum": 600, "default": 300 }, "DesiredCapacity": { "description": "The number of EC2 instances you want running in the group. This number must be greater than or equal to the MinInstances setting and less than or equal to the MaxInstances setting.", "type": "integer", "minimum": 1, "maximum": 1000, "default": 1 }, "EBSOptimized": { "description": "True to create EBS-optimized instances, false to not. EBS-optimization provides dedicated throughput to Amazon EBS and optimal EBS I/O performance.", "type": "boolean", "default": false ct-09t6q7j9v5hrn Version April 22, 2025 1882 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "HealthCheckGracePeriodInSeconds": { "description": "The amount of time, in seconds, that Auto Scaling waits before checking the health status of an EC2 instance that has come into service. During this time, any health check failures for the instance are ignored.", "type": "integer", "minimum": 600, "maximum": 1800, "default": 1800 }, "HealthCheckType": { "description": "The service to use for the health checks. The ELB Health Check Type includes EC2 instance and system status checks. If ASGHealthCheckType = ELB, ensure that your ASGHealthCheckGracePeriod value is long enough so that your instances are not terminated due to load-balancer health checks failing, before your application has been deployed.", "default": "EC2", "type": "string", "enum": [ "EC2", "ELB" ] }, "IAMInstanceProfile": { "description": "The IAM instance profile for the Auto Scaling group. EC2 instances launched with an IAM role automatically have AWS security credentials available.", "type": "string", "default": |
ams-ct-534 | ams-ct.pdf | 534 | "integer", "minimum": 600, "maximum": 1800, "default": 1800 }, "HealthCheckType": { "description": "The service to use for the health checks. The ELB Health Check Type includes EC2 instance and system status checks. If ASGHealthCheckType = ELB, ensure that your ASGHealthCheckGracePeriod value is long enough so that your instances are not terminated due to load-balancer health checks failing, before your application has been deployed.", "default": "EC2", "type": "string", "enum": [ "EC2", "ELB" ] }, "IAMInstanceProfile": { "description": "The IAM instance profile for the Auto Scaling group. EC2 instances launched with an IAM role automatically have AWS security credentials available.", "type": "string", "default": "customer-mc-ec2-instance-profile" }, "InstanceDetailedMonitoring": { "description": "True to enable detailed monitoring on the instances in the Auto Scaling group, false to use only basic monitoring.", "type": "boolean", "default": true }, "InstanceRootVolumeIops": { "description": "The IOPS to use for the root volume if io1 volume type is specified.", "type": "integer", "minimum": 0, "maximum": 20000, "default": 0 }, ct-09t6q7j9v5hrn Version April 22, 2025 1883 AMS Advanced Change Type Reference AMS Advanced Change Type Details "InstanceRootVolumeName": { "description": "The name of the root volume to use. Defaults to /dev/xvda for Linux, and /dev/sda for Windows.", "type": "string" }, "InstanceRootVolumeSizeInGiB": { "description": "The size of the root volume for the instance. Defaults to 20 GiB for Linux, and 60 GiB for Windows.", "type": "integer", "minimum": 8, "maximum": 1024 }, "InstanceRootVolumeType": { "description": "Choose io1, gp2 or gp3 for SSD-backed volumes optimized for transactional workloads; choose standard for HDD-backed volumes optimized for large streaming workloads.", "type": "string", "enum": [ "standard", "io1", "gp2", "gp3" ], "default": "standard" }, "InstanceType": { "description": "The instance type for the Auto Scaling group to use when creating new EC2 instances.", "type": "string", "default": "m4.large" }, "MaxInstances": { "description": "The maximum number of instances you want in the Auto Scaling group at any time.", "type": "integer", "minimum": 1, "maximum": 1000, "default": 1 }, "MinInstances": { "description": "The minimum number of instances you want in the Auto Scaling group at any time.", "type": "integer", "minimum": 1, ct-09t6q7j9v5hrn Version April 22, 2025 1884 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maximum": 1000, "default": 1 }, "ScaleMetricName": { "description": "The metric to use to in a scale-down event. Exceeding the metric triggers an alarm.", "type": "string", "enum": [ "CPUCreditUsage", "CPUCreditBalance", "CPUUtilization", "DiskReadOps", "DiskWriteOps", "DiskReadBytes", "DiskWriteBytes", "NetworkIn", "NetworkOut", "StatusCheckFailed", "StatusCheckFailed_Instance", "StatusCheckFailed_System" ], "default": "CPUUtilization" }, "ScaleDownPolicyCooldownInSeconds": { "description": "The number of seconds after a scale-down activity is completed before any further scaling activities can start.", "type": "integer", "minimum": 120, "maximum": 600, "default": 300 }, "ScaleDownPolicyEvaluationPeriods": { "description": "The number of periods over which data is compared to the specified ScaleMetricName threshold.", "type": "integer", "minimum": 2, "default": 4 }, "ScaleDownPolicyPeriod": { "description": "The time over which the specified ScaleDownPolicyStatistic is applied. You must specify a time in seconds that is a multiple of 60.", "type": "integer", "multipleOf": 60, "minimum": 60, ct-09t6q7j9v5hrn Version April 22, 2025 1885 AMS Advanced Change Type Reference AMS Advanced Change Type Details "default": 60 }, "ScaleDownPolicyScalingAdjustment": { "description": "The number of instances by which to scale down.", "type": "integer", "maximum": 0, "default": -1 }, "ScaleDownPolicyStatistic": { "description": "The statistic to apply to the alarm's ScaleDownMetricName.", "type": "string", "enum": [ "Average", "Maximum", "Minimum", "SampleCount", "Sum" ], "default": "Average" }, "ScaleDownPolicyThreshold": { "description": "The value against which the specified ScaleDownPolicyStatistic is compared.", "type": "number", "default": 35 }, "ScaleUpPolicyCooldownInSeconds": { "description": "The number of seconds after a scale-up activity is completed before any further scaling activities can start.", "type": "integer", "minimum": 120, "maximum": 600, "default": 300 }, "ScaleUpPolicyEvaluationPeriods": { "description": "The number of periods over which data is compared to the specified ScaleUpMetricName threshold.", "type": "integer", "minimum": 2, "default": 2 }, "ScaleUpPolicyPeriod": { "description": "The time over which the specified ScaleUpPolicyStatistic is applied. You must specify a time in seconds that is a multiple of 60.", ct-09t6q7j9v5hrn Version April 22, 2025 1886 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "integer", "multipleOf": 60, "minimum": 60, "default": 60 }, "ScaleUpPolicyScalingAdjustment": { "description": "The number of instances by which to scale up.", "type": "integer", "minimum": 0, "default": 2 }, "ScaleUpPolicyStatistic": { "description": "The statistic to apply to the alarm's ScaleMetricName.", "type": "string", "enum": [ "Average", "Maximum", "Minimum", "SampleCount", "Sum" ], "default": "Average" }, "ScaleUpPolicyThreshold": { "description": "The value against which the specified ScaleUpPolicyStatistic is compared.", "type": "number", "default": 75 }, "SubnetIds": { "description": "One or more subnets for the Auto Scaling group to launch instances into (scale up) or remove instances from (scale down), in the form subnet-0123abcd or subnet-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 1, "maxItems": 2, "uniqueItems": true }, "UserData": { ct-09t6q7j9v5hrn Version April 22, 2025 1887 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A comma-delimited list where each element is a line of script to be run on boot.", "type": |
ams-ct-535 | ams-ct.pdf | 535 | }, "ScaleUpPolicyThreshold": { "description": "The value against which the specified ScaleUpPolicyStatistic is compared.", "type": "number", "default": 75 }, "SubnetIds": { "description": "One or more subnets for the Auto Scaling group to launch instances into (scale up) or remove instances from (scale down), in the form subnet-0123abcd or subnet-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 1, "maxItems": 2, "uniqueItems": true }, "UserData": { ct-09t6q7j9v5hrn Version April 22, 2025 1887 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A comma-delimited list where each element is a line of script to be run on boot.", "type": "array", "items": { "type": "string" }, "minItems": 1, "default": [ "" ] } }, "additionalProperties": false, "required": [ "AmiId", "SubnetIds" ] } }, "additionalProperties": false, "required": [ "AutoScalingGroup", "ApplicationLoadBalancer", "Description", "Name", "TimeoutInMinutes", "VpcId" ] } Schema for Change Type ct-0ah3gwb9seqk2 Classifications: • Deployment | Applications | CodeDeploy application | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create CodeDeploy application", "description": "Use to create an AWS CodeDeploy application resource with the specified name.", "type": "object", ct-0ah3gwb9seqk2 Version April 22, 2025 1888 AMS Advanced Change Type Reference "properties": { "Description": { "description": "The reason for the request.", AMS Advanced Change Type Details "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "StackTemplateId": { "description": "Must be stm-sft6rv00000000000", "type": "string", "enum": [ "stm-sft6rv00000000000" ] }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to seven tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, ct-0ah3gwb9seqk2 Version April 22, 2025 1889 AMS Advanced Change Type Reference AMS Advanced Change Type Details "additionalProperties": false, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 7 }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 60 }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "CodeDeployApplicationName": { "description": "The name of an AWS CodeDeploy application.", "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[a-zA-Z0-9._+=,@-]{1,100}$" } }, "additionalProperties": false, "required": [ "CodeDeployApplicationName" ] } }, "additionalProperties": false, "required": [ "Description", "VpcId", "StackTemplateId", "Name", "TimeoutInMinutes", "Parameters" ] ct-0ah3gwb9seqk2 Version April 22, 2025 1890 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Schema for Change Type ct-0aqx5t0pgfzbg Classifications: • Management | Advanced stack components | Load balancer (ELB) stack | Replace listener certificate { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Replace ELB Listener Certificate", "description": "Replace the certificate of an existing Elastic (Classic) Load Balancer (ELB) listener. Use the RemediateDrift parameter to have the automation try to remediate the stack drift, if drift is introduced in the CloudFormation stack that was used to create the load balancer.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-SetClassicLoadBalancerCertificate.", "type": "string", "enum": [ "AWSManagedServices-SetClassicLoadBalancerCertificate" ], "default": "AWSManagedServices-SetClassicLoadBalancerCertificate" }, "Region": { "description": "The AWS Region where the ELB listener is located, in the form us- east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "LoadBalancerName": { "description": "The name of the Classic Load Balancer.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9][a-zA-Z0-9-]{1,30}[a-zA-Z0-9]$" ct-0aqx5t0pgfzbg Version April 22, 2025 1891 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "minItems": 1, "maxItems": 1 }, "SSLCertificateArn": { "description": "The Amazon Resource Name (ARN) of the certificate in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "type": "array", "items": { "type": "string", "pattern": "^arn:(aws|aws-cn|aws-us-gov):acm:[a-z]{2}-[a-z]+-[0-9]{1}:[0-9] {12}:certificate/[a-z0-9-]+$" }, "minItems": 1, "maxItems": 1 }, "LoadBalancerPort": { "description": "The listener port of the Classic Load Balancer.", "type": "array", "items": { "type": "string", "pattern": "^[0-9]{2,5}$" }, "minItems": 1, "maxItems": 1 }, "RemediateStackDrift": { "description": "True to initiate drift remediation, if any drift is caused by replacing the certificate on the Load Balancer listener. False to not attempt drift remediation. Drift remediation can be performed only on CloudFormation stacks that were created using a CT other than the Ingestion CT ct-36cn2avfrrj9v and that are in sync with the definitions in the stack template prior to setting certificate to the Load Balancer listener. Set to False to replace the certificate on the Load Balancer listener in an ingested stack if any drift introduced by the change is acceptable.", "type": "array", "items": { "type": "string", "default": "True", "enum": [ "True", "False" ] }, ct-0aqx5t0pgfzbg Version April 22, 2025 1892 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "LoadBalancerName", "SSLCertificateArn", "LoadBalancerPort", "RemediateStackDrift" ] }, "additionalProperties": false, "required": [ |
ams-ct-536 | ams-ct.pdf | 536 | the Ingestion CT ct-36cn2avfrrj9v and that are in sync with the definitions in the stack template prior to setting certificate to the Load Balancer listener. Set to False to replace the certificate on the Load Balancer listener in an ingested stack if any drift introduced by the change is acceptable.", "type": "array", "items": { "type": "string", "default": "True", "enum": [ "True", "False" ] }, ct-0aqx5t0pgfzbg Version April 22, 2025 1892 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "LoadBalancerName", "SSLCertificateArn", "LoadBalancerPort", "RemediateStackDrift" ] }, "additionalProperties": false, "required": [ "LoadBalancerName", "SSLCertificateArn" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0ary07xiajwx4 Classifications: • Deployment | Advanced stack components | Load balancer (ELB) stack | Create (with additional listeners) ct-0ary07xiajwx4 Version April 22, 2025 1893 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Load Balancer (ELB)", "description": "Create an Elastic (\"Classic\") load balancer (ELB).", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name used in the Console.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, ct-0ary07xiajwx4 Version April 22, 2025 1894 AMS Advanced Change Type Reference AMS Advanced Change Type Details "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 50, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-3tdleig07sbhstgnf", "type": "string", "enum": [ "stm-3tdleig07sbhstgnf" ], "default": "stm-3tdleig07sbhstgnf" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 60, "default": 60 }, "LoadBalancer": { "type": "object", "properties": { "Name": { "type": "string", "description": "A friendly name for the load balancer.", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,31}$|^$" }, "Scheme": { "type": "string", "description": "True if the load balancer endpoint is public, false if it is private.", ct-0ary07xiajwx4 Version April 22, 2025 1895 AMS Advanced Change Type Reference AMS Advanced Change Type Details "enum": [ "true", "false" ], "default": "false" }, "SecurityGroups": { "type": "array", "description": "A list of security groups to associate with the load balancer.", "items": { "type": "string", "pattern": "^sg-[a-z0-9]{8}$|^sg-[a-z0-9]{17}$" }, "minItems": 1, "maxItems": 5, "uniqueItems": true }, "SubnetIds": { "type": "array", "description": "A list of subnet IDs that the Elastic Load Balancing creates load balancer nodes in. For an Internet-facing load balancer provide a public subnet ID, for an internal load balancer we recommend private subnet IDs.", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "uniqueItems": true }, "AccessLogInterval": { "type": "string", "description": "The time interval, in minutes, to upload the load balancer access log to the specified S3 bucket. Defaults to 60 Minutes.", "enum": [ "5", "60" ], "default": "60" }, "ConnectionDrainingTimeout": { "type": "integer", "description": "The maximum time, in seconds, to keep the existing connections open before deregistering the instances.", "default": 60, ct-0ary07xiajwx4 Version April 22, 2025 1896 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minimum": 1, "maximum": 3600 }, "IdleTimeout": { "type": "integer", "description": "The time, in seconds, that a connection to the load balancer can remain idle (no data is sent over the connection). After the specified time, the load balancer closes the connection.", "default": 60, "minimum": 1, "maximum": 3600 }, "CrossZone": { "type": "string", "description": "True to enable cross-zone load balancing (the load balancer nodes route traffic to the back-end instances across all Availability Zones), false to disable. Default is true.", "enum": [ "true", "false" ], "default": "true" }, "HealthCheckHealthyThreshold": { "type": "string", "description": "The number of consecutive health probe successes required before moving the instance to the healthy state after it was moved to unhealthy.", "pattern": "[1-9]{1}[0-9]{0,1}", "default": "2" }, "HealthCheckInterval": { "type": "string", "description": "How often, in seconds, that health checks are run on an individual load balancer node.", "pattern": "[1-9]{1}[0-9]{0,3}", "default": "10" }, "HealthCheckTarget": { "type": "string", "description": "The protocol, port, and path of the instance to check. The protocol can be TCP, HTTP, HTTPS, or SSL and valid ports are 1 through 65535. For TCP/ SSL no path is required. For HTTP/HTTPS, you must include a ping path in the string. For example, HTTP:80/weather/us/wa/seattle.", "pattern": "(HTTP|HTTPS):[0-9]{1,5}[/][\\w./-]*|(SSL|TCP):[0-9]{1,5}", ct-0ary07xiajwx4 Version |
ams-ct-537 | ams-ct.pdf | 537 | before moving the instance to the healthy state after it was moved to unhealthy.", "pattern": "[1-9]{1}[0-9]{0,1}", "default": "2" }, "HealthCheckInterval": { "type": "string", "description": "How often, in seconds, that health checks are run on an individual load balancer node.", "pattern": "[1-9]{1}[0-9]{0,3}", "default": "10" }, "HealthCheckTarget": { "type": "string", "description": "The protocol, port, and path of the instance to check. The protocol can be TCP, HTTP, HTTPS, or SSL and valid ports are 1 through 65535. For TCP/ SSL no path is required. For HTTP/HTTPS, you must include a ping path in the string. For example, HTTP:80/weather/us/wa/seattle.", "pattern": "(HTTP|HTTPS):[0-9]{1,5}[/][\\w./-]*|(SSL|TCP):[0-9]{1,5}", ct-0ary07xiajwx4 Version April 22, 2025 1897 AMS Advanced Change Type Reference AMS Advanced Change Type Details "default": "TCP:80" }, "HealthCheckTimeout": { "type": "string", "description": "The amount of time, in seconds, during which no response means a failed health probe. This value must be less than the value for HealthCheckInterval.", "pattern": "[1-9]{1}[0-9]{0,3}", "default": "5" }, "HealthCheckUnhealthyThreshold": { "type": "string", "description": "The number of consecutive health probe failures required before moving the instance to the unhealthy state.", "pattern": "[1-9]{1}[0-9]{0,2}", "default": "10" }, "BackendInstances": { "type": "array", "description": "A list of EC2 instance IDs to associate with the load balancer, in the form of i-0123abcd or i-01234567890abcdef for a single instance, or i-0123abcd,i-12345abcd or i-01234567890abcdef,i-2345678901abcdefg for multiple instances. Leave blank to not associate individual EC2 instances with the load balancer. A load balancer can be associated with an autoscaling group by specifying the load balancer name in the ASGLoadBalancerNames property during creation or update of the autoscaling group.", "items": { "type": "string", "pattern": "^i-([0-9a-zA-Z]{8}|[0-9a-zA-Z]{17})$" }, "minItems": 0, "uniqueItems": true }, "LBCookieExpirationPeriod": { "type": "string", "description": "The time period, in seconds, after which the cookie is considered stale. If this parameter isn't specified, the sticky session will last for the duration of the browser session.", "pattern": "^[0-9]+$|^$" }, "LBCookieStickinessPolicyName": { "type": "string", "description": "A name for the load balancer cookie stickiness policy. The name must be unique within the set of policies for this load balancer. To associate ct-0ary07xiajwx4 Version April 22, 2025 1898 AMS Advanced Change Type Reference AMS Advanced Change Type Details with a listener, specify the name under PolicyNames in the respective listener configuration.", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "AppCookieName": { "type": "string", "description": "A name for the application cookie used for stickiness.", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "AppCookiePolicyName": { "type": "string", "description": "A name for the application cookie stickiness policy. The name must be unique within the set of policies for this load balancer. To associate with a listener, specify the name under PolicyNames in the respective listener configuration.", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" } }, "metadata": { "ui:order": [ "Name", "Scheme", "SecurityGroups", "SubnetIds", "BackendInstances", "IdleTimeout", "CrossZone", "AccessLogInterval", "ConnectionDrainingTimeout", "HealthCheckHealthyThreshold", "HealthCheckInterval", "HealthCheckTarget", "HealthCheckTimeout", "HealthCheckUnhealthyThreshold", "LBCookieExpirationPeriod", "LBCookieStickinessPolicyName", "AppCookieName", "AppCookiePolicyName" ] }, "required": [ "SecurityGroups", "SubnetIds" ], ct-0ary07xiajwx4 Version April 22, 2025 1899 AMS Advanced Change Type Reference AMS Advanced Change Type Details "additionalProperties": false }, "Listener1": { "type": "object", "properties": { "InstancePort": { "type": "string", "description": "The TCP port the listener uses to send traffic to the target instance.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$", "default": "80" }, "InstanceProtocol": { "type": "string", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ], "default": "HTTP" }, "Port": { "type": "string", "description": "The port number for the load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$", "default": "80" }, "Protocol": { "type": "string", "description": "The transport protocol to use for routing front-end connections (client to load balancer) to the listener.", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ], "default": "HTTP" }, "PolicyNames": { ct-0ary07xiajwx4 Version April 22, 2025 1900 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "description": "A list of policy names to associate with the listener.", "items": { "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "minItems": 0, "uniqueItems": true }, "SSLCertificateId": { "type": "string", "description": "The Amazon Resource Name (ARN) of the SSL certificate to use with the listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "pattern": "^$|^arn:aws:acm:[a-z0-9-]+:[0-9]{12}:certificate/[0-9a-f]{8}- [0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$|^arn:aws:iam::[0-9]{12}:server- certificate/.*$" } }, "metadata": { "ui:order": [ "Port", "Protocol", "InstancePort", "InstanceProtocol", "PolicyNames", "SSLCertificateId" ] }, "required": [ "Port", "Protocol", "InstancePort" ], "additionalProperties": false }, "Listener2": { "type": "object", "properties": { "InstancePort": { "type": "string", "description": "The TCP port the listener uses to send traffic to the target instance.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" ct-0ary07xiajwx4 Version April 22, 2025 1901 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "InstanceProtocol": { "type": "string", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "Port": { "type": "string", "description": "The port number for the load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "Protocol": { "type": "string", "description": "The transport protocol to use for routing front-end connections |
ams-ct-538 | ams-ct.pdf | 538 | TCP port the listener uses to send traffic to the target instance.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" ct-0ary07xiajwx4 Version April 22, 2025 1901 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "InstanceProtocol": { "type": "string", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "Port": { "type": "string", "description": "The port number for the load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "Protocol": { "type": "string", "description": "The transport protocol to use for routing front-end connections (client to load balancer) to the listener.", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "PolicyNames": { "type": "array", "description": "A list of policy names to associate with the listener.", "items": { "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "minItems": 0, "uniqueItems": true }, "SSLCertificateId": { "type": "string", "description": "The Amazon Resource Name (ARN) of the SSL certificate to use with the listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", ct-0ary07xiajwx4 Version April 22, 2025 1902 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^$|^arn:aws:acm:[a-z0-9-]+:[0-9]{12}:certificate/[0-9a-f]{8}- [0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$|^arn:aws:iam::[0-9]{12}:server- certificate/.*$" } }, "metadata": { "ui:order": [ "Port", "Protocol", "InstancePort", "InstanceProtocol", "PolicyNames", "SSLCertificateId" ] }, "additionalProperties": false }, "Listener3": { "type": "object", "properties": { "InstancePort": { "type": "string", "description": "The TCP port the listener uses to send traffic to the target instance.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "InstanceProtocol": { "type": "string", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "Port": { "type": "string", "description": "The port number for the load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "Protocol": { ct-0ary07xiajwx4 Version April 22, 2025 1903 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The transport protocol to use for routing front-end connections (client to load balancer) to the listener.", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "PolicyNames": { "type": "array", "description": "A list of policy names to associate with the listener.", "items": { "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "minItems": 0, "uniqueItems": true }, "SSLCertificateId": { "type": "string", "description": "The Amazon Resource Name (ARN) of the SSL certificate to use with the listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "pattern": "^$|^arn:aws:acm:[a-z0-9-]+:[0-9]{12}:certificate/[0-9a-f]{8}- [0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$|^arn:aws:iam::[0-9]{12}:server- certificate/.*$" } }, "metadata": { "ui:order": [ "Port", "Protocol", "InstancePort", "InstanceProtocol", "PolicyNames", "SSLCertificateId" ] }, "additionalProperties": false }, "Listener4": { "type": "object", ct-0ary07xiajwx4 Version April 22, 2025 1904 AMS Advanced Change Type Reference AMS Advanced Change Type Details "properties": { "InstancePort": { "type": "string", "description": "The TCP port the listener uses to send traffic to the target instance.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "InstanceProtocol": { "type": "string", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "Port": { "type": "string", "description": "The port number for the load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "Protocol": { "type": "string", "description": "The transport protocol to use for routing front-end connections (client to load balancer) to the listener.", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "PolicyNames": { "type": "array", "description": "A list of policy names to associate with the listener.", "items": { "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "minItems": 0, "uniqueItems": true ct-0ary07xiajwx4 Version April 22, 2025 1905 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "SSLCertificateId": { "type": "string", "description": "The Amazon Resource Name (ARN) of the SSL certificate to use with the listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "pattern": "^$|^arn:aws:acm:[a-z0-9-]+:[0-9]{12}:certificate/[0-9a-f]{8}- [0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$|^arn:aws:iam::[0-9]{12}:server- certificate/.*$" } }, "metadata": { "ui:order": [ "Port", "Protocol", "InstancePort", "InstanceProtocol", "PolicyNames", "SSLCertificateId" ] }, "additionalProperties": false }, "Listener5": { "type": "object", "properties": { "InstancePort": { "type": "string", "description": "The TCP port the listener uses to send traffic to the target instance.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "InstanceProtocol": { "type": "string", "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance).", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "Port": { ct-0ary07xiajwx4 Version April 22, 2025 1906 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The port number for the load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "Protocol": { "type": "string", "description": "The transport protocol to use for routing front-end connections (client to load balancer) to the listener.", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "PolicyNames": { "type": "array", "description": "A list of policy names to associate with the listener.", "items": { "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "minItems": 0, "uniqueItems": true }, "SSLCertificateId": { "type": "string", "description": "The Amazon Resource Name (ARN) of the SSL certificate to use with the listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "pattern": "^$|^arn:aws:acm:[a-z0-9-]+:[0-9]{12}:certificate/[0-9a-f]{8}- [0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$|^arn:aws:iam::[0-9]{12}:server- certificate/.*$" } |
ams-ct-539 | ams-ct.pdf | 539 | load balancer to use when routing external incoming traffic to the listener.", "pattern": "(?!^22$)(?!^3389$)(?!^5985$)^([1-9]{1}[0-9]{0,4})$" }, "Protocol": { "type": "string", "description": "The transport protocol to use for routing front-end connections (client to load balancer) to the listener.", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "PolicyNames": { "type": "array", "description": "A list of policy names to associate with the listener.", "items": { "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "minItems": 0, "uniqueItems": true }, "SSLCertificateId": { "type": "string", "description": "The Amazon Resource Name (ARN) of the SSL certificate to use with the listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "pattern": "^$|^arn:aws:acm:[a-z0-9-]+:[0-9]{12}:certificate/[0-9a-f]{8}- [0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$|^arn:aws:iam::[0-9]{12}:server- certificate/.*$" } }, "metadata": { "ui:order": [ "Port", "Protocol", "InstancePort", "InstanceProtocol", "PolicyNames", "SSLCertificateId" ct-0ary07xiajwx4 Version April 22, 2025 1907 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] }, "additionalProperties": false } }, "metadata": { "ui:order": [ "Description", "VpcId", "Name", "TimeoutInMinutes", "StackTemplateId", "Tags", "LoadBalancer", "Listener1", "Listener2", "Listener3", "Listener4", "Listener5" ] }, "required": [ "Description", "VpcId", "Name", "TimeoutInMinutes", "StackTemplateId", "LoadBalancer", "Listener1" ], "additionalProperties": false } Schema for Change Type ct-0attesnjqy2cx Classifications: • Deployment | Advanced stack components | Database Migration Service (DMS) | Create source endpoint { ct-0attesnjqy2cx Version April 22, 2025 1908 AMS Advanced Change Type Reference AMS Advanced Change Type Details "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create DMS source endpoint", "description": "Use to create a Database Migration Service (DMS) source endpoint.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to 40 tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 } }, "additionalProperties": false, ct-0attesnjqy2cx Version April 22, 2025 1909 AMS Advanced Change Type Reference AMS Advanced Change Type Details "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 40, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-pud4ghhkp7395n9bc.", "type": "string", "enum": [ "stm-pud4ghhkp7395n9bc" ], "default": "stm-pud4ghhkp7395n9bc" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 60, "default": 60 }, "Parameters": { "type": "object", "properties": { "CertificateArn": { "type": "string", "description": "The Amazon Resource Name (ARN) for the certificate to use with the source. This is required if SslMode = verify-ca or verify-full.", "pattern": "^$|^arn:aws:dms:[a-z0-9-]+:[0-9]{12}:cert:[A-Z0-9]+$" }, "DatabaseName": { "type": "string", ct-0attesnjqy2cx Version April 22, 2025 1910 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The name of the source database. Must not be blank if EngineName = azuredb, db2, oracle, postgres, sqlserver or sybase." }, "EndpointIdentifier": { "type": "string", "description": "A meaningful identifier for the source database endpoint. Must be unique for all endpoints owned by your AWS account in the current region. Must begin with a letter, must contain only ASCII letters, digits and hyphens and must not end with a hyphen or contain two consecutive hyphens.", "pattern": "^$|(?!.*--)[a-zA-Z][a-zA-Z0-9-]*[a-zA-Z0-9]$" }, "EngineName": { "type": "string", "description": "The type of engine this source endpoint is connected to. Some parameters become required depending on the specified EngineName.", "enum": [ "aurora", "azuredb", "db2", "mariadb", "mysql", "oracle", "postgres", "sqlserver", "sybase" ] }, "ExtraConnectionAttributes": { "type": "string", "description": "Additional attributes associated with the connection. See AWS documentation for more information on the supported extra connection attributes for the EngineName you have selected." }, "KmsKeyId": { "type": "string", "description": "The AWS Key Management Service (AWS KMS) customer master key (CMK) ID to use for encrypting volumes associated with the replication instance. If not specified, the default CMK for Amazon DMS is used.", "pattern": "^$|^[\\w]{8}-[\\w]{4}-[\\w]{4}-[\\w]{4}-[\\w]{12}$" }, "Password": { "type": "string", "description": "The password to be used to log in to the source database.", "metadata": { ct-0attesnjqy2cx Version April 22, 2025 1911 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ams:sensitive": true } }, "Port": { "type": "integer", "description": "The port used by the source database.", "minimum": 1, "maximum": 65535 }, "ServerName": { "type": "string", "description": "The name of the server where the source database resides." }, "SslMode": { "type": "string", "description": "The SSL mode to use for the SSL connection.", "enum": [ "none", "require", "verify-ca", "verify-full" ], "default": "none" }, "Username": { "type": "string", "description": "The user name to be used to log in to the source database.", "metadata": { "ams:sensitive": true } } }, "metadata": { "ui:order": [ "EndpointIdentifier", "EngineName", "ServerName", "Port", "DatabaseName", |
ams-ct-540 | ams-ct.pdf | 540 | AMS Advanced Change Type Details "ams:sensitive": true } }, "Port": { "type": "integer", "description": "The port used by the source database.", "minimum": 1, "maximum": 65535 }, "ServerName": { "type": "string", "description": "The name of the server where the source database resides." }, "SslMode": { "type": "string", "description": "The SSL mode to use for the SSL connection.", "enum": [ "none", "require", "verify-ca", "verify-full" ], "default": "none" }, "Username": { "type": "string", "description": "The user name to be used to log in to the source database.", "metadata": { "ams:sensitive": true } } }, "metadata": { "ui:order": [ "EndpointIdentifier", "EngineName", "ServerName", "Port", "DatabaseName", "Username", "Password", "SslMode", "CertificateArn", "KmsKeyId", ct-0attesnjqy2cx Version April 22, 2025 1912 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ExtraConnectionAttributes" ] }, "required": [ "EngineName", "ServerName", "Port", "Username", "Password" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Name", "Description", "VpcId", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } Schema for Change Type ct-0biqnokj25gkd Classifications: • Management | Host security | Trend Micro DSM | Update agent status (review required) { ct-0biqnokj25gkd Version April 22, 2025 1913 AMS Advanced Change Type Reference AMS Advanced Change Type Details "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Trend Micro DSM agent status.", "description": "Start, stop, deactivate, or reactivate Trend Micro agent.", "type": "object", "properties": { "Region": { "description": "The AWS Region where the instances are in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "InstanceIds": { "description": "ID of the instance in the form i-12345678901234567 or i-12345678.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-z0-9]{8,17}$" }, "minItems": 1, "maxItems": 25, "uniqueItems": true }, "AgentAction": { "description": "Choose agent update action: start, stop, deactivate, or reactivate.", "type": "string", "enum": [ "Start", "Stop", "Deactivate", "Reactivate" ] }, "Description": { "description": "A meaningful description for updating the Trend Micro agent status.", "type": "string", "minLength": 0, "maxLength": 5000 }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", ct-0biqnokj25gkd Version April 22, 2025 1914 AMS Advanced Change Type Reference AMS Advanced Change Type Details "enum": [ "Low", "Medium", "High" ] } }, "metadata": { "ui:order": [ "Region", "InstanceIds", "AgentAction", "Description", "Priority" ] }, "additionalProperties": false, "required": [ "InstanceIds", "AgentAction", "Region" ] } Schema for Change Type ct-0bpxsrtu16igp Classifications: • Management | Advanced stack components | RDS database stack | Reboot { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Reboot RDS DB instance", "description": "Use to reboot an RDS DB instance.", "additionalProperties": false, "type": "object", "properties": { "DbInstanceIdentifier": { "pattern": "(?=[a-zA-Z0-9-]{1,63}$)^[a-zA-Z][a-zA-Z0-9]*(-[a-zA-Z0-9]+)*$", "description": "The identifier of the DB instance to reboot.", "type": "string" }, ct-0bpxsrtu16igp Version April 22, 2025 1915 AMS Advanced Change Type Reference "ForceFailover": { AMS Advanced Change Type Details "default": false, "description": "True to reboot with Multi-AZ failover, for Multi-AZ instances. Default is false.", "type": "boolean" } }, "required": [ "DbInstanceIdentifier" ] } Schema for Change Type ct-0c38gftq56zj6 Classifications: • Deployment | Advanced stack components | DNS (private) | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Private DNS Record", "description": "Create a new Route 53 DNS resource record sets and a new private hosted zone for a VPC, and configure traffic routing.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-CreateAddRoute53Resources.", "type": "string", "enum": [ "AWSManagedServices-CreateAddRoute53Resources" ], "default": "AWSManagedServices-CreateAddRoute53Resources" }, "Region": { "description": "The AWS Region in which the AWS resource is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "description": "Specifications for the stack.", "type": "object", ct-0c38gftq56zj6 Version April 22, 2025 1916 AMS Advanced Change Type Reference "properties": { AMS Advanced Change Type Details "DomainName": { "description": "A domain name for the hosted zone. The name can contain only lowercase letters, numbers, hyphens (-), and a dot (.). For example, mycorp.com", "type": "string", "minLength": 2, "pattern": "^([a-z0-9]+(-[a-z0-9]+)*\\.)+[a-z]{2,255}$" }, "VPCId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "DomainType": { "description": "Must be 'private'", "type": "string", "enum": [ "private" ], "default": "private" }, "RecordSet": { "description": "A JSON of resource records for the hosted zone.", "type": "array", "items": { "type": "string", "pattern": "^\\s*\\{\\s*\"RecordSet\"\\s*:\\s*\\[.*\\]\\s*\\}\\s*$" }, "minItems": 1, "maxItems": 1 } }, "additionalProperties": false, "metadata": { "ui:order": [ "DomainName", "VPCId", "DomainType", "RecordSet" ] }, "required": [ "DomainName", ct-0c38gftq56zj6 Version April 22, 2025 1917 AMS Advanced Change Type Reference AMS Advanced Change Type Details "VPCId", "DomainType", "RecordSet" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0cupn1txog5tk Classifications: • Deployment | Advanced stack components | Storage Gateway | Create from Backup { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Start Storage Gateway Restore Job", "description": "Start an AWS Backup service restore job to restore a Storage Gateway volume snapshot of the specified resource.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices- StartRestoreJobStorageGatewayVolume.", "type": |
ams-ct-541 | ams-ct.pdf | 541 | "DomainName", ct-0c38gftq56zj6 Version April 22, 2025 1917 AMS Advanced Change Type Reference AMS Advanced Change Type Details "VPCId", "DomainType", "RecordSet" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0cupn1txog5tk Classifications: • Deployment | Advanced stack components | Storage Gateway | Create from Backup { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Start Storage Gateway Restore Job", "description": "Start an AWS Backup service restore job to restore a Storage Gateway volume snapshot of the specified resource.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices- StartRestoreJobStorageGatewayVolume.", "type": "string", "enum": [ "AWSManagedServices-StartRestoreJobStorageGatewayVolume" ], "default": "AWSManagedServices-StartRestoreJobStorageGatewayVolume" ct-0cupn1txog5tk Version April 22, 2025 1918 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "Region": { "description": "The AWS Region in which the AWS resource is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "RecoveryPointArn": { "description": "The Amazon Resource Name (ARN) that uniquely identifies a recovery point.", "type": "array", "items": { "type": "string", "pattern": "^arn:aws:([a-z][a-z0-9-]+):([a-z]{2}((-gov))?-[a-z]+-\\d{1}): [0-9]{0,12}:[a-zA-Z0-9\\_\\-\\/\\:]+$" }, "minItems": 1, "maxItems": 1 }, "BackupVaultName": { "description": "The name of the target backup vault. The backup vault name is case sensitive and must contain from 2 to 50 alphanumeric characters or hyphens.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\_\\-]{2,50}$" }, "minItems": 1, "maxItems": 1 }, "GatewayArn": { "description": "The Amazon Resource Name (ARN) that uniquely identifies a Storage Gateway.", "type": "array", "items": { "type": "string", "pattern": "^arn:aws:([a-z][a-z0-9-]+):([a-z]{2}((-gov))?-[a-z]+-\\d{1}): [0-9]{0,12}:[a-zA-Z0-9\\_\\-\\/\\:]+$" }, "minItems": 1, "maxItems": 1 ct-0cupn1txog5tk Version April 22, 2025 1919 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "TargetName": { "description": "The name of the Internet Small Computer Systems Interface(iSCSI) target. This is the name your iSCSI initiator uses to connect to your volume. The target name can contain lowercase letters, numbers, periods (.), and hyphens (-).", "type": "array", "items": { "type": "string", "pattern": "^[a-z0-9\\_\\-\\.]+$" }, "minItems": 1, "maxItems": 1 }, "GatewayType": { "description": "The Storage Gateway volume restore type. For data that is cached in the gateway and stored in S3, choose Cached. For on-premise data stored locally, choose Stored. If you choose Stored, you must also specify a DiskId.", "type": "array", "items": { "type": "string", "enum": [ "Cached", "Stored" ] }, "minItems": 1, "maxItems": 1 }, "DiskId": { "description": "The unique identifier for the gateway local disk that is configured as a stored volume. Find disk IDs for a gateway on the Storage Gateway console. Required when GatewayType = Stored. If specified, all data currently residing on this disk will be lost, and overwritten with the current data on the snapshot.", "type": "array", "items": { "type": "string", "default": "", "pattern": "^(|[a-z0-9\\_\\-\\.\\:]+)$" }, "minItems": 1, "maxItems": 1 }, "VolumeSize": { ct-0cupn1txog5tk Version April 22, 2025 1920 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The size of the volume, in GiBs. If this value is specified, it must be greater than the snapshot size, to take affect. By default, the volume size is equal to the snapshot size.", "type": "array", "items": { "type": "string", "default": "0", "pattern": "^(0|[1-9]|[1-8][0-9]|9[0-9]|[1-8][0-9]{2}|9[0-8][0-9]|99[0-9]| [1-8][0-9]{3}|9[0-8][0-9]{2}|99[0-8][0-9]|999[0-9]|1[0-5][0-9]{3}|16[0-2][0-9]{2}| 163[0-7][0-9]|1638[0-4])$" }, "minItems": 1, "maxItems": 1 }, "IamRoleArn": { "description": "The ARN of the role that allows AWS Backup to perform the actions on your behalf. If no role is specified, the default IAM role, created by AMS during the account onboarding process, is used.", "type": "array", "items": { "type": "string", "default": "", "pattern": "^(|arn:aws:iam:([a-z]{2}((-gov))?-[a-z]+-[0-9]){0,1}:[0-9] {12}:role\\/[a-zA-Z0-9\\_\\-]+)$" }, "minItems": 1, "maxItems": 1 }, "KmsKeyArn": { "description": "The Amazon Resource Name (ARN) for the AWS KMS key to encrypt the new Storage Gateway volume.", "type": "array", "items": { "type": "string", "default": "", "pattern": "^(|arn:aws:kms:([a-z]{2}((-gov))?-[a-z]+-\\d{1}):[0-9]{0,12}: [a-zA-Z0-9\\_\\-\\/\\:]+)$" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ ct-0cupn1txog5tk Version April 22, 2025 1921 AMS Advanced Change Type Reference AMS Advanced Change Type Details "RecoveryPointArn", "BackupVaultName", "GatewayArn", "TargetName", "GatewayType", "DiskId", "VolumeSize", "IamRoleArn", "KmsKeyArn" ] }, "required": [ "RecoveryPointArn", "BackupVaultName", "GatewayArn", "TargetName", "GatewayType" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0cyqd7laxyhlm Classifications: • Deployment | Monitoring and notification | CloudWatch | Create LogGroup ct-0cyqd7laxyhlm Version April 22, 2025 1922 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "CloudWatch LogGroup with optional subscription filter, log streams and metric filters.", "description": "Creates a CloudWatch LogGroup with optional subscription filter, up to 5 log streams and up to 5 metric filters.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", |
ams-ct-542 | ams-ct.pdf | 542 | Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "CloudWatch LogGroup with optional subscription filter, log streams and metric filters.", "description": "Creates a CloudWatch LogGroup with optional subscription filter, up to 5 log streams and up to 5 metric filters.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,255}$", "minLength": 1, ct-0cyqd7laxyhlm Version April 22, 2025 1923 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 50, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-8ian3plt5a6jbv7jt", "type": "string", "enum": [ "stm-8ian3plt5a6jbv7jt" ], "default": "stm-8ian3plt5a6jbv7jt" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 60, "default": 60 }, "Parameters": { "type": "object", "properties": { "LogGroupName": { "type": "string", "description": "A name for the log group. The name must be prefixed with the word 'customer'.", "pattern": "^customer[a-zA-Z0-9\\.\\-_/#]{1,504}$" ct-0cyqd7laxyhlm Version April 22, 2025 1924 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "LogGroupRetentionInDays": { "type": "string", "description": "The number of days to retain the log events in the log group created. Leave blank to keep logs indefinitely.", "enum": [ "", "1", "3", "5", "7", "14", "30", "60", "90", "120", "150", "180", "365", "400", "545", "731", "1827", "3653" ], "default": "" }, "LogStream1Name": { "type": "string", "description": "A name for log stream 1. The name must be unique within the log group. If left blank log stream 1 is not created.", "pattern": "^[a-zA-Z0-9\\.\\-_/#]{1,512}$|^$", "default": "" }, "LogStream2Name": { "type": "string", "description": "A name for log stream 2. The name must be unique within the log group. If left blank log stream 2 is not created.", "pattern": "^[a-zA-Z0-9\\.\\-_/#]{1,512}$|^$", "default": "" }, "LogStream3Name": { "type": "string", ct-0cyqd7laxyhlm Version April 22, 2025 1925 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A name for log stream 3. The name must be unique within the log group. If left blank log stream 3 is not created.", "pattern": "^[a-zA-Z0-9\\.\\-_/#]{1,512}$|^$", "default": "" }, "LogStream4Name": { "type": "string", "description": "A name for log stream 4. The name must be unique within the log group. If left blank log stream 4 is not created.", "pattern": "^[a-zA-Z0-9\\.\\-_/#]{1,512}$|^$", "default": "" }, "LogStream5Name": { "type": "string", "description": "A name for log stream 5. The name must be unique within the log group. If left blank log stream 5 is not created.", "pattern": "^[a-zA-Z0-9\\.\\-_/#]{1,512}$|^$", "default": "" }, "SubscriptionFilterIAMroleARN": { "type": "string", "description": "An IAM role that grants CloudWatch Logs permission to put data into the destination. Applicable only if the destination is Kinesis stream or Kinesis Data Firehose delivery stream.", "pattern": "(arn:aws:iam::\\d{12}:role\\/[\\w+=,.@-]{1,64}|^$)", "default": "" }, "SubscriptionFilterPattern": { "type": "string", "description": "The filtering expressions that restrict what gets delivered to the destination AWS resource.", "pattern": "^.{1,1024}$|^$", "default": "" }, "SubscriptionDestinationARN": { "type": "string", "description": "The Amazon Resource Name (ARN) of the Kinesis stream, Kinesis Data Firehose delivery stream, or Lambda function, to use as the subscription feed destination.", "pattern": "^arn:aws:kinesis:[a-z0-9-]+:[0-9]{12}:stream/[a-zA-Z0-9-_\\.] {1,128}$|^arn:aws:firehose:[a-z0-9-]+:[0-9]{12}:deliverystream/[a-zA-Z0-9-_\\.]{1,64}$| ^arn:aws:lambda:[a-z0-9-]+:[0-9]{12}:function:[a-zA-Z0-9-_]{1,140}$|^$", "default": "" }, ct-0cyqd7laxyhlm Version April 22, 2025 1926 AMS Advanced Change Type Reference AMS Advanced Change Type Details "MetricFilter1Pattern": { "type": "string", "description": "The pattern for MetricFilter1 that CloudWatch Logs follows to interpret each entry in a log.", "pattern": "^.{1,1024}$|^$", "default": "" }, "MetricFilter1DefaultValue": { "type": "string", "description": "The value to emit when a filter pattern does not match a log event.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter1Value": { "type": "string", "description": "The value that is published to the CloudWatch metric. If left blank MetricFilter1 is not created.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter1Namespace": { "type": "string", "description": "The destination namespace of the CloudWatch metric for the MetricFilter1. Namespaces are containers for metrics. If left blank MetricFilter1 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter1Name": { "type": "string", "description": "The name of the CloudWatch metric that the log information is published to. If left blank MetricFilter1 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter2Pattern": { "type": "string", "description": "The pattern for MetricFilter2 that CloudWatch Logs follows to interpret each entry in a log.", |
ams-ct-543 | ams-ct.pdf | 543 | is published to the CloudWatch metric. If left blank MetricFilter1 is not created.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter1Namespace": { "type": "string", "description": "The destination namespace of the CloudWatch metric for the MetricFilter1. Namespaces are containers for metrics. If left blank MetricFilter1 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter1Name": { "type": "string", "description": "The name of the CloudWatch metric that the log information is published to. If left blank MetricFilter1 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter2Pattern": { "type": "string", "description": "The pattern for MetricFilter2 that CloudWatch Logs follows to interpret each entry in a log.", "pattern": "^.{1,1024}$|^$", "default": "" }, "MetricFilter2DefaultValue": { ct-0cyqd7laxyhlm Version April 22, 2025 1927 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The value to emit when a filter pattern does not match a log event.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter2Value": { "type": "string", "description": "The value that is published to the CloudWatch metric. If left blank MetricFilter2 is not created.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter2Namespace": { "type": "string", "description": "The destination namespace of the CloudWatch metric for the MetricFilter2. Namespaces are containers for metrics. If left blank MetricFilter2 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter2Name": { "type": "string", "description": "The name of the CloudWatch metric that the log information is published to. If left blank MetricFilter2 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter3Pattern": { "type": "string", "description": "The pattern for MetricFilter3 that CloudWatch Logs follows to interpret each entry in a log.", "pattern": "^.{1,1024}$|^$", "default": "" }, "MetricFilter3DefaultValue": { "type": "string", "description": "The value to emit when a filter pattern does not match a log event.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter3Value": { "type": "string", ct-0cyqd7laxyhlm Version April 22, 2025 1928 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The value that is published to the CloudWatch metric. If left blank MetricFilter3 is not created.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter3Namespace": { "type": "string", "description": "The destination namespace of the CloudWatch metric for the MetricFilter3. Namespaces are containers for metrics. If left blank MetricFilter3 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter3Name": { "type": "string", "description": "The name of the CloudWatch metric that the log information is published to. If left blank MetricFilter3 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter4Pattern": { "type": "string", "description": "The pattern for MetricFilter4 that CloudWatch Logs follows to interpret each entry in a log.", "pattern": "^.{1,1024}$|^$", "default": "" }, "MetricFilter4DefaultValue": { "type": "string", "description": "The value to emit when a filter pattern does not match a log event.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter4Value": { "type": "string", "description": "The value that is published to the CloudWatch metric. If left blank MetricFilter4 is not created.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter4Namespace": { "type": "string", ct-0cyqd7laxyhlm Version April 22, 2025 1929 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The destination namespace of the CloudWatch metric for the MetricFilter4. Namespaces are containers for metrics. If left blank MetricFilter4 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter4Name": { "type": "string", "description": "The name of the CloudWatch metric that the log information is published to. If left blank MetricFilter4 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter5Pattern": { "type": "string", "description": "The pattern for MetricFilter5 that CloudWatch Logs follows to interpret each entry in a log.", "pattern": "^.{1,1024}$|^$", "default": "" }, "MetricFilter5DefaultValue": { "type": "string", "description": "The value to emit when a filter pattern does not match a log event.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter5Value": { "type": "string", "description": "The value that is published to the CloudWatch metric. If left blank MetricFilter5 is not created.", "pattern": "^[0-9]{1,100}$|^$", "default": "" }, "MetricFilter5Namespace": { "type": "string", "description": "The destination namespace of the CloudWatch metric for the MetricFilter5. Namespaces are containers for metrics. If left blank MetricFilter5 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" }, "MetricFilter5Name": { "type": "string", ct-0cyqd7laxyhlm Version April 22, 2025 1930 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The name of the CloudWatch metric that the log information is published to. If left blank MetricFilter5 is not created.", "pattern": "^[a-zA-Z0-9_\\-\\/.]{1,1024}$|^$", "default": "" } }, "metadata": { "ui:order": [ "LogGroupName", "LogGroupRetentionInDays", "LogStream1Name", "LogStream2Name", "LogStream3Name", "LogStream4Name", "LogStream5Name", "SubscriptionFilterIAMroleARN", "SubscriptionFilterPattern", "SubscriptionDestinationARN", "MetricFilter1Name", "MetricFilter1Namespace", "MetricFilter1Pattern", "MetricFilter1Value", "MetricFilter1DefaultValue", "MetricFilter2Name", "MetricFilter2Namespace", "MetricFilter2Pattern", "MetricFilter2Value", "MetricFilter2DefaultValue", "MetricFilter3Name", "MetricFilter3Namespace", "MetricFilter3Pattern", "MetricFilter3Value", "MetricFilter3DefaultValue", "MetricFilter4Name", "MetricFilter4Namespace", "MetricFilter4Pattern", "MetricFilter4Value", "MetricFilter4DefaultValue", "MetricFilter5Name", "MetricFilter5Namespace", "MetricFilter5Pattern", "MetricFilter5Value", "MetricFilter5DefaultValue" ] ct-0cyqd7laxyhlm Version April 22, 2025 1931 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "required": [ "LogGroupName" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } Schema for Change Type ct-0el2j07llrxs7 Classifications: • Deployment | Patching | SSM patch window | Create { |
ams-ct-544 | ams-ct.pdf | 544 | "LogStream2Name", "LogStream3Name", "LogStream4Name", "LogStream5Name", "SubscriptionFilterIAMroleARN", "SubscriptionFilterPattern", "SubscriptionDestinationARN", "MetricFilter1Name", "MetricFilter1Namespace", "MetricFilter1Pattern", "MetricFilter1Value", "MetricFilter1DefaultValue", "MetricFilter2Name", "MetricFilter2Namespace", "MetricFilter2Pattern", "MetricFilter2Value", "MetricFilter2DefaultValue", "MetricFilter3Name", "MetricFilter3Namespace", "MetricFilter3Pattern", "MetricFilter3Value", "MetricFilter3DefaultValue", "MetricFilter4Name", "MetricFilter4Namespace", "MetricFilter4Pattern", "MetricFilter4Value", "MetricFilter4DefaultValue", "MetricFilter5Name", "MetricFilter5Namespace", "MetricFilter5Pattern", "MetricFilter5Value", "MetricFilter5DefaultValue" ] ct-0cyqd7laxyhlm Version April 22, 2025 1931 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "required": [ "LogGroupName" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } Schema for Change Type ct-0el2j07llrxs7 Classifications: • Deployment | Patching | SSM patch window | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create SSM Patch Window", "description": "Create an AWS Systems Manager (SSM) patch window for patching to take place on instances with the specified PatchGroup. The patch window is an SSM resource that you can manage with the SSM console.", "properties": { ct-0el2j07llrxs7 Version April 22, 2025 1932 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Cutoff": { "description": "The maximum number of hours before the end of the scheduled patch window for starting a new patching command. This helps ensure that patching commands complete before the patch window ends. A new patching command can only start execution within the patch window and before the specified Cutoff. After the Cutoff is reached, no new patching commands can be started.", "default": 0, "maximum": 23, "minimum": 0, "type": "integer" }, "Description": { "description": "A meaningful description for this patch window.", "maxLength": 500, "minLength": 1, "type": "string" }, "Duration": { "description": "The duration of the patch window in hours.", "maximum": 24, "minimum": 1, "type": "integer" }, "EndDate": { "description": "The date and time, in ISO-8601 extended format, for when the patch window is scheduled to become inactive (i.e.: 2019-10-23T19:45:00Z).", "type": "string" }, "MaxConcurrency": { "description": "The maximum number or rate (%) of instances allowed to patch in parallel.", "default": "33%", "maxLength": 7, "minLength": 1, "pattern": "^([1-9][0-9]*|[1-9][0-9]%|[1-9]%|100%)$", "type": "string" }, "MaxErrors": { "description": "The maximum number or rate (%) of errors allowed before the Patching stops being scheduled.", "default": "100%", "maxLength": 7, "minLength": 1, "pattern": "^([1-9][0-9]*|[1-9][0-9]%|[1-9]%|100%)$", ct-0el2j07llrxs7 Version April 22, 2025 1933 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string" }, "Name": { "description": "A friendly name for this patch window.", "maxLength": 128, "minLength": 3, "pattern": "^[a-zA-Z0-9._-]+$", "type": "string" }, "NotificationEmails": { "description": "One or more email addresses to receive notifications about patching status.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9-_+.]+@[a-zA-Z0-9-_+.]+$" }, "minItems": 1, "maxItems": 5, "uniqueItems": true }, "PatchGroup": { "description": "The value of the \"Patch Group\" tag of an existing instance; for example 'App123-CustA-EnvTest'. Instances with the specified \"Patch Group\" tag values, are included in the patch window. If needed, you can create \"Patch Group \" tags using the console for the resource, but these tags are usually created at onboarding.", "type": "string", "minLength": 1, "maxLength": 256 }, "Schedule": { "description": "The schedule of the patch window in the form of a cron or rate expression; for example, cron(30 09 ? * * *) or rate(7 days).", "maxLength": 256, "minLength": 1, "type": "string" }, "ScheduleOffset": { "description": "The number of days to wait after the date and time specified by a cron expression before the maintenance window runs.", "default": 0, "maximum": 6, "minimum": 0, ct-0el2j07llrxs7 Version April 22, 2025 1934 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "integer" }, "ScheduleTimeZone": { "description": "The time zone that the scheduled patch window executions are based on, in Internet Assigned Numbers Authority (IANA) format (i.e.: UTC, America/ Los_Angeles).", "default": "UTC", "pattern": "^[a-zA-Z_]+(\\+|/)?[a-zA-Z0-9_-]*(\\+|/)?[a-zA-Z0-9_-]+$", "type": "string" }, "StartDate": { "description": "The date and time, in ISO-8601 extended format, after which the patch window becomes active (i.e.: 2019-10-23T19:45:00Z).", "type": "string" } }, "additionalProperties": false, "metadata": { "ui:order": [ "Name", "Description", "PatchGroup", "Schedule", "ScheduleOffset", "Duration", "MaxConcurrency", "MaxErrors", "Cutoff", "StartDate", "EndDate", "ScheduleTimeZone", "NotificationEmails" ] }, "required": [ "Cutoff", "Duration", "MaxConcurrency", "MaxErrors", "Name", "NotificationEmails", "PatchGroup", "Schedule", "ScheduleTimeZone" ct-0el2j07llrxs7 Version April 22, 2025 1935 AMS Advanced Change Type Reference AMS Advanced Change Type Details ], "type": "object" } Schema for Change Type ct-0erkoad6uyvvg Classifications: • Management | Monitoring and notification | CloudWatch | Enable Non-Root Volumes Monitoring { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Enable Non-Root Volumes Monitoring", "description": "Enable monitoring on non-root volumes of an EC2 instance.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-DeployNonRootVolumeMonitoring.", "type": "string", "enum": [ "AWSManagedServices-DeployNonRootVolumeMonitoring" ], "default": "AWSManagedServices-DeployNonRootVolumeMonitoring" }, "Region": { "description": "The AWS Region where the EC2 instance, and volumes, are.", "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "InstanceId": { "description": "The ID of the EC2 instance, in the form i-12345678 or i-123456789012345ab.", "type": "array", "items": { "type": "string", "pattern": "^i-[0-9a-f]{8}$|^i-[0-9a-f]{17}$" }, "minItems": 1, "maxItems": 1 ct-0erkoad6uyvvg Version April 22, 2025 1936 AMS Advanced Change Type Reference AMS Advanced Change Type Details } }, "metadata": { "ui:order": [ "InstanceId" |
ams-ct-545 | ams-ct.pdf | 545 | non-root volumes of an EC2 instance.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-DeployNonRootVolumeMonitoring.", "type": "string", "enum": [ "AWSManagedServices-DeployNonRootVolumeMonitoring" ], "default": "AWSManagedServices-DeployNonRootVolumeMonitoring" }, "Region": { "description": "The AWS Region where the EC2 instance, and volumes, are.", "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "InstanceId": { "description": "The ID of the EC2 instance, in the form i-12345678 or i-123456789012345ab.", "type": "array", "items": { "type": "string", "pattern": "^i-[0-9a-f]{8}$|^i-[0-9a-f]{17}$" }, "minItems": 1, "maxItems": 1 ct-0erkoad6uyvvg Version April 22, 2025 1936 AMS Advanced Change Type Reference AMS Advanced Change Type Details } }, "metadata": { "ui:order": [ "InstanceId" ] }, "additionalProperties": false, "required": [ "InstanceId" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0ffvihqwjvqj1 Classifications: • Management | Advanced stack components | EC2 instance stack | Restore volumes { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Restore EC2 Volumes From Backup", "description": "Replace the instance volumes from an existing backup image of the instance. To restore from snapshot, use version 1.0 of this Change Type.", "type": "object", "properties": { "DocumentName": { ct-0ffvihqwjvqj1 Version April 22, 2025 1937 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Must be AWSManagedServices- ReplaceInstanceVolumesFromSnapshotsWithContext.", "type": "string", "enum": [ "AWSManagedServices-ReplaceInstanceVolumesFromSnapshotsWithContext" ], "default": "AWSManagedServices-ReplaceInstanceVolumesFromSnapshotsWithContext" }, "Region": { "description": "The AWS Region in which the EC2 instance is located, in the form us-east-1.", "type": "string", "pattern": "[a-z]{2}-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "InstanceId": { "description": "The identifier of the EC2 instance to replace the volumes from the backup.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-z0-9]{8,17}$" }, "minItems": 1, "maxItems": 1 }, "Backup": { "description": "The Amazon EC2 backup ARN, or AMI ID, custom or from backup, to use to restore the volumes, i.e. ami-0ecdf967356c809c7.", "type": "array", "items": { "type": "string", "pattern": "^arn:aws:ec2:[\\w]{2}-[a-z]+-[0-9]{1}::image/[A-Za-z0-9_-]+$| ^ami-[a-z0-9]+$" }, "minItems": 1, "maxItems": 1 }, "KMSKeyId": { "description": "The KMS key identifier, or ARN, to encrypt all restored volumes on the EC2 instance.", "type": "array", ct-0ffvihqwjvqj1 Version April 22, 2025 1938 AMS Advanced Change Type Reference "items": { AMS Advanced Change Type Details "type": "string", "pattern": "^[a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12}$| ^arn:aws:kms:[a-z]{2}-[a-z]+-\\d{1}:[0-9]{12}:key/[a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}- [a-z0-9]{4}-[a-z0-9]{12}$|^$" }, "minItems": 1, "maxItems": 1 }, "SleepTime": { "description": "The sleep time (how long to wait) before attempting access validation after data restoration completes.", "type": "array", "items": { "type": "string", "pattern": "^PT([0-9]|[1-5][0-9]|60)M$", "default": "PT5M" }, "minItems": 1, "maxItems": 1 }, "ChangeHostname": { "description": "True to change the hostname after the restore operation, to a generated hostname. False to not change the hostname. Default is False.", "type": "array", "items": { "type": "string", "enum": [ "True", "False" ], "default": "False" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "InstanceId", "Backup", "KMSKeyId", "ChangeHostname", "SleepTime" ct-0ffvihqwjvqj1 Version April 22, 2025 1939 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] }, "additionalProperties": false, "required": [ "InstanceId", "Backup" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0fpjlxa808sh2 Classifications: • Management | Advanced stack components | S3 storage | Update policy (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update policy", "description": "Update an S3 bucket policy.", "type": "object", "properties": { "BucketName": { "description": "The name of the Amazon S3 bucket to which the policy applies.", "type": "string", "pattern": "^(?!(mc|ams|awsms)-)[a-z0-9][-.a-z0-9]{1,61}[a-z0-9]$" }, "BucketPolicy": { ct-0fpjlxa808sh2 Version April 22, 2025 1940 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Detailed information about the bucket permissions update, or a policy document to be attached to the bucket (paste the policy document into the value field). Details should include the type of access (for example Read, Write or Delete).", "type": "string", "maxLength": 20000 }, "PolicyAction": { "description": "Whether the given bucket policy needs to be appended to the existing bucket policy or to replace the bucket policy entirely. If you want to add a new statement block to the existing policy, choose 'Append'. If you want to replace the entire policy or update the policy in specific sections, provide the entire policy containing desired changes and choose 'Replace'.", "type": "string", "enum": [ "Append", "Replace" ] }, "Operation": { "description": "Must be Update policy.", "type": "string", "default": "Update policy", "enum": [ "Update policy" ] }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "BucketName", "BucketPolicy", "PolicyAction", ct-0fpjlxa808sh2 Version April 22, 2025 1941 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Operation", "Priority" ] }, "required": [ "BucketName", "BucketPolicy", "PolicyAction", "Operation" ] } Schema for Change Type ct-0fqo03yizfnw6 Classifications: • Management | AWS Backup | Backup plan | Enable cross region copy { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Enable Cross Region Copy", "description": "Update an existing |
ams-ct-546 | ams-ct.pdf | 546 | policy" ] }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "BucketName", "BucketPolicy", "PolicyAction", ct-0fpjlxa808sh2 Version April 22, 2025 1941 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Operation", "Priority" ] }, "required": [ "BucketName", "BucketPolicy", "PolicyAction", "Operation" ] } Schema for Change Type ct-0fqo03yizfnw6 Classifications: • Management | AWS Backup | Backup plan | Enable cross region copy { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Enable Cross Region Copy", "description": "Update an existing backup plan rule with copy actions like cross region destination vault, and storage retention settings.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-ConfigureCrossRegionBackup.", "type": "string", "enum": [ "AWSManagedServices-ConfigureCrossRegionBackup" ], "default": "AWSManagedServices-ConfigureCrossRegionBackup" }, "Region": { "description": "The AWS Region in which the AWS Backup plan is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { ct-0fqo03yizfnw6 Version April 22, 2025 1942 AMS Advanced Change Type Reference AMS Advanced Change Type Details "BackupPlanName": { "description": "The name of the existing Backup plan to be updated.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\_\\-]{2,50}$" }, "maxItems": 1 }, "RuleName": { "description": "The name of the existing rule in the specified backup plan to be updated.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\_\\-]{2,50}$" }, "maxItems": 1 }, "DestinationRegion": { "description": "The AWS Region where the destination backup vault is.", "type": "array", "items": { "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "maxItems": 1 }, "DestinationVaultName": { "description": "The destination backup vault for the copied backup. If the vault does not exist in the destination Region, it is created automatically.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\_\\-]{2,50}$", "default": "ams-replication-vault" }, "maxItems": 1 }, "DestinationEncryptionKeyArn": { "description": "The destination server-side encryption key that is used to protect your backups. If the vault name does not exist and you do not provide a key ARN, a new key is created in the destination Region. For disaster recovery patterns, we recommend that you provide a key that belongs to a different account.", ct-0fqo03yizfnw6 Version April 22, 2025 1943 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "pattern": "^(|arn:aws:kms:([a-z]{2}((-gov))?-[a-z]+-\\d{1}):[0-9]{0,12}: [a-zA-Z0-9\\_\\-\\/\\:]+)$", "default": "" }, "maxItems": 1 }, "DeleteAfterNumberOfDays": { "description": "The number of days after creation that a recovery point is deleted. Must be greater than 90 days plus MoveToColdStorageAfterNumberOfDays.", "type": "array", "items": { "type": "string", "pattern": "^(0|[1-9]|[1-8][0-9]|9[0-9]|[1-8][0-9]{2}|9[0-8][0-9]|99[0-9]| [1-8][0-9]{3}|9[0-8][0-9]{2}|99[0-8][0-9]|999[0-9]|[12][0-9]{4}|3[0-4][0-9]{3}|35[0-5] [0-9]{2}|35600)$", "default": "0" }, "maxItems": 1 }, "MoveToColdStorageAfterNumberOfDays": { "description": "The number of days after creation that a recovery point is moved to cold storage.", "type": "array", "items": { "type": "string", "pattern": "^(0|[1-9]|[1-8][0-9]|9[0-9]|[1-8][0-9]{2}|9[0-8][0-9]|99[0-9]| [1-8][0-9]{3}|9[0-8][0-9]{2}|99[0-8][0-9]|999[0-9]|[12][0-9]{4}|3[0-4][0-9]{3}|35[0-5] [0-9]{2}|35600)$", "default": "0" }, "maxItems": 1 } }, "metadata": { "ui:order": [ "BackupPlanName", "DeleteAfterNumberOfDays", "DestinationRegion", "DestinationVaultName", "DestinationEncryptionKeyArn", "MoveToColdStorageAfterNumberOfDays", ct-0fqo03yizfnw6 Version April 22, 2025 1944 AMS Advanced Change Type Details AMS Advanced Change Type Reference "RuleName" ] }, "additionalProperties": false, "required": [ "BackupPlanName", "DestinationRegion", "RuleName" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0g690ekkyfm79 Classifications: • Deployment | Advanced stack components | Elastic File System (EFS) | Create from backup { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create EFS From Backup", "description": "Create an AWS Elastic File System (EFS) stack from backup.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-StartRestoreJobEFS.", "type": "string", "enum": [ ct-0g690ekkyfm79 Version April 22, 2025 1945 AMS Advanced Change Type Reference AMS Advanced Change Type Details "AWSManagedServices-StartRestoreJobEFS" ], "default": "AWSManagedServices-StartRestoreJobEFS" }, "Region": { "description": "The AWS Region in which the EFS snapshot is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "BackupVaultName": { "description": "The name of a logical container where backups are stored. The backup vault name is case sensitive and must contain from 2 to 50 alphanumeric characters or hyphens.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9_\\/\\-]{2,50}$" }, "maxItems": 1 }, "EnableEncryption": { "description": "Flag to control, when restoring to a new filesystem, whether it is encrypted or not. If specified, the KmsKeyId must also be set. If not specified, the new filesystem will be created without encryption.", "type": "array", "items": { "type": "string", "enum": [ "true", "false" ], "default": "false" }, "maxItems": 1 }, "ItemsToRestore": { "description": "The list containing up to five directories or files paths to be restored. Paths are case sensitive and cannot contain the following special characters: :, *, ?, \", <, > and `. If not specified, the entire filesystem will be restored.", ct-0g690ekkyfm79 Version April 22, 2025 1946 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "pattern": "^(/[^:*?\"<>`]*)$" }, "maxItems": 5 }, "KmsKeyId": { "description": "The Amazon Resource Name (ARN) for the AWS KMS key to |
ams-ct-547 | ams-ct.pdf | 547 | { "type": "string", "enum": [ "true", "false" ], "default": "false" }, "maxItems": 1 }, "ItemsToRestore": { "description": "The list containing up to five directories or files paths to be restored. Paths are case sensitive and cannot contain the following special characters: :, *, ?, \", <, > and `. If not specified, the entire filesystem will be restored.", ct-0g690ekkyfm79 Version April 22, 2025 1946 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "pattern": "^(/[^:*?\"<>`]*)$" }, "maxItems": 5 }, "KmsKeyId": { "description": "The Amazon Resource Name (ARN) for the AWS KMS key to be used to encrypt the new filesystem at rest.", "type": "array", "items": { "type": "string", "pattern": "^(|arn:aws:kms:([a-z]{2}((-gov))?-[a-z]+-\\d{1}):[0-9]{0,12}: [a-zA-Z0-9\\_\\-\\/\\:]+)$" }, "maxItems": 1 }, "PerformanceMode": { "description": "The performance mode, if restoring to a new filesystem. Use generalPurpose for most file systems. Use maxIO for applications where tens, hundreds, or thousands of EC2 instances are accessing the file system. If not specified, generalPurpose is used.", "type": "array", "items": { "type": "string", "enum": [ "generalPurpose", "maxIO" ], "default": "generalPurpose" }, "maxItems": 1 }, "RecoveryPointArn": { "description": "The Amazon Resource Name (ARN) that uniquely identifies the recovery point to restore.", "type": "array", "items": { "type": "string", "pattern": "^arn:aws:([a-z][a-z0-9-]+):([a-z]{2}((-gov))?-[a-z]+-\\d{1}): [0-9]{0,12}:[a-zA-Z0-9\\_\\-\\/\\:]+$" }, "maxItems": 1 ct-0g690ekkyfm79 Version April 22, 2025 1947 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "RestoreToNewFileSystem": { "description": "Flag to control whether the restore process creates a new filesystem or restores it to a directory in the source filesystem. If not specified, it is restored to a new filesystem.", "type": "array", "items": { "type": "string", "enum": [ "true", "false" ], "default": "true" }, "maxItems": 1 } }, "metadata": { "ui:order": [ "BackupVaultName", "EnableEncryption", "ItemsToRestore", "KmsKeyId", "PerformanceMode", "RecoveryPointArn", "RestoreToNewFileSystem" ] }, "additionalProperties": false, "required": [ "BackupVaultName", "RecoveryPointArn" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ ct-0g690ekkyfm79 Version April 22, 2025 1948 AMS Advanced Change Type Reference AMS Advanced Change Type Details "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0h3p576mj4rqm Classifications: • Management | Advanced stack components | EC2 instance stack | Change hostname (Windows) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Change Windows Hostname", "description": "Change the hostname of an EC2 Windows instance. Note that the instance will be rebooted.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-ChangeHostname.", "type": "string", "enum": [ "AWSManagedServices-ChangeHostname" ], "default": "AWSManagedServices-ChangeHostname" }, "Region": { "description": "The AWS Region where the EC2 instance is located, in the form us- east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "InstanceId": { "description": "The ID of the EC2 instance.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-f0-9]{8}$|^i-[a-f0-9]{17}$" ct-0h3p576mj4rqm Version April 22, 2025 1949 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "minItems": 1, "maxItems": 1 }, "Hostname": { "description": "The new hostname of the instance.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9-]{1,63}$" }, "minItems": 1, "maxItems": 1 }, "Platform": { "description": "Must be windows. To change the hostname for a Linux instance, use CT ct-2781aqd6f6svs.", "type": "array", "items": { "type": "string", "default": "windows", "enum": [ "windows" ] }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "InstanceId", "Hostname", "Platform" ] }, "required": [ "InstanceId", "Hostname", "Platform" ], "additionalProperties": false } }, ct-0h3p576mj4rqm Version April 22, 2025 1950 AMS Advanced Change Type Reference AMS Advanced Change Type Details "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0hahohe17csnc Classifications: • Management | Advanced stack components | EC2 instance stack | Encrypt instance volumes { "$schema" : "http://json-schema.org/draft-04/schema#", "name" : "Encrypt Instance Volumes", "description" : "Encrypt Elastic Block Store (EBS) volumes attached to an EC2 instance. Note: If the CT execution fails, verify that the EC2 instance related to this execution is healthy.", "type" : "object", "properties" : { "DocumentName" : { "description" : "Must be AWSManagedServices-EncryptInstanceVolumes", "type" : "string", "enum" : [ "AWSManagedServices-EncryptInstanceVolumes" ], "default" : "AWSManagedServices-EncryptInstanceVolumes" }, "Region" : { "description" : "The AWS Region where the EC2 instance is located, in the form us-east-1.", "type" : "string", "pattern" : "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" ct-0hahohe17csnc Version April 22, 2025 1951 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "Parameters": { "type": "object", "properties": { "InstanceId": { "description": "The ID of the EC2 instance to encrypt volumes for. The instance must support encryption of EBS volumes and not part of an Auto Scaling group.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-z0-9]{8}|i-[a-z0-9]{17}$" }, "minItems": 1, "maxItems": 1 }, "VolumeIds": { "description": "The list of EBS volume IDs to encrypt. The volume IDs must be attached to the specified EC2 instance.", "type": "array", "items": { "type": "string", "pattern": "^vol-([0-9a-f]{8}|[0-9a-f]{17})$" }, "minItems": 1, "maxItems": 25, "uniqueItems": true }, "KMSKeyId": { "description": "The KMS key ID, or ARN, to encrypt all the |
ams-ct-548 | ams-ct.pdf | 548 | "Parameters": { "type": "object", "properties": { "InstanceId": { "description": "The ID of the EC2 instance to encrypt volumes for. The instance must support encryption of EBS volumes and not part of an Auto Scaling group.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-z0-9]{8}|i-[a-z0-9]{17}$" }, "minItems": 1, "maxItems": 1 }, "VolumeIds": { "description": "The list of EBS volume IDs to encrypt. The volume IDs must be attached to the specified EC2 instance.", "type": "array", "items": { "type": "string", "pattern": "^vol-([0-9a-f]{8}|[0-9a-f]{17})$" }, "minItems": 1, "maxItems": 25, "uniqueItems": true }, "KMSKeyId": { "description": "The KMS key ID, or ARN, to encrypt all the new volumes.", "type": "array", "items": { "type": "string", "pattern": "^(arn:(aws|aws-cn|aws-us-gov):kms:[a-z]{2}-[a-z]+-\ \d{1}:[0-9]{12}:key/)?([a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12}| mrk-[a-z0-9]{32})$" }, "minItems": 1, "maxItems": 1 }, "DeleteStaleNonEncryptedSnapshotBackups": { "description": "True to delete existing snapshot backups of specified EBS volumes. False to not delete the existing snapshots.", ct-0hahohe17csnc Version April 22, 2025 1952 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "enum": ["True","False"], "default": "True" }, "minItems": 1, "maxItems": 1 }, "CopyTagsToNewEncryptedVolumes": { "description": "(Optional) True to copy tags from old volumes to new encrypted volumes, false to not copy tags. Default is true.", "type": "array", "items": { "type": "string", "enum": ["True","False"], "default": "True" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "InstanceId", "VolumeIds", "KMSKeyId", "DeleteStaleNonEncryptedSnapshotBackups", "CopyTagsToNewEncryptedVolumes" ] }, "additionalProperties": false, "required": [ "InstanceId", "VolumeIds", "KMSKeyId" ] } }, "metadata" : { "ui:order" : [ "DocumentName", "Region", "Parameters" ct-0hahohe17csnc Version April 22, 2025 1953 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] }, "required" : [ "DocumentName", "Region", "Parameters" ], "additionalProperties" : false } Schema for Change Type ct-0hi7z7tyikjf6 Classifications: • Management | Monitoring and notification | SQS | Update { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update SQS", "description": "Use to modify the properties of an existing Amazon Simple Queue Service instance.", "type": "object", "properties": { "VpcId": { "description": "ID of the VPC that contains the SQS queue, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "StackId": { "description": "ID of the stack instance that contains the SQS queue, in the form stack-a1b2c3d4e5f67890e.", "type": "string", "pattern": "^stack-[a-z0-9]{17}$" }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "SQSDelaySeconds": { "description": "The time in seconds that the delivery of new messages in the queue will be delayed.", ct-0hi7z7tyikjf6 Version April 22, 2025 1954 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "number", "minimum": 0, "maximum": 900, "default": 0 }, "SQSMaximumMessageSize": { "description": "The limit of how many bytes a message can contain before SQS rejects it.", "type": "number", "minimum": 1024, "maximum": 262144, "default": 262144 }, "SQSMessageRetentionPeriod": { "description": "The number of seconds SQS retains a message, from 60 (1 minute) to 1209600 (14 days).", "type": "number", "minimum": 60, "maximum": 1209600, "default": 345600 }, "SQSQueueName": { "description": "A name for the queue.", "type": "string", "pattern": "^[a-zA-Z0-9-_]{1,80}$", "minLength": 1, "maxLength": 80 }, "SQSReceiveMessageWaitTimeSeconds": { "description": "The number of seconds that the ReceiveMessage call waits for a message to arrive in the queue before returning a response.", "type": "number", "minimum": 0, "maximum": 20, "default": 0 }, "SQSVisibilityTimeout": { "description": "The number of seconds that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request.", "type": "number", "minimum": 0, "maximum": 43200 } ct-0hi7z7tyikjf6 Version April 22, 2025 1955 AMS Advanced Change Type Reference AMS Advanced Change Type Details } } }, "additionalProperties": false, "required": [ "VpcId", "StackId", "Parameters" ] } Schema for Change Type ct-0hu3q3957aghj Classifications: • Deployment | Advanced stack components | ACM | Create private certificate { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Private ACM Certificate", "description": "Create a private AWS Certificate Manager (ACM) certificate with email or DNS validation. To create a public ACM certificate, use ct-3ll9hnadql9s1.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-RequestACMCertificateV2", "type": "string", "enum": [ "AWSManagedServices-RequestACMCertificateV2" ], "default": "AWSManagedServices-RequestACMCertificateV2" }, "Region": { "description": "The AWS Region in which you want the ACM certificate, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "DomainName": { ct-0hu3q3957aghj Version April 22, 2025 1956 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The fully qualified domain name (FQDN), such as www.example.com, that you want to secure with an ACM certificate.", "type": "string", "pattern": "^(?!://)(?=.{1,255}$)((.{1,63}\\.){1,127}(?![0-9]*$)[a-z0-9-]+\ \.?)$" }, "CertificateType": { "description": "Confirm that you are creating a private ACM certificate. To create a public ACM certificate, use ct-3ll9hnadql9s1.", "type": "string", "enum": [ "Private" ], "default": "Private" }, "CertificateAuthorityArn": { "description": "The Amazon Resource Name (ARN) of the private certificate authority (CA) used to issue the certificate.", "type": "string", "pattern": "^arn:aws:.+$" }, "SubjectAlternativeNames": { "description": "Additional FQDNs to be included in the subject alternative name extension of the ACM certificate.", "type": "array", "items": { "type": "string", "pattern": "^(?!://)(?=.{1,255}$)((.{1,63}\\.){1,127}(?![0-9]*$)[a-z0-9-]+\ \.?)$" }, "minItems": 1, "maxItems": 5 }, "Route53DNSValidation": { "description": "True |
ams-ct-549 | ams-ct.pdf | 549 | with an ACM certificate.", "type": "string", "pattern": "^(?!://)(?=.{1,255}$)((.{1,63}\\.){1,127}(?![0-9]*$)[a-z0-9-]+\ \.?)$" }, "CertificateType": { "description": "Confirm that you are creating a private ACM certificate. To create a public ACM certificate, use ct-3ll9hnadql9s1.", "type": "string", "enum": [ "Private" ], "default": "Private" }, "CertificateAuthorityArn": { "description": "The Amazon Resource Name (ARN) of the private certificate authority (CA) used to issue the certificate.", "type": "string", "pattern": "^arn:aws:.+$" }, "SubjectAlternativeNames": { "description": "Additional FQDNs to be included in the subject alternative name extension of the ACM certificate.", "type": "array", "items": { "type": "string", "pattern": "^(?!://)(?=.{1,255}$)((.{1,63}\\.){1,127}(?![0-9]*$)[a-z0-9-]+\ \.?)$" }, "minItems": 1, "maxItems": 5 }, "Route53DNSValidation": { "description": "True for automatic ACM validation using your Route53 DNS, if the ACM and the domain are on the same account; false for no automatic validation. Default is false.", "type": "string", "enum": [ "True", "False" ], "default": "False" } ct-0hu3q3957aghj Version April 22, 2025 1957 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "metadata": { "ui:order": [ "DomainName", "CertificateType", "CertificateAuthorityArn", "SubjectAlternativeNames", "Route53DNSValidation" ] }, "additionalProperties": false, "required": [ "DomainName", "CertificateAuthorityArn" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0idxb0xsg1ui6 Classifications: • Management | Advanced stack components | RDS snapshot | Delete { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete RDS Snapshots", ct-0idxb0xsg1ui6 Version April 22, 2025 1958 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Delete DB instance or cluster snapshots. This document only supports deletion of 'manual' and 'awsbackup' snapshot types. If the snapshot is being copied, the copy operation is terminated. The snapshot must be in available state to be deleted. If one or more snapshots cannot be deleted, automation fails. Up to 20 snapshots can be deleted in one execution.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-DeleteRDSSnapshotsV2.", "type": "string", "enum": [ "AWSManagedServices-DeleteRDSSnapshotsV2" ], "default": "AWSManagedServices-DeleteRDSSnapshotsV2" }, "Region": { "description": "The AWS Region where the DB snapshots are located, in the form us-east-1.", "type": "string", "pattern": "[a-z]{2}-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "SnapshotNamesOrArns": { "description": "A list of up to 20 RDS snapshot names or ARN's to delete.", "type": "array", "items": { "type": "string", "pattern": "^(?!rds:).*$" }, "minItems": 1, "maxItems": 20 } }, "metadata": { "ui:order": [ "SnapshotNamesOrArns" ] }, "additionalProperties": false, "required": [ "SnapshotNamesOrArns" ] ct-0idxb0xsg1ui6 Version April 22, 2025 1959 AMS Advanced Change Type Reference AMS Advanced Change Type Details } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0ikpop8zqhkxg Classifications: • Management | Access | Stack admin access | Update { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update stack admin access", "description": "Update admin access for one or more users for one or more stacks. The maximum access time is 12 hours.", "type": "object", "properties": { "DomainFQDN": { "description": "The FQDN for the user accounts to grant access to.", "type": "string", "minLength": 1, "maxLength": 255 }, "StackIds": { "description": "A minimum of one stack ID is required.", "type": "array", "items": { "type": "string", "pattern": "^stack-[a-z0-9]{17}$|^SC-[0-9]{12}-pp-[a-zA-Z0-9]{13}$" ct-0ikpop8zqhkxg Version April 22, 2025 1960 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "minItems": 1, "uniqueItems": true }, "TimeRequestedInHours": { "description": "The amount of time, in hours, requested for access to the instance. Access is terminated after this time.", "type": "integer", "minimum": 1, "default": 1 }, "Usernames": { "description": "One or more Active Directory user names used to grant access.", "type": "array", "items": { "type": "string" }, "minItems": 1, "uniqueItems": true }, "VpcId": { "description": "The ID of the VPC that contains the stacks where access is required, in the form of vpc-12345678 or vpc-1234567890abcdef0.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" } }, "metadata": { "ui:order": [ "VpcId", "StackIds", "Usernames", "DomainFQDN", "TimeRequestedInHours" ] }, "additionalProperties": false, "required": [ "DomainFQDN", "StackIds", "Usernames", "VpcId" ] ct-0ikpop8zqhkxg Version April 22, 2025 1961 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Schema for Change Type ct-0ixp4ch2tiu04 Classifications: • Management | Applications | IAM instance profile | Create (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create IAM instance profile", "description": "Use to create an instance profile.", "type": "object", "properties": { "InstanceProfileDescription": { "description": "The description of the instance profile.", "type": "string", "maxLength": 5000 }, "InstanceProfileName": { "description": "The name of the instance profile to create.", "type": "string", "minLength": 1, "maxLength": 128, "pattern": "^[a-zA-Z0-9_.=@,+-]{1,128}$" }, "RelatedIds": { "description": "(Optional) IDs of resources related to the change request.", "type": "array", "items": { "type": "string" }, "minItems": 1, "maxItems": 1000, "uniqueItems": true }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", ct-0ixp4ch2tiu04 Version April 22, 2025 1962 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Medium", "High" ] } }, "additionalProperties": false, "required": [ "InstanceProfileDescription", "InstanceProfileName" ], "metadata": { "ui:order": [ |
ams-ct-550 | ams-ct.pdf | 550 | "description": "The name of the instance profile to create.", "type": "string", "minLength": 1, "maxLength": 128, "pattern": "^[a-zA-Z0-9_.=@,+-]{1,128}$" }, "RelatedIds": { "description": "(Optional) IDs of resources related to the change request.", "type": "array", "items": { "type": "string" }, "minItems": 1, "maxItems": 1000, "uniqueItems": true }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", ct-0ixp4ch2tiu04 Version April 22, 2025 1962 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Medium", "High" ] } }, "additionalProperties": false, "required": [ "InstanceProfileDescription", "InstanceProfileName" ], "metadata": { "ui:order": [ "InstanceProfileDescription", "InstanceProfileName", "RelatedIds", "Priority" ] } } Schema for Change Type ct-0jb01cofkhwk1 Classifications: • Management | Managed account | Stack access duration | Override (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Override Stack Access Duration", "description": "Use to override maximum stack access time for all stacks in this account for single landing zone (SALZ) and for all stacks of the member accounts of an organization for multi-landing zone (MALZ). For multi-landing zone (MALZ), please raise a request for change (RFC) from shared-services account with this change type (CT) ID. Access can be overridden from a minimum of 1 hour to a maximum of 120 hours, default stack access is granted for 12 hours.", "type": "object", "properties": { "TimeRequestedInHours": { "description": "The amount of time, in hours, requested to override. Access can be overridden from a minimum of 1 hour to a maximum of 120 hours, default stack access is granted for 12 hours. Access is terminated after this time.", "type": "integer", ct-0jb01cofkhwk1 Version April 22, 2025 1963 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minimum": 1, "maximum": 120, "default": 1 }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "metadata": { "ui:order": [ "TimeRequestedInHours", "Priority" ] }, "required": [ "TimeRequestedInHours" ], "additionalProperties": false } Schema for Change Type ct-0k4b96aatyqgl Classifications: • Management | Advanced stack components | Tag | Bulk update (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Bulk Update Resource Tags (Review Required)", "description": "Bulk add tags to existing, supported resources except those in AMS infrastructure stacks (stacks named mc-*). Tags simplify categorization, identification and targeting AWS resources. Use this with AWS Tag Editor when managing large numbers of tags (i.e. >50). For Autoscaling, EC2, Elastic Load Balancing, RDS resources and S3 buckets, use automated CT ct-3047c34zuvswh.", "type": "object", ct-0k4b96aatyqgl Version April 22, 2025 1964 AMS Advanced Change Type Reference "properties": { AMS Advanced Change Type Details "Description": { "description": "Meaningful information about the tag operation.", "type": "string", "maxLength": 5000 }, "CsvS3Url": { "description": "The S3 bucket endpoint for the CSV file with the tag update details. The CSV file must be formatted to the correct format. Please see AMS tag documentation for the correct format of the CSV file.", "type": "string", "pattern": "^https?://[a-z0-9]([-.a-z0-9]+)[a-z0-9]\\.s3\\.((([a-z]{2}-[a-z]+-\ \d{1}\\.)?))amazonaws\\.com/[\\S]*", "minLength": 1, "maxLength": 2000 }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "Description", "CsvS3Url", "Priority" ] }, "required": [ "Description", "CsvS3Url" ] } ct-0k4b96aatyqgl Version April 22, 2025 1965 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0kbey7hb00atp Classifications: • Deployment | Patching | SSM patch baseline | Create (Windows) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create SSM Patch Baseline (Windows)", "description": "Create an AWS Systems Manager (SSM) patch baseline to define which patches are approved for installation on your instances for Windows OS. Specify existing instance \"Patch Group\" tag values for the patch baseline. The patch baseline is an SSM resource that you can manage with the SSM console.", "additionalProperties": false, "properties": { "ApprovalRules": { "description": "Create auto-approval rules to specify that certain types of operating system patches are approved automatically.", "items": { "additionalProperties": false, "properties": { "ApproveAfterDays": { "default": 7, "description": "The number of days to wait after a patch is released before approving patches automatically.", "maximum": 100, "minimum": 0, "type": "integer" }, "Classification": { "description": "The Classification of the patches to be selected. Allowed values are \"CriticalUpdates\", \"DefinitionUpdates\", \"Drivers\", \"FeaturePacks \", \"SecurityUpdates\", \"ServicePacks\", \"Tools\", \"UpdateRollups\", \"Updates\", \"Upgrades\" and \"All\".", "items": { "enum": [ "CriticalUpdates", "DefinitionUpdates", "Drivers", "FeaturePacks", "SecurityUpdates", "ServicePacks", ct-0kbey7hb00atp Version April 22, 2025 1966 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Tools", "UpdateRollups", "Updates", "Upgrades", "All" ], "type": "string" }, "type": "array", "uniqueItems": true }, "Severity": { "description": "The severity of the patches to be selected. Allowed values are \"Critical\", \"Important\", \"Low\", \"Moderate\", \"Unspecified\" and \"All \".", "items": { "enum": [ "Critical", "Important", "Low", "Moderate", "Unspecified", "All" ], "type": "string" }, "type": "array", "uniqueItems": true } }, "metadata": { "ui:order": [ "Severity", "Classification", |
ams-ct-551 | ams-ct.pdf | 551 | \"DefinitionUpdates\", \"Drivers\", \"FeaturePacks \", \"SecurityUpdates\", \"ServicePacks\", \"Tools\", \"UpdateRollups\", \"Updates\", \"Upgrades\" and \"All\".", "items": { "enum": [ "CriticalUpdates", "DefinitionUpdates", "Drivers", "FeaturePacks", "SecurityUpdates", "ServicePacks", ct-0kbey7hb00atp Version April 22, 2025 1966 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Tools", "UpdateRollups", "Updates", "Upgrades", "All" ], "type": "string" }, "type": "array", "uniqueItems": true }, "Severity": { "description": "The severity of the patches to be selected. Allowed values are \"Critical\", \"Important\", \"Low\", \"Moderate\", \"Unspecified\" and \"All \".", "items": { "enum": [ "Critical", "Important", "Low", "Moderate", "Unspecified", "All" ], "type": "string" }, "type": "array", "uniqueItems": true } }, "metadata": { "ui:order": [ "Severity", "Classification", "ApproveAfterDays" ] }, "required": [ "ApproveAfterDays" ], "type": "object" }, "maxItems": 10, "minItems": 0, ct-0kbey7hb00atp Version April 22, 2025 1967 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "uniqueItems": true }, "ApprovedPatches": { "description": "The list of patches to approve explicitly.", "items": { "type": "string", "maxLength": 100, "minLength": 1, "pattern": "^(^KB[0-9]{1,7}$)|(^MS[0-9]{2}-[0-9]{3}$)" }, "maxItems": 50, "minItems": 0, "type": "array", "uniqueItems": true }, "Description": { "description": "A meaningful description for this patch baseline.", "maxLength": 500, "minLength": 1, "type": "string" }, "Name": { "description": "A friendly name for this patch baseline.", "maxLength": 128, "minLength": 3, "pattern": "^[a-zA-Z0-9._-]+$", "type": "string" }, "OperatingSystem": { "default": "Windows", "description": "The operating system of instances to which this baseline is applied.", "enum": [ "Windows" ], "type": "string" }, "PatchGroupTagValues": { "description": "A list of the values of your \"Patch Group\" tags on the instances you want patched; the values for up to twenty-five \"Patch Group\" tags can be provided. Instances with those values are associated with this patch baseline.", "items": { "maxLength": 256, ct-0kbey7hb00atp Version April 22, 2025 1968 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minLength": 1, "type": "string" }, "maxItems": 25, "minItems": 1, "type": "array", "uniqueItems": true }, "RejectedPatches": { "description": "The list of patches to reject explicitly.", "items": { "maxLength": 100, "minLength": 1, "pattern": "^(^KB[0-9]{1,7}$)|(^MS[0-9]{2}-[0-9]{3}$)", "type": "string" }, "maxItems": 50, "minItems": 0, "type": "array", "uniqueItems": true }, "Tags": { "description": "Up to fifty tags (key/value pairs) to categorize the SSM patch baseline resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ct-0kbey7hb00atp Version April 22, 2025 1969 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] }, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 50, "uniqueItems": true } }, "metadata": { "ui:order": [ "OperatingSystem", "Name", "Description", "PatchGroupTagValues", "ApprovalRules", "ApprovedPatches", "RejectedPatches", "Tags" ] }, "required": [ "Name", "PatchGroupTagValues", "OperatingSystem" ], "type": "object" } Schema for Change Type ct-0loed9dzig1ze Classifications: • Management | Advanced stack components | RDS database stack | Update Storage { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update RDS Storage", ct-0loed9dzig1ze Version April 22, 2025 1970 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Change the RDS instance storage type, capacity or IOPS through direct API calls. The RDS instance can be standalone or belong to a CloudFormation stack, in the latter case, the change might cause stack drift. To avoid causing stack drift, please use ct-12w49boaiwtzp instead, or ct-361tlo1k7339x if the RDS instance was provisioned via CFN ingestion.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-UpdateRDSStorage.", "type": "string", "enum": [ "AWSManagedServices-UpdateRDSStorage" ], "default": "AWSManagedServices-UpdateRDSStorage" }, "Region": { "description": "The AWS Region of the account with the RDS database instance; for example, us-east-1.", "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}" }, "Parameters": { "type": "object", "properties": { "DBInstanceIdentifier": { "description": "The identifier of the RDS database instance; for example, mydbinstance.", "type": "array", "items": { "type": "string", "pattern": "^(?!(mc|ams|awsms)-)[a-zA-Z]{1}(?!.*--)(?!.*-$)[A-Za-z0-9-] {0,62}$" }, "minItems": 1, "maxItems": 1 }, "AllocatedStorage": { "description": "The new amount of storage in gibibytes (GiB) to allocate for the DB instance.", "type": "array", "items": { "type": "string", "pattern": "^$|^\\d+$" }, ct-0loed9dzig1ze Version April 22, 2025 1971 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 0, "maxItems": 1 }, "MaxAllocatedStorage": { "description": "The upper limit in gibibytes (GiB) to which Amazon RDS can automatically scale the storage of the DB instance. To disable automatic scaling, set the value equal to AllocatedStorage.", "type": "array", "items": { "type": "string", "pattern": "^$|^\\d+$" }, "minItems": 0, "maxItems": 1 }, "StorageType": { "description": "The storage type to be associated with the DB instance.", "type": "array", "items": { "type": "string", "enum": [ "", "gp2", "gp3", "io1", "Magnetic" ], "default": "" } }, "Iops": { "description": "The new provisioned IOPS (I/O operations per second) value for the RDS instance. This parameter is only valid for io1 and gp3 storage type.", "type": "array", "items": { "type": "string", "pattern": "^$|^\\d+$", "default": "" } }, "ApplyImmediately": { "description": "True to apply the change immediately, false to schedule the change on next maintenance window. To discover your next maintenance window, check the details page for |
ams-ct-552 | ams-ct.pdf | 552 | }, "StorageType": { "description": "The storage type to be associated with the DB instance.", "type": "array", "items": { "type": "string", "enum": [ "", "gp2", "gp3", "io1", "Magnetic" ], "default": "" } }, "Iops": { "description": "The new provisioned IOPS (I/O operations per second) value for the RDS instance. This parameter is only valid for io1 and gp3 storage type.", "type": "array", "items": { "type": "string", "pattern": "^$|^\\d+$", "default": "" } }, "ApplyImmediately": { "description": "True to apply the change immediately, false to schedule the change on next maintenance window. To discover your next maintenance window, check the details page for the instance in the RDS console.", ct-0loed9dzig1ze Version April 22, 2025 1972 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "enum": [ "true", "false" ] } }, "metadata": { "ui:order": [ "DBInstanceIdentifier", "AllocatedStorage", "StorageType", "MaxAllocatedStorage", "Iops", "ApplyImmediately" ] }, "additionalProperties": false, "required": [ "DBInstanceIdentifier", "ApplyImmediately" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } ct-0loed9dzig1ze Version April 22, 2025 1973 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0lqruajvhwsbk Classifications: • Management | Advanced stack components | Security group | Authorize egress rule { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Authorize Egress Rule", "description": "Authorize the egress rule for the specified security group (SG). You must specify the configurations of the egress rule that you are authorizing. Note that this adds an egress rule to the specified SG but does not modify any existing egress rules.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-AuthorizeSecurityGroupEgressRule", "type": "string", "enum": [ "AWSManagedServices-AuthorizeSecurityGroupEgressRule" ], "default": "AWSManagedServices-AuthorizeSecurityGroupEgressRule" }, "Region": { "description": "The AWS Region in which the security group is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "SecurityGroupId": { "description": "The ID of the security group (SG) that you are updating, in the form sg-0123456789abcdef.", "type": "array", "items": { "type": "string", "pattern": "^sg-[0-9a-f]{8}$|^sg-[0-9a-f]{17}$" }, "minItems": 1, "maxItems": 1 ct-0lqruajvhwsbk Version April 22, 2025 1974 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "IpProtocol": { "description": "The IP protocol name, or IP protocol number, for the egress rule. For example, for TCP, enter either TCP, or (IP protocol number) 6. If you enter ICMP, you can specify any or all of the ICMP types and codes.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\+-\\\\(\\\\)\\w]{1,18}$" }, "minItems": 1, "maxItems": 1 }, "FromPort": { "description": "Start of allowed port range, from 0 to 65535 for TCP/UDP. For ICMP, use -1.", "type": "array", "items": { "type": "string", "pattern": "^-1$|^[0-9]{1,4}$|^[1-5][0-9]{4}$|^6[0-4][0-9]{3}$|^65[0-4] [0-9]{2}$|^655[0-2][0-9]$|^6553[0-5]$" }, "minItems": 1, "maxItems": 1 }, "ToPort": { "description": "End of allowed port range, from 0 to 65535 for TCP/UDP. For ICMP, use -1.", "type": "array", "items": { "type": "string", "pattern": "^-1$|^[0-9]{1,4}$|^[1-5][0-9]{4}$|^6[0-4][0-9]{3}$|^65[0-4] [0-9]{2}$|^655[0-2][0-9]$|^6553[0-5]$" }, "minItems": 1, "maxItems": 1 }, "Destination": { "description": "An IP address, in the form 255.255.255.255, or an IP address range in CIDR notation, in the form 255.255.255.255/32, or the ID of another security group in the same region; or self to specify the same security group.", "type": "array", "items": { "type": "string", ct-0lqruajvhwsbk Version April 22, 2025 1975 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^(([0-9][0-9]{0,1}|1[0-9]{2}|2[0-4][0-9]|25[0-5])\\.){3}([0-9] [0-9]{0,1}|1[0-9]{2}|2[0-4][0-9]|25[0-5])(\\/([0-9]|[1-2][0-9]|3[0-2])){0,1}$|^sg- [0-9a-f]{8}$|^sg-[0-9a-f]{17}$|^self$" }, "minItems": 1, "maxItems": 1 }, "Description": { "description": "A meaningful description of the egress rule.", "type": "array", "items": { "type": "string", "pattern": "^$|^[ a-zA-Z0-9._\\-:/()#,@\\[\\]+=&;{}!$\\*]{1,255}$" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "SecurityGroupId", "IpProtocol", "FromPort", "ToPort", "Destination", "Description" ] }, "required": [ "SecurityGroupId", "IpProtocol", "FromPort", "ToPort", "Destination" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] ct-0lqruajvhwsbk Version April 22, 2025 1976 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "required": [ "DocumentName", "Region", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0ltm873rsebx9 Classifications: • Management | Advanced stack components | Load balancer (ELB) stack | Update { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update load balancer (ELB) stack", "description": "Modify the properties of an existing Amazon ELB Classic Load Balancer created using CT id ct-12amsdz909cfh, version 3.0.", "type": "object", "properties": { "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "StackId": { "description": "The stack ID of the ELB that you are updating, in the form stack- a1b2c3d4e5f67890e.", "type": "string", "pattern": "^stack-[a-z0-9]{17}$" }, "Parameters": { "description": "Specifications for updating the ELB.", "type": "object", "properties": { "ELBSubnetIds": { "description": "One or more subnet IDs for the load balancer, in the form subnet-0123abcd or subnet-01234567890abcdef. Changing this value during an update ct-0ltm873rsebx9 Version April 22, 2025 1977 AMS Advanced Change Type Reference AMS Advanced Change Type Details does not append to the existing subnets associated with the load balancer. Include all required subnets when modifying this value.", "type": "array", "items": { |
ams-ct-553 | ams-ct.pdf | 553 | }, "StackId": { "description": "The stack ID of the ELB that you are updating, in the form stack- a1b2c3d4e5f67890e.", "type": "string", "pattern": "^stack-[a-z0-9]{17}$" }, "Parameters": { "description": "Specifications for updating the ELB.", "type": "object", "properties": { "ELBSubnetIds": { "description": "One or more subnet IDs for the load balancer, in the form subnet-0123abcd or subnet-01234567890abcdef. Changing this value during an update ct-0ltm873rsebx9 Version April 22, 2025 1977 AMS Advanced Change Type Reference AMS Advanced Change Type Details does not append to the existing subnets associated with the load balancer. Include all required subnets when modifying this value.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 1, "uniqueItems": true }, "ELBBackendInstances": { "description": "One or more EC2 instance IDs to associate with the load balancer, in the form of i-0123abcd or i-01234567890abcdef for a single instance, or i-0123abcd,i-12345abcd or i-01234567890abcdef,i-2345678901abcdefg for multiple instances. A load balancer can be associated with an autoscaling group by specifying the load balancer name in the ASGLoadBalancerNames property during creation or update of the autoscaling group. Changing this value during an update does not append to the existing instances associated with the load balancer. Include all required EC2 instances not part of an autoscaling group when modifying this value. To remove all EC2 instances not part of an autoscaling group during an update specify None.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-z0-9]{8}$|^i-[a-z0-9]{17}$|^[Nn]one$|^$" }, "minItems": 1, "uniqueItems": true }, "ELBCrossZone": { "description": "With cross-zone load balancing, your load balancer nodes route traffic to the back-end instances across all Availability Zones. True to enable, false to disable. The default is true.", "type": "boolean" }, "ELBCookieExpirationPeriod": { "description": "The time period, in seconds, after which the cookie is considered stale. If this parameter isn't specified, the sticky session lasts for the duration of the browser session.", "type": "string", "pattern": "^[0-9]+$|^$" }, "ELBCookieExpirationPeriod2": { ct-0ltm873rsebx9 Version April 22, 2025 1978 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The time period, in seconds, after which the cookie is considered stale. If this parameter isn't specified, the sticky session lasts for the duration of the browser session.", "type": "string", "pattern": "^[0-9]+$|^$" }, "ELBCookieStickinessPolicyName": { "description": "A name for the cookie stickiness policy. The name must be unique within the set of policies for this load balancer.", "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "ELBCookieStickinessPolicyName2": { "description": "A name for the second cookie stickiness policy. The name must be unique within the set of policies for this load balancer.", "type": "string", "pattern": "^[a-zA-Z0-9]{1,1}[a-zA-Z0-9-]{0,127}$|^$" }, "ELBHealthCheckHealthyThreshold": { "description": "The number of consecutive health check successes required to declare an EC2 instance healthy.", "type": "number", "minimum": 2, "maximum": 10 }, "ELBHealthCheckInterval": { "description": "The approximate interval, in seconds, between health checks.", "type": "number", "minimum": 5, "maximum": 300 }, "ELBHealthCheckTarget": { "description": "The protocol, port, and path of the instance to check. For example, HTTP:80/weather/us/wa/seattle. The protocol can be TCP, HTTP, HTTPS, or SSL. The range of valid ports is 1 through 65535.", "type": "string", "pattern": "^(HTTP|HTTPS):[0-9]{1,5}[/][a-zA-Z0-9/_.-]*$|^(SSL|TCP):[0-9] {1,5}$" }, "ELBHealthCheckTimeout": { "description": "The amount of time, in seconds, to wait for a response to a health check. Must be less than the value for ELBHealthCheckInterval.", "type": "number", ct-0ltm873rsebx9 Version April 22, 2025 1979 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minimum": 2, "maximum": 60 }, "ELBHealthCheckUnhealthyThreshold": { "description": "The number of consecutive health check failures required to declare an EC2 instance unhealthy.", "type": "number", "minimum": 2, "maximum": 10 }, "ELBIdleTimeout": { "description": "The time, in seconds, that a connection to the load balancer can remain idle, which means no data is sent over the connection. After the specified time, the load balancer closes the connection.", "type": "number", "minimum": 1, "maximum": 3600 }, "ELBInstancePort": { "description": "The TCP port the listener uses to send traffic to the target instance. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "pattern": "^[0-9]{1,5}$" }, "ELBInstancePort2": { "description": "The TCP port the optional second listener uses to send traffic to the target instance. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "pattern": "^[0-9]{1,5}$" }, "ELBInstanceProtocol": { "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance). Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ct-0ltm873rsebx9 Version April 22, 2025 1980 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] }, "ELBInstanceProtocol2": { "description": "The protocol the second listener uses for routing traffic to |
ams-ct-554 | ams-ct.pdf | 554 | will be unable to connect during this time.", "type": "string", "pattern": "^[0-9]{1,5}$" }, "ELBInstanceProtocol": { "description": "The protocol the listener uses for routing traffic to back- end connections (load balancer to backend instance). Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ct-0ltm873rsebx9 Version April 22, 2025 1980 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] }, "ELBInstanceProtocol2": { "description": "The protocol the second listener uses for routing traffic to back-end connections (load balancer to backend instance). Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "ELBLoadBalancerPort": { "description": "The port number for the load balancer to use when routing external incoming traffic. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "pattern": "^[0-9]{1,5}$" }, "ELBLoadBalancerPort2": { "description": "The port number for the load balancer to use when routing external incoming traffic on the second listener. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "pattern": "^[0-9]{1,5}$" }, "ELBLoadBalancerProtocol": { "description": "The transport protocol to use for routing front-end connections (client to load balancer). Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, ct-0ltm873rsebx9 Version April 22, 2025 1981 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ELBLoadBalancerProtocol2": { "description": "The transport protocol to use for routing front-end connections (client to load balancer) on the second listener. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "enum": [ "HTTP", "HTTPS", "SSL", "TCP" ] }, "ELBSSLCertificateId": { "description": "The Amazon Resource Name (ARN) of the SSL certificate to use, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012. This must be specified if the HTTPS or SSL protocol is specified for ELBLoadBalancerProtocol. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "pattern": "^$|(arn:aws:acm:[a-z1-9\\-]{9,15}:[0-9]{12}:certificate/[a-z0-9] {8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12})|(arn:aws:iam::[0-9]{12}:server- certificate/[\\w+=,.@-]+)$|^([a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9] {12})$" }, "ELBSSLCertificateId2": { "description": "The Amazon Resource Name (ARN) of the SSL certificate to use for the optional second listener, in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012. Required only if a second listener is used and ELBLoadBalancerProtocol2 is either HTTPS or SSL. Changing this value during an update will cause the existing listener to be deleted and a new one created. Clients will be unable to connect during this time.", "type": "string", "pattern": "^$|(arn:aws:acm:[a-z1-9\\-]{9,15}:[0-9]{12}:certificate/[a-z0-9] {8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12})|(arn:aws:iam::[0-9]{12}:server- certificate/[\\w+=,.@-]+)$|^([a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9] {12})$" } }, "metadata": { "ui:order": [ "ELBSubnetIds", "ELBBackendInstances", ct-0ltm873rsebx9 Version April 22, 2025 1982 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ELBIdleTimeout", "ELBCrossZone", "ELBHealthCheckTarget", "ELBHealthCheckInterval", "ELBHealthCheckTimeout", "ELBHealthCheckHealthyThreshold", "ELBHealthCheckUnhealthyThreshold", "ELBCookieStickinessPolicyName", "ELBCookieExpirationPeriod", "ELBInstancePort", "ELBInstanceProtocol", "ELBLoadBalancerPort", "ELBLoadBalancerProtocol", "ELBSSLCertificateId", "ELBCookieExpirationPeriod2", "ELBCookieStickinessPolicyName2", "ELBInstancePort2", "ELBInstanceProtocol2", "ELBLoadBalancerPort2", "ELBLoadBalancerProtocol2", "ELBSSLCertificateId2" ] }, "additionalProperties": false } }, "metadata": { "ui:order": [ "VpcId", "StackId", "Parameters" ] }, "additionalProperties": false, "required": [ "VpcId", "StackId", "Parameters" ] } ct-0ltm873rsebx9 Version April 22, 2025 1983 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0mss4i7neuj7f Classifications: • Management | Managed Firewall | Outbound (Palo Alto) | Update security policy { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Security Policy", "description": "Update a security policy for AMS managed Palo Alto firewall - Outbound.", "type": "object", "properties": { "RequestType": { "description": "Must be UpdateSecurityPolicy.", "type": "string", "enum": [ "UpdateSecurityPolicy" ], "default": "UpdateSecurityPolicy" }, "Parameters": { "type": "object", "properties": { "SecurityPolicyName": { "description": "The name of the security policy. Must start with custom- sec-.", "type": "string", "pattern": "^custom-sec-[a-zA-Z0-9][a-zA-Z0-9-_]{0,51}$" }, "SourceAddressesToAdd": { "description": "A list of source addresses to add to the policy.", "type": "array", "items": { "type": "string", "pattern": "^([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+(/[0-9]{1,2})?)$" }, "minItems": 1, "maxItems": 50 }, "DestinationAddressesToAdd": { ct-0mss4i7neuj7f Version April 22, 2025 1984 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A list of destination addresses to add to the policy. Supply values for this parameter or for AllowListsToAdd, but not both.", "type": "array", "items": { "type": "string", "pattern": "^(([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+(/[0-9]{1,2})?)|((([a-zA- Z0-9][a-zA-Z0-9-_]{0,62}[a-zA-Z0-9]{0,1}))\\.){1,127}([a-zA-Z][a-zA-Z0-9\\-]{0,23}[a- zA-Z]))$" }, "minItems": 1, "maxItems": 50 }, "AllowListsToAdd": { "description": "A list of allowlists to add to the policy. Supply values for this parameter or for DestinationAddressesToAdd, but not both.", "type": "array", "items": { "type": "string", |
ams-ct-555 | ams-ct.pdf | 555 | policy.", "type": "array", "items": { "type": "string", "pattern": "^([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+(/[0-9]{1,2})?)$" }, "minItems": 1, "maxItems": 50 }, "DestinationAddressesToAdd": { ct-0mss4i7neuj7f Version April 22, 2025 1984 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A list of destination addresses to add to the policy. Supply values for this parameter or for AllowListsToAdd, but not both.", "type": "array", "items": { "type": "string", "pattern": "^(([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+(/[0-9]{1,2})?)|((([a-zA- Z0-9][a-zA-Z0-9-_]{0,62}[a-zA-Z0-9]{0,1}))\\.){1,127}([a-zA-Z][a-zA-Z0-9\\-]{0,23}[a- zA-Z]))$" }, "minItems": 1, "maxItems": 50 }, "AllowListsToAdd": { "description": "A list of allowlists to add to the policy. Supply values for this parameter or for DestinationAddressesToAdd, but not both.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9][a-zA-Z0-9-_]{0,62}$" }, "minItems": 1, "maxItems": 10 }, "ServicePortsToAdd": { "type": "object", "description": "A list of Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) service ports to add.", "properties": { "TCPPortsToAdd": { "description": "A list of Transmission Control Protocol (TCP) service ports to add.", "type": "array", "items": { "type": "integer", "minimum": 1, "maximum": 65535 }, "minItems": 1, "maxItems": 50 }, "UDPPortsToAdd": { "description": "A list of User Datagram Protocol (UDP) service ports to add.", "type": "array", ct-0mss4i7neuj7f Version April 22, 2025 1985 AMS Advanced Change Type Reference AMS Advanced Change Type Details "items": { "type": "integer", "minimum": 1, "maximum": 65535 }, "minItems": 1, "maxItems": 50 } }, "metadata": { "ui:order": [ "TCPPortsToAdd", "UDPPortsToAdd" ] } }, "SourceAddressesToRemove": { "description": "A list of source addresses to remove from the policy.", "type": "array", "items": { "type": "string", "pattern": "^([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+(/[0-9]{1,2})?)$" }, "minItems": 1, "maxItems": 50 }, "DestinationAddressesToRemove": { "description": "A list of destination addresses to remove from the policy. Supply values for this parameter or for AllowListsToRemove, but not both.", "type": "array", "items": { "type": "string", "pattern": "^(([0-9]+\\.[0-9]+\\.[0-9]+\\.[0-9]+(/[0-9]{1,2})?)|((([a-zA- Z0-9][a-zA-Z0-9-_]{0,62}[a-zA-Z0-9]{0,1}))\\.){1,127}([a-zA-Z][a-zA-Z0-9\\-]{0,23}[a- zA-Z]))$" }, "minItems": 1, "maxItems": 50 }, "AllowListsToRemove": { "description": "A list of allowlists to remove from the policy. Supply values for this parameter or for DestinationAddressesToRemove, but not both.", "type": "array", "items": { ct-0mss4i7neuj7f Version April 22, 2025 1986 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "pattern": "^[a-zA-Z0-9][a-zA-Z0-9-_]{0,62}$" }, "minItems": 1, "maxItems": 10 }, "ServicePortsToRemove": { "type": "object", "description": "A list of Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) service ports to remove.", "properties": { "TCPPortsToRemove": { "description": "A list of Transmission Control Protocol (TCP) service ports to remove.", "type": "array", "items": { "type": "integer", "minimum": 1, "maximum": 65535 }, "minItems": 1, "maxItems": 50 }, "UDPPortsToRemove": { "description": "A list of User Datagram Protocol (UDP) service ports to remove.", "type": "array", "items": { "type": "integer", "minimum": 1, "maximum": 65535 }, "minItems": 1, "maxItems": 50 } }, "metadata": { "ui:order": [ "TCPPortsToRemove", "UDPPortsToRemove" ] } }, "ActionType": { ct-0mss4i7neuj7f Version April 22, 2025 1987 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The type of action the security policy will perform on outbound traffic that matches the policy's rules.", "type": "string", "enum": [ "Allow", "Deny" ] }, "EnablePolicy": { "description": "True to enable the security policy, false to disable it.", "type": "boolean" } }, "additionalProperties": false, "metadata": { "ui:order": [ "SecurityPolicyName", "SourceAddressesToAdd", "DestinationAddressesToAdd", "AllowListsToAdd", "ServicePortsToAdd", "SourceAddressesToRemove", "DestinationAddressesToRemove", "AllowListsToRemove", "ServicePortsToRemove", "ActionType", "EnablePolicy" ] }, "required": [ "SecurityPolicyName" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "RequestType", "Parameters" ] }, "required": [ "RequestType", "Parameters" ct-0mss4i7neuj7f Version April 22, 2025 1988 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] } Schema for Change Type ct-0o4zi9bzg74lp Classifications: • Management | Advanced stack components | S3 storage | Add event notification { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Add Event Notification", "description": "Add an event notification to the specified S3 bucket through direct API calls. The S3 bucket can be standalone or belong to a CloudFormation stack. For buckets in CloudFormation stacks, be aware that stack drift might occur if the bucket was provisioned through CFN ingestion.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-AddBucketEventNotification.", "type": "string", "enum": [ "AWSManagedServices-AddBucketEventNotification" ], "default": "AWSManagedServices-AddBucketEventNotification" }, "Region": { "description": "The AWS Region in which the source bucket is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "BucketName": { "description": "The name of the bucket for which to add the notification configuration.", "type": "string", "pattern": "^(?!(mc|ams|awsms)-)[a-z0-9][-.a-z0-9]{1,61}[a-z0-9]$" }, "EventName": { ct-0o4zi9bzg74lp Version April 22, 2025 1989 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A unique identifier for the event notification configuration.", "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9-]{1,255}$" }, "Prefix": { "description": "The object key name prefix to which the filtering rule applies. If a value is specified, event notifications will be limited to objects with key starting with the specified characters.", "type": "string", "pattern": "^.{0,1024}$", "default": "" }, "Suffix": { "description": "The object key name suffix to which the filtering rule applies. If a value is specified, event notifications will be limited to objects with key ending with the specified characters.", "type": "string", "pattern": "^.{0,1024}$", "default": "" }, "EventTypes": |
ams-ct-556 | ams-ct.pdf | 556 | AMS Advanced Change Type Details "description": "A unique identifier for the event notification configuration.", "type": "string", "pattern": "^[a-zA-Z][a-zA-Z0-9-]{1,255}$" }, "Prefix": { "description": "The object key name prefix to which the filtering rule applies. If a value is specified, event notifications will be limited to objects with key starting with the specified characters.", "type": "string", "pattern": "^.{0,1024}$", "default": "" }, "Suffix": { "description": "The object key name suffix to which the filtering rule applies. If a value is specified, event notifications will be limited to objects with key ending with the specified characters.", "type": "string", "pattern": "^.{0,1024}$", "default": "" }, "EventTypes": { "description": "Specify the events for which you want to receive notifications. Enter '*' if you would like to enable notifications for all available event types or if selecting EventBridge as the destination. Refer to https:// docs.aws.amazon.com/AmazonS3/latest/userguide/notification-how-to-event-types-and- destinations.html#supported-notification-event-types for details on the values.", "type": "array", "items": { "enum": [ "s3:ObjectCreated:*", "s3:ObjectCreated:Put", "s3:ObjectCreated:Post", "s3:ObjectCreated:Copy", "s3:ObjectCreated:CompleteMultipartUpload", "s3:ObjectRemoved:*", "s3:ObjectRemoved:Delete", "s3:ObjectRemoved:DeleteMarkerCreated", "s3:ObjectRestore:*", "s3:ObjectRestore:Post", "s3:ObjectRestore:Completed", "s3:ObjectRestore:Delete", "s3:ReducedRedundancyLostObject", "s3:Replication:*", ct-0o4zi9bzg74lp Version April 22, 2025 1990 AMS Advanced Change Type Reference AMS Advanced Change Type Details "s3:Replication:OperationFailedReplication", "s3:Replication:OperationMissedThreshold", "s3:Replication:OperationReplicatedAfterThreshold", "s3:Replication:OperationNotTracked", "s3:LifecycleExpiration:*", "s3:LifecycleExpiration:Delete", "s3:LifecycleExpiration:DeleteMarkerCreated", "s3:LifecycleTransition", "s3:IntelligentTiering", "s3:ObjectTagging:*", "s3:ObjectTagging:Put", "s3:ObjectTagging:Delete", "s3:ObjectAcl:Put", "*" ], "type": "string" }, "minItems": 1, "maxItems": 27 }, "DestinationARN": { "description": "The Amazon Resource Name (ARN) of the Amazon SQS queue, the Amazon SNS topic or the Lambda function to which Amazon S3 publishes a message when it detects events of the specified type. Input 'eventbridge' for using EventBridge as destination.", "type": "string", "pattern": "(^arn:(aws|aws-cn|aws-us-gov):(lambda|sns|sqs):\\w{2}-[a-z]+-\ \d{1}:\\d{12}:((function:[a-zA-Z0-9-_]{1,64})|([a-zA-Z0-9-_.]{1,256}))|eventbridge)$" } }, "metadata": { "ui:order": [ "BucketName", "EventName", "EventTypes", "DestinationARN", "Prefix", "Suffix" ] }, "additionalProperties": false, "required": [ "BucketName", "EventName", ct-0o4zi9bzg74lp Version April 22, 2025 1991 AMS Advanced Change Type Reference AMS Advanced Change Type Details "EventTypes", "DestinationARN" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0pgvtw5rpcsb6 Classifications: • Deployment | Advanced stack components | RDS database stack | Create from backup { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create RDS From Backup", "description": "Create an Amazon Relational Database Service (RDS) from a backup. When you restore a backup this way, the service-specific restore parameters are presented automatically.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { ct-0pgvtw5rpcsb6 Version April 22, 2025 1992 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "ID of the VPC where the backup is stored, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "StackTemplateId": { "description": "Must be stm-siqajx00000000000.", "type": "string", "enum": [ "stm-siqajx00000000000" ] }, "Name": { "description": "A name for the stack; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,255}$", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, ct-0pgvtw5rpcsb6 Version April 22, 2025 1993 AMS Advanced Change Type Reference AMS Advanced Change Type Details "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 50, "uniqueItems": true }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 360, "default": 60 }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "DBInstanceClass": { "description": "The compute and memory capacity for the DB instance. To inherit this value from the backup, use inherit.", "type": "string", "enum": [ "inherit", "db.m1.small", "db.m1.medium", "db.m1.large", "db.m1.xlarge", "db.m2.xlarge", "db.m2.2xlarge", "db.m2.4xlarge", "db.m3.medium", "db.m3.large", "db.m3.xlarge", "db.m3.2xlarge", "db.m4.large", "db.m4.xlarge", "db.m4.2xlarge", "db.m4.4xlarge", "db.m4.10xlarge", ct-0pgvtw5rpcsb6 Version April 22, 2025 1994 AMS Advanced Change Type Reference AMS Advanced Change Type Details "db.m4.16xlarge", "db.r3.large", "db.r3.xlarge", "db.r3.2xlarge", "db.r3.4xlarge", "db.r3.8xlarge", "db.r4.large", "db.r4.xlarge", "db.r4.2xlarge", "db.r4.4xlarge", "db.r4.8xlarge", "db.r4.16xlarge", "db.t1.micro", "db.t2.micro", "db.t2.small", "db.t2.medium", "db.t2.large", "db.t2.xlarge", "db.t2.2xlarge" ], "default": "inherit" }, "DBInstanceIdentifier": { "description": "A name for the DB instance. If you specify a name, it is converted to lowercase. If you don't specify a name, a unique physical ID is generated and used for the DBInstanceIdentifier.", "type": "string", "pattern": "^[a-zA-Z]{1}(?!.*--)(?!.*-$)[A-Za-z0-9-]{0,62}$|^$", "default": "" }, "DBSnapshotIdentifier": { "description": "The name of the RDS DB backup to use, in the form awsbackup:job-00000000-0000-0000-0000-000000000000.", "type": "string" }, "DBSubnetIds": { "description": "Two or more subnet IDs for the DB instance, in the form subnet-0123abcd or subnet-01234567890abcdef, spanning at least two Availability Zones.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, ct-0pgvtw5rpcsb6 Version April 22, 2025 1995 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 2, "maxItems": 20, "uniqueItems": true } }, "metadata": { "ui:order": [ "DBInstanceClass", |
ams-ct-557 | ams-ct.pdf | 557 | name, a unique physical ID is generated and used for the DBInstanceIdentifier.", "type": "string", "pattern": "^[a-zA-Z]{1}(?!.*--)(?!.*-$)[A-Za-z0-9-]{0,62}$|^$", "default": "" }, "DBSnapshotIdentifier": { "description": "The name of the RDS DB backup to use, in the form awsbackup:job-00000000-0000-0000-0000-000000000000.", "type": "string" }, "DBSubnetIds": { "description": "Two or more subnet IDs for the DB instance, in the form subnet-0123abcd or subnet-01234567890abcdef, spanning at least two Availability Zones.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, ct-0pgvtw5rpcsb6 Version April 22, 2025 1995 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 2, "maxItems": 20, "uniqueItems": true } }, "metadata": { "ui:order": [ "DBInstanceClass", "DBInstanceIdentifier", "DBSnapshotIdentifier", "DBSubnetIds" ] }, "additionalProperties": false, "required": [ "DBSnapshotIdentifier", "DBSubnetIds" ] } }, "metadata": { "ui:order": [ "Name", "Description", "VpcId", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "additionalProperties": false, "required": [ "Description", "VpcId", "StackTemplateId", "Name", "Parameters" ] } ct-0pgvtw5rpcsb6 Version April 22, 2025 1996 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0q0bic0ywqk6c Classifications: • Management | Advanced stack components | Stack | Delete • Management | Standard stacks | Stack | Delete { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete stack", "description": "Delete an existing stack and its resources from your account. The effects of deleting a resource vary. For details, see the appropriate AWS documentation for the resource. Note that termination protection on a resource in the stack causes the RFC to fail. To check for a resource's termination protection status, see the corresponding AWS console.", "type": "object", "properties": { "StackId": { "description": "The ID of the stack instance to delete, in the form stack- a1b2c3d4e5f67890e.", "type": "string", "pattern": "^stack-[a-z0-9]{17}$" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of deleting the stack. This does not prolong the execution. If the delete is not completed in the specified time, the RFC is failed and you are notified that the delete is over time but continuing. The delete operation continues because delete operations cannot be rolled back. Set this timeout so you get notice of delete stack problems in a timely manner. Defaults to 60 if not provided.", "type": "number", "minimum": 0, "maximum": 720 } }, "additionalProperties": false, "required": [ "StackId" ] } ct-0q0bic0ywqk6c Version April 22, 2025 1997 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0q43l40hxrzum Classifications: • Deployment | Advanced stack components | Redshift | Create (cluster subnet group) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Redshift cluster subnet group", "description": "Use to create a Redshift cluster subnet group.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, ct-0q43l40hxrzum Version April 22, 2025 1998 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 50, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-5rsvv3l4760usboci", "type": "string", "enum": [ "stm-5rsvv3l4760usboci" ], "default": "stm-5rsvv3l4760usboci" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", "minimum": 0, "maximum": 60, "default": 60 }, "Parameters": { "type": "object", "properties": { "SubnetGroupDescription": { "type": "string", ct-0q43l40hxrzum Version April 22, 2025 1999 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "A description to help identify your cluster subnet group.", "minLength": 1, "maxLength": 255 }, "SubnetIds": { "type": "array", "minItems": 2, "uniqueItems": true, "description": "Two or more subnet IDs for the cluster subnet group, in the form subnet-0123abcd or subnet-01234567890abcdef, spanning at least two Availability Zones.", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" } } }, "metadata": { "ui:order": [ "SubnetGroupDescription", "SubnetIds" ] }, "required": [ "SubnetGroupDescription", "SubnetIds" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", ct-0q43l40hxrzum Version April 22, 2025 2000 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } Schema for Change Type ct-0qbikxr9okwvy Classifications: • Deployment | Advanced stack components | VPN Gateway | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create VPN Gateway", "description": "Create a virtual private network (VPN) gateway (the endpoint on the VPC side of your VPN |
ams-ct-558 | ams-ct.pdf | 558 | }, "metadata": { "ui:order": [ "SubnetGroupDescription", "SubnetIds" ] }, "required": [ "SubnetGroupDescription", "SubnetIds" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Description", "VpcId", "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", ct-0q43l40hxrzum Version April 22, 2025 2000 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Name", "Parameters", "TimeoutInMinutes", "StackTemplateId" ], "additionalProperties": false } Schema for Change Type ct-0qbikxr9okwvy Classifications: • Deployment | Advanced stack components | VPN Gateway | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create VPN Gateway", "description": "Create a virtual private network (VPN) gateway (the endpoint on the VPC side of your VPN connection), and associate it to an existing virtual private cloud (VPC) in your account.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the VPC to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { ct-0qbikxr9okwvy Version April 22, 2025 2001 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Up to fifty tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 0, "maxItems": 50, "uniqueItems": true }, "StackTemplateId": { "description": "Must be stm-mcti3bha1vhon1sie", "type": "string", "enum": [ "stm-mcti3bha1vhon1sie" ], "default": "stm-mcti3bha1vhon1sie" }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", ct-0qbikxr9okwvy Version April 22, 2025 2002 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "number", "minimum": 0, "maximum": 60, "default": 60 }, "Parameters": { "type": "object", "properties": { "VpcId": { "type": "string", "description": "The VPC ID to associate the VPN Gateway to.", "pattern": "^vpc-[0-9a-z]{17}|vpc-[0-9a-z]{8}$" }, "AmazonSideAsn": { "type": "integer", "description": "The private Autonomous System Number (ASN) for the Amazon side of a Border Gateway Protocol (BGP) session.", "default": 64512 }, "Name": { "type": "string", "description": "The tag Key name of the new VPN Gateway.", "pattern": "^[a-zA-Z0-9._-]+$", "minLength": 1, "maxLength": 255 } }, "metadata": { "ui:order": [ "VpcId", "AmazonSideAsn", "Name" ] }, "required": [ "VpcId" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Name", "Description", ct-0qbikxr9okwvy Version April 22, 2025 2003 AMS Advanced Change Type Reference AMS Advanced Change Type Details "VpcId", "Parameters", "TimeoutInMinutes", "StackTemplateId", "Tags" ] }, "required": [ "Description", "VpcId", "Name", "TimeoutInMinutes", "StackTemplateId", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0rmgrnr9w8mzh Classifications: • Management | Managed landing zone | Networking account | Remove TGW static route { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Remove TGW Static Route", "description": "Remove the specified TGW static route from the specified transit gateway (TGW) route table. Use this multi-account landing zone (MALZ) change type only in a Networking account.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-RemoveRouteFromTGWRouteTable.", "type": "string", "enum": [ "AWSManagedServices-RemoveRouteFromTGWRouteTable" ], "default": "AWSManagedServices-RemoveRouteFromTGWRouteTable" }, "Region": { "description": "The AWS Region of the account.", ct-0rmgrnr9w8mzh Version April 22, 2025 2004 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "enum": [ "us-east-1", "us-east-2", "us-west-1", "us-west-2", "eu-west-1", "eu-west-2", "eu-west-3", "eu-south-1", "eu-north-1", "eu-central-1", "ca-central-1", "ap-southeast-1", "ap-southeast-2", "ap-southeast-3", "ap-south-1", "ap-northeast-1", "ap-northeast-2", "ap-northeast-3", "ap-east-1", "sa-east-1", "me-south-1", "af-south-1", "us-gov-west-1", "us-gov-east-1", "cn-northwest-1", "cn-north-1" ] }, "Parameters": { "type": "object", "properties": { "TransitGatewayRouteTableId": { "description": "The ID of the TGW route table.", "type": "array", "items": { "type": "string", "pattern": "^tgw-rtb-[a-z0-9]{17}$" }, "maxItems": 1 }, "DestinationCidrBlock": { "description": "The IPV4 CIDR range used for destination matches.", ct-0rmgrnr9w8mzh Version April 22, 2025 2005 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "pattern": "^(([0-9][0-9]{0,1}|1[0-9]{2}|2[0-4][0-9]|25[0-5]).){3}([0-9] [0-9]{0,1}|1[0-9]{2}|2[0-4][0-9]|25[0-5])(/([0-9]|[1-2][0-9]|3[0-2])){0,1}$" }, "maxItems": 1 } }, "metadata": { "ui:order": [ "TransitGatewayRouteTableId", "DestinationCidrBlock" ] }, "additionalProperties": false, "required": [ "TransitGatewayRouteTableId", "DestinationCidrBlock" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0tmpmp1wpgkr9 Classifications: • Management | Advanced stack components | EC2 instance stack | Update instance detailed monitoring ct-0tmpmp1wpgkr9 Version April 22, 2025 2006 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Detailed Monitoring", "description": "Update EC2 instances' detailed monitoring setting through direct API calls. The EC2 instances can be standalone or belong to a CloudFormation stack; in the latter case, the change might cause stack drift. To avoid causing stack drift, please use ct-38s4s4tm4ic4u instead, or ct-361tlo1k7339x if the EC2 instance was provisioned via CFN ingestion.", "type": "object", "properties": { "DocumentName": |
ams-ct-559 | ams-ct.pdf | 559 | Change Type ct-0tmpmp1wpgkr9 Classifications: • Management | Advanced stack components | EC2 instance stack | Update instance detailed monitoring ct-0tmpmp1wpgkr9 Version April 22, 2025 2006 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Detailed Monitoring", "description": "Update EC2 instances' detailed monitoring setting through direct API calls. The EC2 instances can be standalone or belong to a CloudFormation stack; in the latter case, the change might cause stack drift. To avoid causing stack drift, please use ct-38s4s4tm4ic4u instead, or ct-361tlo1k7339x if the EC2 instance was provisioned via CFN ingestion.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-UpdateInstanceEnhancedMonitoring.", "type": "string", "enum": [ "AWSManagedServices-UpdateInstanceEnhancedMonitoring" ], "default": "AWSManagedServices-UpdateInstanceEnhancedMonitoring" }, "Region": { "description": "The AWS Region in which the EC2 instance is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "InstanceIds": { "description": "A list of up to 50 EC2 instance IDs, in the form i-1234567890abcdef0 or i-b188560f.", "type": "array", "items": { "type": "string", "pattern": "^i-[a-f0-9]{8}$|^i-[a-f0-9]{17}$" }, "minItems": 1, "maxItems": 50, "uniqueItems": true }, "MonitoringValue": { "description": "Enabled to turn on detailed monitoring for your instances. Disabled to turn off detailed monitoring for your instances and set it to basic monitoring. EC2 detailed monitoring provides more frequent metrics, published at ct-0tmpmp1wpgkr9 Version April 22, 2025 2007 AMS Advanced Change Type Reference AMS Advanced Change Type Details one-minute intervals, instead of the five-minute intervals used in Amazon EC2 basic monitoring. Detailed monitoring does incur charges. For more information, see AWS CloudWatch documentation.", "type": "array", "items": { "type": "string", "enum": [ "enabled", "disabled" ] } } }, "metadata": { "ui:order": [ "InstanceIds", "MonitoringValue" ] }, "additionalProperties": false, "required": [ "InstanceIds", "MonitoringValue" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } ct-0tmpmp1wpgkr9 Version April 22, 2025 2008 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0tpbr6lfa3zng Classifications: • Management | Advanced stack components | Application Load Balancer | Remove listener certificate { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Remove ALB Listener Certificate", "description": "Remove a certificate from the specified Application Load Balancer (ALB) listener. Use the RemediateStackDrift parameter for the automation to try to remediate drift, if it is introduced.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-RemoveCertificateFromElbv2Listener.", "type": "string", "enum": [ "AWSManagedServices-RemoveCertificateFromElbv2Listener" ], "default": "AWSManagedServices-RemoveCertificateFromElbv2Listener" }, "Region": { "description": "The AWS Region where the application load balancer listener is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "ListenerArn": { "description": "The Amazon Resource Name (ARN) of the listener in the form arn:aws:elasticloadbalancing:us-east-1:123456789012:listener/app/ sample/1234567890abcdfe/1234567890abcdfe.", "type": "array", "items": { "type": "string", "pattern": "^arn:(aws|aws-cn|aws-us-gov):elasticloadbalancing:[a-z]{2}-[a- z]+-[0-9]{1}:[0-9]{12}:listener/[a-z]{3}/[A-Za-z0-9-]+/[a-z0-9-]+/[a-z0-9-]+$" }, ct-0tpbr6lfa3zng Version April 22, 2025 2009 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 1, "maxItems": 1 }, "CertificateArn": { "description": "The Amazon Resource Name (ARN) of the certificate in the form arn:aws:acm:us- east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012.", "type": "array", "items": { "type": "string", "pattern": "^arn:(aws|aws-cn|aws-us-gov):acm:[a-z]{2}-[a-z]+-[0-9]{1}:[0-9] {12}:certificate/[a-z0-9-]+$" }, "minItems": 1, "maxItems": 1 }, "RemediateStackDrift": { "description": "True to initiate drift remediation, if any drift is caused by removing the certificate from the Loadbalancer Listener. False to not attempt drift remediation. Drift remediation can be performed only on CloudFormation stacks that were created using a CT other than the Ingestion CT ct-36cn2avfrrj9v and that are in sync with the definitions in the stack template prior to removing the certificate from the Loadbalancer Listener. Set to False to remove the certificate from the Loadbalancer Listener in an ingested stack if any drift introduced by the change is acceptable.", "type": "array", "items": { "type": "string", "default": "True", "enum": [ "True", "False" ] }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "ListenerArn", "CertificateArn", "RemediateStackDrift" ] ct-0tpbr6lfa3zng Version April 22, 2025 2010 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "additionalProperties": false, "required": [ "CertificateArn", "ListenerArn" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0ttx8eh3ice91 Classifications: • Management | Advanced stack components | S3 storage | Delete policy (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Delete policy", "description": "Use to delete an S3 bucket policy.", "type": "object", "properties": { "BucketName": { "description": "S3 Bucket to delete the bucket policy from.", "type": "string", "pattern": "^[A-Za-z0-9][A-Za-z0-9\\-]{1,61}[A-Za-z0-9]$", "maxLength": 63 }, "Operation": { ct-0ttx8eh3ice91 Version April 22, 2025 2011 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Must be Delete policy.", "type": "string", "default": "Delete policy", "enum": [ "Delete policy" ] }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "BucketName", "Operation", "Priority" ] }, "required": [ "BucketName", "Operation" ] |
ams-ct-560 | ams-ct.pdf | 560 | "object", "properties": { "BucketName": { "description": "S3 Bucket to delete the bucket policy from.", "type": "string", "pattern": "^[A-Za-z0-9][A-Za-z0-9\\-]{1,61}[A-Za-z0-9]$", "maxLength": 63 }, "Operation": { ct-0ttx8eh3ice91 Version April 22, 2025 2011 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Must be Delete policy.", "type": "string", "default": "Delete policy", "enum": [ "Delete policy" ] }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "BucketName", "Operation", "Priority" ] }, "required": [ "BucketName", "Operation" ] } Schema for Change Type ct-0vdiy51oyrhhm Classifications: • Management | Managed landing zone | Management account | Offboard application account { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Offboard Application Account", ct-0vdiy51oyrhhm Version April 22, 2025 2012 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Offboard the specified application account. Run this from the management account for the application account that you want offboarded. You must first confirm the offboarding request by submitting the Confirm offboarding CT (ct-2wlfo2jxj2rkj) from the application account. If you are offboarding a customer- managed account, then ct-2wlfo2jxj2rkj is not needed. After you successfully submit both CTs, AMS can't undo the offboarding, repurpose the account, or help you to remediate issues in the account.", "type": "object", "properties": { "RequestType": { "description": "Must be OffboardingExecution.", "type": "string", "enum": [ "OffboardingExecution" ], "default": "OffboardingExecution" }, "Parameters": { "type": "object", "properties": { "AccountId": { "description": "The unique identifier (ID) of the application account to offboard.", "type": "string", "pattern": "^[0-9]{12}$" }, "AccountEmail": { "description": "The email associated with the application account to offboard.", "type": "string", "pattern": "^[a-zA-Z0-9_.+-]+@[a-zA-Z0-9-]+\\.[a-zA-Z0-9-.]+$" }, "Confirmation": { "description": "To offboard the provided application account, confirm the operation by specifying 'confirm' in the text input field.", "type": "string", "pattern": "confirm" }, "DeleteTransitGatewayAttachment": { "description": "Specify true to delete the attachment to the default Transit Gateway within core networking account. Set to false to retain the connectivity using Transit Gateway.", "type": "boolean" } ct-0vdiy51oyrhhm Version April 22, 2025 2013 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "additionalProperties": false, "metadata": { "ui:order": [ "AccountId", "AccountEmail", "Confirmation", "DeleteTransitGatewayAttachment" ] }, "required": [ "AccountId", "AccountEmail", "Confirmation", "DeleteTransitGatewayAttachment" ] } }, "metadata": { "ui:order": [ "Parameters", "RequestType" ] }, "additionalProperties": false, "required": [ "Parameters", "RequestType" ] } Schema for Change Type ct-0vevjppj9eta4 Classifications: • Management | Advanced stack components | EBS Volume | Encrypt EBS by default { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Encrypt EBS By Default", "description": "Set Amazon Elastic Block Store (EBS) to enforce the encryption. After you enable encryption by default, the EBS volumes that you create and snapshot ct-0vevjppj9eta4 Version April 22, 2025 2014 AMS Advanced Change Type Reference AMS Advanced Change Type Details copies are always encrypted, either using the KMS key configured as default for EBS encryption or the key that you specified when you created each volume.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-EncryptEBSByDefault.", "type": "string", "enum": [ "AWSManagedServices-EncryptEBSByDefault" ], "default": "AWSManagedServices-EncryptEBSByDefault" }, "Region": { "description": "The AWS Region to enable EBS encryption by default in, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" } }, "metadata": { "ui:order": [ "DocumentName", "Region" ] }, "required": [ "DocumentName", "Region" ], "additionalProperties": false } Schema for Change Type ct-0vzsr2nyraedl Classifications: • Deployment | Advanced stack components | DNS (public) | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Public DNS Record", ct-0vzsr2nyraedl Version April 22, 2025 2015 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "Create a new Route 53 DNS resource record set and a new public hosted zone for a VPC, and configure traffic routing.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-CreateAddRoute53Resources.", "type": "string", "enum": [ "AWSManagedServices-CreateAddRoute53Resources" ], "default": "AWSManagedServices-CreateAddRoute53Resources" }, "Region": { "description": "The AWS Region in which the AWS resource is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "DomainName": { "description": "A domain name for the hosted zone. The name can contain only lowercase letters, numbers, hyphens (-), and a dot (.). For example, mycorp.com", "type": "string", "minLength": 2, "pattern": "^([a-z0-9]+(-[a-z0-9]+)*\\.)+[a-z]{2,255}$" }, "DomainType": { "description": "Must be 'public'", "type": "string", "enum": [ "public" ], "default": "public" }, "RecordSet": { "description": "A JSON of resource records for the hosted zone.", "type": "array", "items": { "type": "string", "pattern": "^\\s*\\{\\s*\"RecordSet\"\\s*:\\s*\\[.*\\]\\s*\\}\\s*$" }, ct-0vzsr2nyraedl Version April 22, 2025 2016 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 1, "maxItems": 1 } }, "additionalProperties": false, "metadata": { "ui:order": [ "DomainName", "DomainType", "RecordSet" ] }, "required": [ "DomainName", "DomainType", "RecordSet" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0wglhholzo0uw Classifications: • Management | Advanced stack components | Network Load |
ams-ct-561 | ams-ct.pdf | 561 | "public" ], "default": "public" }, "RecordSet": { "description": "A JSON of resource records for the hosted zone.", "type": "array", "items": { "type": "string", "pattern": "^\\s*\\{\\s*\"RecordSet\"\\s*:\\s*\\[.*\\]\\s*\\}\\s*$" }, ct-0vzsr2nyraedl Version April 22, 2025 2016 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 1, "maxItems": 1 } }, "additionalProperties": false, "metadata": { "ui:order": [ "DomainName", "DomainType", "RecordSet" ] }, "required": [ "DomainName", "DomainType", "RecordSet" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-0wglhholzo0uw Classifications: • Management | Advanced stack components | Network Load Balancer | Update { "$schema": "http://json-schema.org/draft-04/schema#", ct-0wglhholzo0uw Version April 22, 2025 2017 AMS Advanced Change Type Reference AMS Advanced Change Type Details "name": "Update Network Load Balancer", "description": "Update the properties of an existing Network Load Balancer.", "type": "object", "properties": { "VpcId": { "description": "The ID of the VPC where the Network Load Balancer is, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "StackId": { "description": "The stack ID of the Network Load Balancer that you are updating, in the form stack-a1b2c3d4e5f67890e.", "type": "string", "pattern": "^stack-[a-z0-9]{17}$" }, "Parameters": { "type": "object", "properties": { "HealthCheckHealthyThreshold": { "type": "string", "description": "The number of consecutive health check successes required to declare an EC2 instance healthy.", "pattern": "[2-9]{1}|10" }, "HealthCheckIntervalSeconds": { "type": "string", "description": "The approximate interval, in seconds, between health checks.", "enum": [ "10", "30" ] }, "HealthCheckTargetPath": { "type": "string", "description": "The ping path destination on the application hosts where the load balancer sends health check requests. This is only applicable if HealthCheckTargetProtocol = HTTP or HTTPS." }, "HealthCheckTargetPort": { "type": "string", ct-0wglhholzo0uw Version April 22, 2025 2018 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The port the load balancer uses when performing health checks on targets. The default is traffic-port, which indicates the port on which each target receives traffic from the load balancer.", "pattern": "([0-9]{1,5})?" }, "HealthCheckTargetProtocol": { "type": "string", "description": "The protocol the load balancer uses when performing health checks on targets.", "enum": [ "HTTP", "HTTPS", "TCP" ] }, "CrossZoneEnabled": { "type": "string", "description": "True if cross-zone load balancing is enabled. False if it is not.", "enum": [ "true", "false" ] }, "SubnetIds": { "type": "array", "description": "One or more subnet IDs for the load balancer, in the form subnet-0123abcd or subnet-01234567890abcdef. Please note that if you update SubnetIds, the new value must contain all of the required SubnetIds for the NLB, the new ones and the ones used before.", "items": { "type": "string" } }, "ProxyProtocolV2": { "type": "string", "description": "True if proxy protocol version 2 is enabled. False if it is not.", "enum": [ "true", "false" ] }, "DeregistrationDelayTimeoutSeconds": { ct-0wglhholzo0uw Version April 22, 2025 2019 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The amount of time, in seconds, for Elastic Load Balancing to wait before changing the state of a deregistering target from draining to unused.", "pattern": "(3600|3[0-5]{1}[0-9]{2}|[1-2]{1}[0-9]{3}|[0-9]{1,3})" }, "Target1ID": { "type": "string", "description": "The ID of the EC2 instance to register a target if the TargetType = instance, in the form i-0123abcd or i-01234567890abcdef. Leave blank if you don't need to register a target." }, "Target1Port": { "type": "string", "description": "The port number on which the target is listening for traffic." }, "Target1AvailabilityZone": { "type": "string", "description": "Where the target receives traffic from. Use an Availability Zone name if the target receives traffic from the load balancer nodes in the specified Availability Zone. Use all if the traffic is received from all enabled Availability Zones for the load balancer and the TargetType = ip and the IP address in Target1ID is outside the VPC. Leave blank if TargetType = instance." }, "Target2ID": { "type": "string", "description": "The ID of the EC2 instance to register a target if the TargetType = instance, in the form i-0123abcd or i-01234567890abcdef. Leave blank if you don't need to register a target." }, "Target2Port": { "type": "string", "description": "The port number on which the target is listening for traffic." }, "Target2AvailabilityZone": { "type": "string", "description": "Where the target receives traffic from. Use an Availability Zone name if the target receives traffic from the load balancer nodes in the specified Availability Zone. Use all if the traffic is received from all enabled Availability Zones for the load balancer and the TargetType = ip and the IP address in Target2ID is outside the VPC. Leave blank if TargetType = instance." }, "Target3ID": { ct-0wglhholzo0uw Version April 22, 2025 2020 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The ID of the EC2 instance to register a target if the TargetType = instance, in the form i-0123abcd or i-01234567890abcdef. Leave blank if you don't need to register a target." }, "Target3Port": { "type": "string", "description": |
ams-ct-562 | ams-ct.pdf | 562 | the specified Availability Zone. Use all if the traffic is received from all enabled Availability Zones for the load balancer and the TargetType = ip and the IP address in Target2ID is outside the VPC. Leave blank if TargetType = instance." }, "Target3ID": { ct-0wglhholzo0uw Version April 22, 2025 2020 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "string", "description": "The ID of the EC2 instance to register a target if the TargetType = instance, in the form i-0123abcd or i-01234567890abcdef. Leave blank if you don't need to register a target." }, "Target3Port": { "type": "string", "description": "The port number on which the target is listening for traffic." }, "Target3AvailabilityZone": { "type": "string", "description": "Where the target receives traffic from. Use an Availability Zone name if the target receives traffic from the load balancer nodes in the specified Availability Zone. Use all if the traffic is received from all enabled Availability Zones for the load balancer and the TargetType = ip and the IP address in Target3ID is outside the VPC. Leave blank if TargetType = instance." }, "Target4ID": { "type": "string", "description": "The ID of the EC2 instance to register a target if the TargetType = instance, in the form i-0123abcd or i-01234567890abcdef. Leave blank if you don't need to register a target." }, "Target4Port": { "type": "string", "description": "The port number on which the target is listening for traffic." }, "Target4AvailabilityZone": { "type": "string", "description": "Where the target receives traffic from. Use an Availability Zone name if the target receives traffic from the load balancer nodes in the specified Availability Zone. Use all if the traffic is received from all enabled Availability Zones for the load balancer and the TargetType = ip and the IP address in Target4ID is outside the VPC. Leave blank if TargetType = instance." } }, "metadata": { "ui:order": [ "ProxyProtocolV2", "DeregistrationDelayTimeoutSeconds", "CrossZoneEnabled", "SubnetIds", ct-0wglhholzo0uw Version April 22, 2025 2021 AMS Advanced Change Type Reference AMS Advanced Change Type Details "HealthCheckTargetPath", "HealthCheckTargetPort", "HealthCheckTargetProtocol", "HealthCheckHealthyThreshold", "HealthCheckIntervalSeconds", "Target1ID", "Target1Port", "Target1AvailabilityZone", "Target2ID", "Target2Port", "Target2AvailabilityZone", "Target3ID", "Target3Port", "Target3AvailabilityZone", "Target4ID", "Target4Port", "Target4AvailabilityZone" ] }, "additionalProperties": false } }, "metadata": { "ui:order": [ "VpcId", "StackId", "Parameters" ] }, "required": [ "VpcId", "StackId", "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0wspy4o646g9p Classifications: • Management | Host security | Trend Micro DSM | Add login (read-only) ct-0wspy4o646g9p Version April 22, 2025 2022 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Add DSM Read-Only Login", "description": "Request a read-only login to the Trend Micro console for your account. For multi-account landing zone (MALZ), use this change type in the shared services account.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-CreateEPSDSMReadOnlyUser.", "type": "string", "enum": [ "AWSManagedServices-CreateEPSDSMReadOnlyUser" ], "default": "AWSManagedServices-CreateEPSDSMReadOnlyUser" }, "Region": { "description": "The AWS Region to use, in the form us-east-1.", "type": "string", "pattern": "[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}|^$" }, "Parameters": { "type": "object", "properties": { "Username": { "description": "The username for the EPS user. The name can be up to 50 characters in length.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9._\\-:/()#,@\\[\\]+=&;{}!$\\*]{1,50}$" }, "minItems": 1, "maxItems": 1 }, "FullName": { "description": "The full name for the EPS user. The name can be up to 50 characters in length.", "type": "array", "items": { "type": "string", "pattern": "^$|^[ a-zA-Z0-9._\\-:/()#,@\\[\\]+=&;{}!$\\*]{1,50}$" }, ct-0wspy4o646g9p Version April 22, 2025 2023 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minItems": 0, "maxItems": 1 }, "Description": { "description": "The description for the EPS user. The description can be up to 150 characters in length.", "type": "array", "items": { "type": "string", "pattern": "^$|^[ a-zA-Z0-9._\\-:/()#,@\\[\\]+=&;{}!$\\*]{1,150}$" }, "minItems": 0, "maxItems": 1 } }, "metadata": { "ui:order": [ "Username", "FullName", "Description" ] }, "additionalProperties": false, "required": [ "Username" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } ct-0wspy4o646g9p Version April 22, 2025 2024 AMS Advanced Change Type Reference AMS Advanced Change Type Details Schema for Change Type ct-0x6dylrnfjgz5 Classifications: • Management | Directory Service | Directory | Create AD trust { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Active Directory Trust", "description": "Create a one-way trust between On-Prem Domain and (AWS) Managed Active Directory. For multi-account landing zone (MALZ), use this change type in the shared services account. Before creating the trust, you need to make sure that the following prerequisites are met: 1. You must create the AD trust first on the On- Prem Domain and save the trust password in the Secrets Manager. 2. You must set up a Managed Active Directory (MAD) Security Group with an outbound rule that allows all traffic to On-Prem CIDR ranges.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-CreateADTrust.", "type": "string", "enum": [ "AWSManagedServices-CreateADTrust" ], "default": "AWSManagedServices-CreateADTrust" }, "Region": { "description": "The AWS Region of the account.", "type": "string", "enum": [ "us-east-1", "us-east-2", "us-west-1", |
ams-ct-563 | ams-ct.pdf | 563 | the shared services account. Before creating the trust, you need to make sure that the following prerequisites are met: 1. You must create the AD trust first on the On- Prem Domain and save the trust password in the Secrets Manager. 2. You must set up a Managed Active Directory (MAD) Security Group with an outbound rule that allows all traffic to On-Prem CIDR ranges.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-CreateADTrust.", "type": "string", "enum": [ "AWSManagedServices-CreateADTrust" ], "default": "AWSManagedServices-CreateADTrust" }, "Region": { "description": "The AWS Region of the account.", "type": "string", "enum": [ "us-east-1", "us-east-2", "us-west-1", "us-west-2", "eu-west-1", "eu-west-2", "eu-west-3", "eu-south-1", "eu-north-1", "eu-central-1", "ca-central-1", "ap-southeast-1", ct-0x6dylrnfjgz5 Version April 22, 2025 2025 AMS Advanced Change Type Reference AMS Advanced Change Type Details "ap-southeast-2", "ap-southeast-3", "ap-south-1", "ap-northeast-1", "ap-northeast-2", "ap-northeast-3", "ap-east-1", "sa-east-1", "me-south-1", "af-south-1", "us-gov-west-1", "us-gov-east-1", "cn-northwest-1", "cn-north-1" ] }, "Parameters": { "type": "object", "properties": { "DirectoryId": { "description": "The Directory ID of the Managed Microsoft AD directory for which to establish the trust relationship.", "type": "string", "pattern": "^d-[0-9a-f]{10}$" }, "RemoteDomainName": { "description": "The Fully Qualified Domain Name (FQDN) of the external domain for which to create the trust relationship.", "type": "string", "pattern": "^([a-zA-Z0-9]+[\\.-])+([a-zA-Z0-9])+[.]?$" }, "SecretArn": { "description": "ARN of the secret where the AD trust password is stored. The secret must be stored as a string value not as a key/value pair. The secret name must be prefixed with customer-shared/; for example, customer-shared/trustpassword.", "type": "string", "pattern": "arn:(aws|aws-cn|aws-us-gov):secretsmanager:[a-z]{2}-[a-z]+-[0-9] {1}:\\d{12}:secret:([cC][uU][sS][tT][oO][mM][eE][rR]-[sS][hH][aA][rR][eE][dD])[\\w/_ +=.@-]{1,512}" }, "TrustType": { "description": "The trust relationship type.", "type": "string", "enum": [ ct-0x6dylrnfjgz5 Version April 22, 2025 2026 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Forest", "External" ] }, "ConditionalForwarderIpAddresses": { "description": "A comma-delimited list of one or more IP addresses of the remote DNS server associated with RemoteDomainName.", "type": "string", "pattern": "^(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])\\.){3}([0-9]| [1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])(,(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]| 25[0-5])\\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5]))*$" } }, "metadata": { "ui:order": [ "DirectoryId", "RemoteDomainName", "SecretArn", "TrustType", "ConditionalForwarderIpAddresses" ] }, "additionalProperties": false, "required": [ "DirectoryId", "RemoteDomainName", "SecretArn", "TrustType", "ConditionalForwarderIpAddresses" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ct-0x6dylrnfjgz5 Version April 22, 2025 2027 AMS Advanced Change Type Reference AMS Advanced Change Type Details ] } Schema for Change Type ct-0xdawir96cy7k Classifications: • Management | Other | Other | Update (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update other", "description": "Use to request a manual update to a resource.", "type": "object", "properties": { "Comment": { "description": "The description of the change.", "type": "string", "maxLength": 5000 }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] }, "RelatedIds": { "description": "(Optional) IDs of resources related to the change request.", "type": "array", "items": { "type": "string" }, "minItems": 1, "maxItems": 1000, "uniqueItems": true } }, "additionalProperties": false, ct-0xdawir96cy7k Version April 22, 2025 2028 AMS Advanced Change Type Reference AMS Advanced Change Type Details "required": [ "Comment" ], "metadata": { "ui:order": [ "Comment", "RelatedIds", "Priority" ] } } Schema for Change Type ct-0xi6q7uwuwrqe Classifications: • Deployment | Advanced stack components | Cache (ElastiCache Memcached) stack | Create { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create Cache (ElastiCache Memcached) stack", "description": "Use to create an Amazon ElastiCache cluster (one or more cache nodes) that uses the Memcached engine, and specify CloudWatch metrics and alarms for the cluster.", "type": "object", "properties": { "Description": { "description": "Meaningful information about the resource to be created.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the vpc to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$|^vpc-[a-z0-9]{17}$" }, "StackTemplateId": { "description": "Must be stm-sfpo2o00000000000.", "type": "string", "enum": [ ct-0xi6q7uwuwrqe Version April 22, 2025 2029 AMS Advanced Change Type Reference AMS Advanced Change Type Details "stm-sfpo2o00000000000" ] }, "Name": { "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to seven tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,127}$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_./=+-]{1,255}$", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 7, "uniqueItems": true }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", ct-0xi6q7uwuwrqe Version April 22, 2025 2030 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minimum": 0, "maximum": 60 }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "ElastiCacheAutoMinorVersionUpgrade": { "description": "True for minor engine upgrades to be applied automatically to the cache cluster during the specified ElastiCachePreferredMaintenanceWindow, false for the upgrades to not be applied |
ams-ct-564 | ams-ct.pdf | 564 | true }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time.", "type": "number", ct-0xi6q7uwuwrqe Version April 22, 2025 2030 AMS Advanced Change Type Reference AMS Advanced Change Type Details "minimum": 0, "maximum": 60 }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "ElastiCacheAutoMinorVersionUpgrade": { "description": "True for minor engine upgrades to be applied automatically to the cache cluster during the specified ElastiCachePreferredMaintenanceWindow, false for the upgrades to not be applied automatically. Default is true.", "type": "boolean", "default": true }, "ElastiCacheAvailabilityZones": { "description": "One or more Availability Zones where cache nodes will be created.", "type": "array", "items": { "type": "string" }, "minItems": 1 }, "ElastiCacheClusterName": { "description": "A name for the cache cluster.", "type": "string", "minLength": 1, "maxLength": 20, "pattern": "^[a-zA-Z][a-zA-Z0-9-]{0,18}[a-zA-Z0-9]$|^[a-zA-Z]$" }, "ElastiCacheCPUThresholdAlarmOverride": { "description": "The optional value for the CPUUtilization metric maximum threshold to use instead of the default value for the instance type.", "type": "number", "default": 0, "minimum": 0, "maximum": 100 }, "ElastiCacheEngine": { "description": "Must be memcached.", "type": "string", "enum": [ "memcached" ] ct-0xi6q7uwuwrqe Version April 22, 2025 2031 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "ElastiCacheEngineVersion": { "description": "The version of the Memcached engine to be used for this cluster.", "type": "string" }, "ElastiCacheInstanceType": { "description": "The compute and memory capacity of nodes in the cache cluster.", "type": "string", "default": "cache.t3.micro" }, "ElastiCacheMultiAZ": { "description": "True for the nodes to be created in a single Availability Zone, false for them to be created across multiple Availability Zones in the cluster's region. Default is false.", "type": "boolean", "default": false }, "ElastiCacheNumberOfNodes": { "description": "The number of cache nodes that the Memcached cluster should have.", "type": "number", "default": 1, "minimum": 1, "maximum": 20 }, "ElastiCachePort": { "description": "The port number on which each of the cache nodes will accept connections.", "type": "number", "minimum": 0, "maximum": 65535, "default": 11211 }, "ElastiCachePreferredMaintenanceWindow": { "description": "The weekly time range (in UTC) during which system maintenance can occur. For example, you can specify: sun:02:00-sun:04:00.", "type": "string", "pattern": "^(?:sun|mon|tue|wed|thu|fri|sat):(?:[0-1][0-9]|2[0-3]):[0-5] [0-9]-(?:sun|mon|tue|wed|thu|fri|sat):(?:[0-1][0-9]|2[0-3]):[0-5][0-9]$" }, "ElastiCacheSubnetGroup": { ct-0xi6q7uwuwrqe Version April 22, 2025 2032 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The name of the subnet group to associate with the cluster.", "type": "string", "minLength": 1, "maxLength": 255, "pattern": "^[a-z0-9-]{1,255}$" }, "ElastiCacheSubnetIds": { "description": "One or more subnet IDs for the cache cluster, in the form subnet-0123abcd or subnet-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^subnet-[a-z0-9]{8}$|^subnet-[a-z0-9]{17}$" }, "minItems": 1 }, "SecurityGroups": { "description": "One or more VPC security groups to associate with the cluster, in the form sg-0123abcd or sg-01234567890abcdef.", "type": "array", "items": { "type": "string", "pattern": "^sg-[a-z0-9]{8}$|^sg-[a-z0-9]{17}$" }, "minItems": 1 } }, "additionalProperties": false, "required": [ "ElastiCacheAvailabilityZones", "ElastiCacheClusterName", "ElastiCacheEngine", "ElastiCacheSubnetIds" ] } }, "additionalProperties": false, "required": [ "Description", "VpcId", "StackTemplateId", "Name", "Parameters", ct-0xi6q7uwuwrqe Version April 22, 2025 2033 AMS Advanced Change Type Reference "TimeoutInMinutes" ] } AMS Advanced Change Type Details Schema for Change Type ct-0xqwmtn1hfh8u Classifications: • Management | Advanced stack components | Tag | Update { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Resource Tags", "description": "Update tags on existing, tagged resources: Autoscaling, EC2, Elastic Load Balancing, RDS, S3 buckets and Redshift clusters. Additionally, CloudWatch LogGroups that do not belong to a CloudFormation stack are supported. AMS infrastructure stacks (stacks named mc-*) cannot have tags updated with this change type.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-UpdateTags.", "type": "string", "enum": [ "AWSManagedServices-UpdateTags" ], "default": "AWSManagedServices-UpdateTags" }, "Region": { "description": "The AWS Region where the tagged resources are, in the form us- east-1.", "type": "string", "pattern": "^[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}$" }, "Parameters": { "type": "object", "properties": { "ResourceArns": { "description": "A list of up to 50 Amazon resource names (ARNs), or the resource IDs, of the resources with tags to be updated. Use resource ID only for these resource types: EC2 instance, EBS volume, EBS snapshot, AMI, and security group. Use the full ARN for all other supported resource types.", ct-0xqwmtn1hfh8u Version April 22, 2025 2034 AMS Advanced Change Type Reference AMS Advanced Change Type Details "type": "array", "items": { "type": "string", "pattern": "^(arn:aws:(autoscaling|ec2|elasticloadbalancing|logs|rds|s3| redshift):(|[a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\\d{1}):(|[0-9]{12}):.*)$|^(ami|i|vol| sg|snap)-([a-f0-9]{8}|[a-f0-9]{17})$" }, "minItems": 1, "maxItems": 50, "uniqueItems": true }, "AddOrUpdateTags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource, in the form {\"Key\":\"TagKey1\",\"Value\":\"TagValue1\"}. If the tag exists, the value for it is overwritten. If the tag does not exist, it is added to the resource. Characters allowed in tags can vary by AWS service. For information about what characters can be used to tag resources in a particular AWS service, please refer to its documentation. In general, allowed characters in tags are letters, numbers, spaces and the following characters: _ . : / = + - @.", "type": "array", "items": { "type": "string", |
ams-ct-565 | ams-ct.pdf | 565 | "uniqueItems": true }, "AddOrUpdateTags": { "description": "Up to fifty tags (key/value pairs) to categorize the resource, in the form {\"Key\":\"TagKey1\",\"Value\":\"TagValue1\"}. If the tag exists, the value for it is overwritten. If the tag does not exist, it is added to the resource. Characters allowed in tags can vary by AWS service. For information about what characters can be used to tag resources in a particular AWS service, please refer to its documentation. In general, allowed characters in tags are letters, numbers, spaces and the following characters: _ . : / = + - @.", "type": "array", "items": { "type": "string", "pattern": "^\\{\\}$|^\\{\"Key\":\"((aws-migration-project-id)|(?![aA] [mMwW][sS])[\\x00-\\x7F+]{1,128})\",\"Value\":\"[\\x00-\\x7F+]{0,255}\"\\}" }, "minItems": 1, "maxItems": 50, "uniqueItems": true }, "RemoveTags": { "description": "Up to fifty tag Keys to remove from the specified resource.", "type": "array", "items": { "type": "string", "pattern": "^((aws-migration-project-id)|(?![aA][mMwW][sS])[\\x00-\\x7F+] {1,128})$", "minLength": 1, "maxLength": 127 }, "minItems": 1, "maxItems": 50, "uniqueItems": true } ct-0xqwmtn1hfh8u Version April 22, 2025 2035 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "metadata": { "ui:order": [ "ResourceArns", "AddOrUpdateTags", "RemoveTags" ] }, "required": [ "ResourceArns" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "Region", "Parameters", "DocumentName" ] }, "additionalProperties": false, "required": [ "Region", "DocumentName", "Parameters" ] } Schema for Change Type ct-0ywnhc8e5k9z5 Classifications: • Deployment | AMS Resource Scheduler | Solution | Deploy { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Deploy AMS Resource Scheduler", "description": "Deploy the AMS Resource Scheduler solution in the account. The AMS Resource Scheduler lets you schedule automatic start and/or stop for Auto Scaling groups, EC2s, and RDS instances. Note that the Resource Scheduler deploys in an ct-0ywnhc8e5k9z5 Version April 22, 2025 2036 AMS Advanced Change Type Reference AMS Advanced Change Type Details enabled state, by default; you can manage that with the AMS Resource Scheduler Disable and Enable change types.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-HandleAMSResourceSchedulerStack- Admin.", "type": "string", "enum": [ "AWSManagedServices-HandleAMSResourceSchedulerStack-Admin" ], "default": "AWSManagedServices-HandleAMSResourceSchedulerStack-Admin" }, "Region": { "description": "The AWS Region of the account for the AMS Resource Scheduler solution to be deployed, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "SchedulingActive": { "description": "Yes to enable the Resource Scheduler. No to disable it. The default is Yes. Use Resource Scheduler enable (ct-2wrvu4kca9xky) and disable (ct-14v49adibs4db) change types to manage state.", "type": "array", "items": { "type": "string", "enum": [ "Yes", "No" ] }, "minItems": 1, "maxItems": 1 }, "ScheduledServices": { "description": "Comma-separated list of scheduled services. Use a combination of AutoScaling, EC2, and RDS.", "type": "array", "items": { "type": "string", "pattern": "^$|(^(ec2|rds|autoscaling)(,(ec2|rds|autoscaling)){0,2}$)" ct-0ywnhc8e5k9z5 Version April 22, 2025 2037 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "minItems": 1, "maxItems": 1 }, "TagName": { "description": "The name of the tag key to use to associate the instance schedule schemas with service resources. Default is Schedule.", "type": "array", "items": { "type": "string", "pattern": "^$|^(?!(aws:|ams:))[a-zA-Z0-9+-=._:/@]{1,127}$" }, "minItems": 1, "maxItems": 1 }, "UseCMK": { "description": "Comma-separated list of Customer Managed Key (CMK) Amazon Resource Names (ARNs) in format arn:<partition>:kms:<region>:<account-id>:key/<key-id> to grant Resource Scheduler permission to. These are CMK that are used to encrypt EBS volumes on EC2 instances.", "type": "array", "items": { "type": "string", "pattern": "^(|arn:(aws|aws-cn|aws-us-gov):kms:([a-z]{2}((-gov))?-[a-z]+-\ \d{1}):[0-9]{0,12}:key/[a-z0-9\\-]+)$" }, "minItems": 1, "maxItems": 20 }, "UseLicenseManager": { "description": "Comma-separated list of AWS License Manager license ARNs to grant Resource Scheduler permission to. These are software or vendor licenses that EC2 instances are configured with.", "type": "array", "items": { "type": "string", "pattern": "^(|arn:(aws|aws-cn|aws-us-gov):license-manager:([a-z]{2}((- gov))?-[a-z]+-\\d{1}):[0-9]{0,12}:license-configuration(/|:)lic-.*)$" }, "minItems": 1, "maxItems": 20 }, "DefaultTimezone": { ct-0ywnhc8e5k9z5 Version April 22, 2025 2038 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "The name of the timezone, in the form US/Pacific, to be used as the default timezone. The default is UTC.", "type": "array", "items": { "type": "string", "enum": [ "Africa/Abidjan", "Africa/Accra", "Africa/Addis_Ababa", "Africa/Algiers", "Africa/Asmara", "Africa/Bamako", "Africa/Bangui", "Africa/Banjul", "Africa/Bissau", "Africa/Blantyre", "Africa/Brazzaville", "Africa/Bujumbura", "Africa/Cairo", "Africa/Casablanca", "Africa/Ceuta", "Africa/Conakry", "Africa/Dakar", "Africa/Dar_es_Salaam", "Africa/Djibouti", "Africa/Douala", "Africa/El_Aaiun", "Africa/Freetown", "Africa/Gaborone", "Africa/Harare", "Africa/Johannesburg", "Africa/Juba", "Africa/Kampala", "Africa/Khartoum", "Africa/Kigali", "Africa/Kinshasa", "Africa/Lagos", "Africa/Libreville", "Africa/Lome", "Africa/Luanda", "Africa/Lubumbashi", "Africa/Lusaka", "Africa/Malabo", "Africa/Maputo", ct-0ywnhc8e5k9z5 Version April 22, 2025 2039 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Africa/Maseru", "Africa/Mbabane", "Africa/Mogadishu", "Africa/Monrovia", "Africa/Nairobi", "Africa/Ndjamena", "Africa/Niamey", "Africa/Nouakchott", "Africa/Ouagadougou", "Africa/Porto-Novo", "Africa/Sao_Tome", "Africa/Tripoli", "Africa/Tunis", "Africa/Windhoek", "America/Adak", "America/Anchorage", "America/Anguilla", "America/Antigua", "America/Araguaina", "America/Argentina/Buenos_Aires", "America/Argentina/Catamarca", "America/Argentina/Cordoba", "America/Argentina/Jujuy", "America/Argentina/La_Rioja", "America/Argentina/Mendoza", "America/Argentina/Rio_Gallegos", "America/Argentina/Salta", "America/Argentina/San_Juan", "America/Argentina/San_Luis", "America/Argentina/Tucuman", "America/Argentina/Ushuaia", "America/Aruba", "America/Asuncion", "America/Atikokan", "America/Bahia", "America/Bahia_Banderas", "America/Barbados", "America/Belem", "America/Belize", "America/Blanc-Sablon", "America/Boa_Vista", "America/Bogota", "America/Boise", "America/Cambridge_Bay", ct-0ywnhc8e5k9z5 Version April 22, 2025 2040 AMS Advanced Change Type Reference AMS Advanced Change Type Details "America/Campo_Grande", "America/Cancun", "America/Caracas", "America/Cayenne", "America/Cayman", "America/Chicago", "America/Chihuahua", "America/Costa_Rica", "America/Creston", "America/Cuiaba", "America/Curacao", "America/Danmarkshavn", "America/Dawson", "America/Dawson_Creek", "America/Denver", "America/Detroit", "America/Dominica", "America/Edmonton", "America/Eirunepe", "America/El_Salvador", "America/Fortaleza", "America/Glace_Bay", "America/Godthab", "America/Goose_Bay", "America/Grand_Turk", "America/Grenada", "America/Guadeloupe", "America/Guatemala", "America/Guayaquil", "America/Guyana", "America/Halifax", "America/Havana", "America/Hermosillo", "America/Indiana/Indianapolis", "America/Indiana/Knox", "America/Indiana/Marengo", "America/Indiana/Petersburg", "America/Indiana/Tell_City", "America/Indiana/Vevay", "America/Indiana/Vincennes", "America/Indiana/Winamac", "America/Inuvik", "America/Iqaluit", "America/Jamaica", ct-0ywnhc8e5k9z5 Version April 22, 2025 2041 AMS Advanced Change Type Reference AMS Advanced Change Type Details "America/Juneau", "America/Kentucky/Louisville", "America/Kentucky/Monticello", "America/Kralendijk", "America/La_Paz", "America/Lima", "America/Los_Angeles", "America/Lower_Princes", |
ams-ct-566 | ams-ct.pdf | 566 | "America/Argentina/San_Luis", "America/Argentina/Tucuman", "America/Argentina/Ushuaia", "America/Aruba", "America/Asuncion", "America/Atikokan", "America/Bahia", "America/Bahia_Banderas", "America/Barbados", "America/Belem", "America/Belize", "America/Blanc-Sablon", "America/Boa_Vista", "America/Bogota", "America/Boise", "America/Cambridge_Bay", ct-0ywnhc8e5k9z5 Version April 22, 2025 2040 AMS Advanced Change Type Reference AMS Advanced Change Type Details "America/Campo_Grande", "America/Cancun", "America/Caracas", "America/Cayenne", "America/Cayman", "America/Chicago", "America/Chihuahua", "America/Costa_Rica", "America/Creston", "America/Cuiaba", "America/Curacao", "America/Danmarkshavn", "America/Dawson", "America/Dawson_Creek", "America/Denver", "America/Detroit", "America/Dominica", "America/Edmonton", "America/Eirunepe", "America/El_Salvador", "America/Fortaleza", "America/Glace_Bay", "America/Godthab", "America/Goose_Bay", "America/Grand_Turk", "America/Grenada", "America/Guadeloupe", "America/Guatemala", "America/Guayaquil", "America/Guyana", "America/Halifax", "America/Havana", "America/Hermosillo", "America/Indiana/Indianapolis", "America/Indiana/Knox", "America/Indiana/Marengo", "America/Indiana/Petersburg", "America/Indiana/Tell_City", "America/Indiana/Vevay", "America/Indiana/Vincennes", "America/Indiana/Winamac", "America/Inuvik", "America/Iqaluit", "America/Jamaica", ct-0ywnhc8e5k9z5 Version April 22, 2025 2041 AMS Advanced Change Type Reference AMS Advanced Change Type Details "America/Juneau", "America/Kentucky/Louisville", "America/Kentucky/Monticello", "America/Kralendijk", "America/La_Paz", "America/Lima", "America/Los_Angeles", "America/Lower_Princes", "America/Maceio", "America/Managua", "America/Manaus", "America/Marigot", "America/Martinique", "America/Matamoros", "America/Mazatlan", "America/Menominee", "America/Merida", "America/Metlakatla", "America/Mexico_City", "America/Miquelon", "America/Moncton", "America/Monterrey", "America/Montevideo", "America/Montreal", "America/Montserrat", "America/Nassau", "America/New_York", "America/Nipigon", "America/Nome", "America/Noronha", "America/North_Dakota/Beulah", "America/North_Dakota/Center", "America/North_Dakota/New_Salem", "America/Ojinaga", "America/Panama", "America/Pangnirtung", "America/Paramaribo", "America/Phoenix", "America/Port-au-Prince", "America/Port_of_Spain", "America/Porto_Velho", "America/Puerto_Rico", "America/Rainy_River", "America/Rankin_Inlet", ct-0ywnhc8e5k9z5 Version April 22, 2025 2042 AMS Advanced Change Type Reference AMS Advanced Change Type Details "America/Recife", "America/Regina", "America/Resolute", "America/Rio_Branco", "America/Santa_Isabel", "America/Santarem", "America/Santiago", "America/Santo_Domingo", "America/Sao_Paulo", "America/Scoresbysund", "America/Sitka", "America/St_Barthelemy", "America/St_Johns", "America/St_Kitts", "America/St_Lucia", "America/St_Thomas", "America/St_Vincent", "America/Swift_Current", "America/Tegucigalpa", "America/Thule", "America/Thunder_Bay", "America/Tijuana", "America/Toronto", "America/Tortola", "America/Vancouver", "America/Whitehorse", "America/Winnipeg", "America/Yakutat", "America/Yellowknife", "Antarctica/Casey", "Antarctica/Davis", "Antarctica/DumontDUrville", "Antarctica/Macquarie", "Antarctica/Mawson", "Antarctica/McMurdo", "Antarctica/Palmer", "Antarctica/Rothera", "Antarctica/Syowa", "Antarctica/Vostok", "Arctic/Longyearbyen", "Asia/Aden", "Asia/Almaty", "Asia/Amman", "Asia/Anadyr", ct-0ywnhc8e5k9z5 Version April 22, 2025 2043 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Asia/Aqtau", "Asia/Aqtobe", "Asia/Ashgabat", "Asia/Baghdad", "Asia/Bahrain", "Asia/Baku", "Asia/Bangkok", "Asia/Beirut", "Asia/Bishkek", "Asia/Brunei", "Asia/Choibalsan", "Asia/Chongqing", "Asia/Colombo", "Asia/Damascus", "Asia/Dhaka", "Asia/Dili", "Asia/Dubai", "Asia/Dushanbe", "Asia/Gaza", "Asia/Harbin", "Asia/Hebron", "Asia/Ho_Chi_Minh", "Asia/Hong_Kong", "Asia/Hovd", "Asia/Irkutsk", "Asia/Jakarta", "Asia/Jayapura", "Asia/Jerusalem", "Asia/Kabul", "Asia/Kamchatka", "Asia/Karachi", "Asia/Kashgar", "Asia/Kathmandu", "Asia/Khandyga", "Asia/Kolkata", "Asia/Krasnoyarsk", "Asia/Kuala_Lumpur", "Asia/Kuching", "Asia/Kuwait", "Asia/Macau", "Asia/Magadan", "Asia/Makassar", "Asia/Manila", "Asia/Muscat", ct-0ywnhc8e5k9z5 Version April 22, 2025 2044 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Asia/Nicosia", "Asia/Novokuznetsk", "Asia/Novosibirsk", "Asia/Omsk", "Asia/Oral", "Asia/Phnom_Penh", "Asia/Pontianak", "Asia/Pyongyang", "Asia/Qatar", "Asia/Qyzylorda", "Asia/Rangoon", "Asia/Riyadh", "Asia/Sakhalin", "Asia/Samarkand", "Asia/Seoul", "Asia/Shanghai", "Asia/Singapore", "Asia/Taipei", "Asia/Tashkent", "Asia/Tbilisi", "Asia/Tehran", "Asia/Thimphu", "Asia/Tokyo", "Asia/Ulaanbaatar", "Asia/Urumqi", "Asia/Ust-Nera", "Asia/Vientiane", "Asia/Vladivostok", "Asia/Yakutsk", "Asia/Yekaterinburg", "Asia/Yerevan", "Atlantic/Azores", "Atlantic/Bermuda", "Atlantic/Canary", "Atlantic/Cape_Verde", "Atlantic/Faroe", "Atlantic/Madeira", "Atlantic/Reykjavik", "Atlantic/South_Georgia", "Atlantic/St_Helena", "Atlantic/Stanley", "Australia/Adelaide", "Australia/Brisbane", "Australia/Broken_Hill", ct-0ywnhc8e5k9z5 Version April 22, 2025 2045 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Australia/Currie", "Australia/Darwin", "Australia/Eucla", "Australia/Hobart", "Australia/Lindeman", "Australia/Lord_Howe", "Australia/Melbourne", "Australia/Perth", "Australia/Sydney", "Canada/Atlantic", "Canada/Central", "Canada/Eastern", "Canada/Mountain", "Canada/Newfoundland", "Canada/Pacific", "Europe/Amsterdam", "Europe/Andorra", "Europe/Athens", "Europe/Belgrade", "Europe/Berlin", "Europe/Bratislava", "Europe/Brussels", "Europe/Bucharest", "Europe/Budapest", "Europe/Busingen", "Europe/Chisinau", "Europe/Copenhagen", "Europe/Dublin", "Europe/Gibraltar", "Europe/Guernsey", "Europe/Helsinki", "Europe/Isle_of_Man", "Europe/Istanbul", "Europe/Jersey", "Europe/Kaliningrad", "Europe/Kiev", "Europe/Lisbon", "Europe/Ljubljana", "Europe/London", "Europe/Luxembourg", "Europe/Madrid", "Europe/Malta", "Europe/Mariehamn", "Europe/Minsk", ct-0ywnhc8e5k9z5 Version April 22, 2025 2046 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Europe/Monaco", "Europe/Moscow", "Europe/Oslo", "Europe/Paris", "Europe/Podgorica", "Europe/Prague", "Europe/Riga", "Europe/Rome", "Europe/Samara", "Europe/San_Marino", "Europe/Sarajevo", "Europe/Simferopol", "Europe/Skopje", "Europe/Sofia", "Europe/Stockholm", "Europe/Tallinn", "Europe/Tirane", "Europe/Uzhgorod", "Europe/Vaduz", "Europe/Vatican", "Europe/Vienna", "Europe/Vilnius", "Europe/Volgograd", "Europe/Warsaw", "Europe/Zagreb", "Europe/Zaporozhye", "Europe/Zurich", "GMT", "Indian/Antananarivo", "Indian/Chagos", "Indian/Christmas", "Indian/Cocos", "Indian/Comoro", "Indian/Kerguelen", "Indian/Mahe", "Indian/Maldives", "Indian/Mauritius", "Indian/Mayotte", "Indian/Reunion", "Pacific/Apia", "Pacific/Auckland", "Pacific/Chatham", "Pacific/Chuuk", "Pacific/Easter", ct-0ywnhc8e5k9z5 Version April 22, 2025 2047 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Pacific/Efate", "Pacific/Enderbury", "Pacific/Fakaofo", "Pacific/Fiji", "Pacific/Funafuti", "Pacific/Galapagos", "Pacific/Gambier", "Pacific/Guadalcanal", "Pacific/Guam", "Pacific/Honolulu", "Pacific/Johnston", "Pacific/Kiritimati", "Pacific/Kosrae", "Pacific/Kwajalein", "Pacific/Majuro", "Pacific/Marquesas", "Pacific/Midway", "Pacific/Nauru", "Pacific/Niue", "Pacific/Norfolk", "Pacific/Noumea", "Pacific/Pago_Pago", "Pacific/Palau", "Pacific/Pitcairn", "Pacific/Pohnpei", "Pacific/Port_Moresby", "Pacific/Rarotonga", "Pacific/Saipan", "Pacific/Tahiti", "Pacific/Tarawa", "Pacific/Tongatapu", "Pacific/Wake", "Pacific/Wallis", "US/Alaska", "US/Arizona", "US/Central", "US/Eastern", "US/Hawaii", "US/Mountain", "US/Pacific", "UTC" ] }, "minItems": 1, ct-0ywnhc8e5k9z5 Version April 22, 2025 2048 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maxItems": 1 }, "MemorySize": { "description": "The amount of Memory available to the Lambda function running the scheduler in MB. Increase the size when processing large numbers of instances. The allowed values are 128, 384, 512, 640, 768, 896, 1024, 1152, 1280, 1408 and 1536. Default is 512.", "type": "array", "items": { "type": "string", "enum": [ "128", "384", "512", "640", "768", "896", "1024", "1152", "1280", "1408", "1536" ], "default": "512" }, "minItems": 1, "maxItems": 1 }, "SchedulerFrequency": { "description": "Scheduler running frequency in minutes. The allowed values are 10, 15, 30 and 60. Default is 10.", "type": "array", "items": { "type": "string", "enum": [ "10", "15", "30", "60" ], "default": "10" }, "minItems": 1, "maxItems": 1 ct-0ywnhc8e5k9z5 Version April 22, 2025 2049 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "Action": { "description": "Must be Deploy.", "type": "array", "items": { "type": "string", "enum": [ "Deploy" ], "default": "Deploy" }, "minItems": 1, "maxItems": 1 } }, "metadata": { "ui:order": [ "SchedulingActive", "ScheduledServices", "TagName", "DefaultTimezone", "UseCMK", "UseLicenseManager", "MemorySize", "SchedulerFrequency", "Action" ] }, "required": [ "Action" ], "additionalProperties": false } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "required": [ "DocumentName", "Region", ct-0ywnhc8e5k9z5 Version April 22, 2025 2050 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0zko7t3rk2efb Classifications: • Management | Advanced stack components | Tag | Update (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Resource Tags (Review Required)", "description": "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 |
ams-ct-567 | ams-ct.pdf | 567 | "Parameters" ] }, "required": [ "DocumentName", "Region", ct-0ywnhc8e5k9z5 Version April 22, 2025 2050 AMS Advanced Change Type Reference AMS Advanced Change Type Details "Parameters" ], "additionalProperties": false } Schema for Change Type ct-0zko7t3rk2efb Classifications: • Management | Advanced stack components | Tag | Update (review required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update Resource Tags (Review Required)", "description": "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.", "type": "object", "properties": { "Resources": { "description": "Parameters for up to fifty resources for tag management.", "type": "array", "items": { "type": "object", "properties": { "ResourceArn": { "description": "The ARN or the resource ID of the resource to be tagged. Resource ID is allowed only for these resource types: EC2 instance, EBS volume, EBS snapshot, AMI, and security group. All other resource types must be provided with the full ARN.", "type": "string", "pattern": "^arn:aws:(|[a-z][a-z0-9-]+):(|[a-z]{2}((-gov)|(-iso(b?)))?-[a- z]+-\\d{1}):(|[0-9]{12}):([^,\\s]+)$|^(ami|i|vol|sg|snap)-([a-f0-9]{8}|[a-f0-9]{17})$" }, "AddOrUpdateTags": { "description": "Up to fifty tags (key/value pairs) to add to, or update for, the specified resources. If the tag exists, the value for it is overwritten. If the tag does not exist, it is added to the resource. Characters allowed in tags can vary by AWS service. For information about what characters can be used to tag resources in a particular AWS service, please refer to its documentation. In general, ct-0zko7t3rk2efb Version April 22, 2025 2051 AMS Advanced Change Type Reference AMS Advanced Change Type Details allowed characters in tags are letters, numbers, spaces and the following characters: _ . : / = + - @.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "pattern": "^(?![aA][mMwW][sS]:)[a-zA-Z0-9\\s_.:/=+\\\\\\-@\\]*]+$", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "pattern": "^[a-zA-Z0-9\\s_.:/=+\\\\\\-@\\]*]+$", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "metadata": { "ui:order": [ "Key", "Value" ] }, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 50, "uniqueItems": true }, "RemoveTags": { "description": "Up to fifty tag Keys to remove from the specified resource.", "type": "array", "items": { "type": "string", "pattern": "^(?![aA][mMwW][sS]:)[a-zA-Z0-9\\s_.:/=+\\\\\\-@\\]*]+$", "minLength": 1, "maxLength": 127 ct-0zko7t3rk2efb Version April 22, 2025 2052 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "minItems": 1, "maxItems": 50, "uniqueItems": true } }, "additionalProperties": false, "metadata": { "ui:order": [ "ResourceArn", "AddOrUpdateTags", "RemoveTags" ] }, "required": [ "ResourceArn" ] }, "minItems": 1, "maxItems": 50, "uniqueItems": true }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "additionalProperties": false, "metadata": { "ui:order": [ "Resources", "Priority" ] }, "required": [ "Resources" ] ct-0zko7t3rk2efb Version April 22, 2025 2053 AMS Advanced Change Type Reference AMS Advanced Change Type Details } Schema for Change Type ct-0zzf0fjz76jmb Classifications: • Management | Monitoring and notification | SNS | Update (Review Required) { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Update SNS Topic", "description": "Modify the properties of an existing Amazon Simple Notification Service (SNS) topic.", "type": "object", "properties": { "TopicArn": { "description": "The ARN of the existing SNS topic.", "type": "string", "pattern": "^(arn:(aws|aws-us-gov):sns:[a-z0-9-]+:[0-9]{12}:[a-zA-Z0-9-_]{0,256}) (.fifo)?$" }, "Parameters": { "type": "object", "properties": { "DisplayName": { "type": "string", "description": "A display name for the SNS topic for use with short message service (SMS) messages. The name maximum is 100 characters, including hyphens (-), underscores (_), spaces, and tabs.", "pattern": "^[a-zA-Z-_ \t]{0,100}|^$", "default": "" }, "Policy": { "type": "string", "description": "The policy that defines who can access your topic. By default, only the topic owner can publish or subscribe to the topic. This policy replaces the existing access policy. The policy must be in JSON string format.", "maxLength": 20000, "default": "" }, "ArchivePolicy": { "type": "string", ct-0zzf0fjz76jmb Version April 22, 2025 2054 AMS Advanced Change Type Reference AMS Advanced Change Type Details "description": "FIFO topics only. The policy that determines the number of days Amazon SNS retains messages in FIFO topics. You can set a retention period ranging from 1 to 365 days. Provide the value in the form of { \"MessageRetentionPeriod\" : \"20\" }.", "maxLength": 20000 }, "DeliveryPolicy": { "type": "string", "description": "The policy that defines how Amazon SNS retries failed deliveries to HTTP/S endpoints.", "maxLength": 20000 }, "ContentBasedDeduplication": { "type": "boolean", "description": "FIFO topics only. False (default) to enable the deduplication (removal of redundant) of messages based on their content for FIFO topics only. When set to false, you must provide a MessageDeduplicationId for each Publish action. When set to true, Amazon SNS automatically generates a MessageDeduplicationId using a SHA-256 hash of the message body (excluding message attributes). You can optionally override this generated value by specifying a MessageDeduplicationId in the Publish action." }, "DataProtectionPolicy": { "type": |
ams-ct-568 | ams-ct.pdf | 568 | { "type": "string", "description": "The policy that defines how Amazon SNS retries failed deliveries to HTTP/S endpoints.", "maxLength": 20000 }, "ContentBasedDeduplication": { "type": "boolean", "description": "FIFO topics only. False (default) to enable the deduplication (removal of redundant) of messages based on their content for FIFO topics only. When set to false, you must provide a MessageDeduplicationId for each Publish action. When set to true, Amazon SNS automatically generates a MessageDeduplicationId using a SHA-256 hash of the message body (excluding message attributes). You can optionally override this generated value by specifying a MessageDeduplicationId in the Publish action." }, "DataProtectionPolicy": { "type": "string", "description": "The body of the policy document you want to use for this topic. You can only add one policy per topic. The policy must be in JSON string format.", "maxLength": 20000 }, "KmsMasterKeyARN": { "type": "string", "description": "A valid AWS KMS key ARN to enable server-side encryption at rest. The ARN must be in the form of 'arn:aws:kms:ap-southeast-2:123456789023:key/ bb43bd18-3a75-482e-822d-d0d3a5544dc8'.", "pattern": "^(arn:(aws|aws-cn|aws-us-gov):kms:[a-z0-9-]+:[0-9]{12}:key/)?([a- f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12})$|^$", "default": "" }, "TracingConfig": { "type": "string", "description": "The tracing mode of an Amazon SNS topic. By default, TracingConfig is set to PassThrough, and the topic passes the tracing header it receives from an SNS publisher to its subscriptions. If set to Active, and the sampled ct-0zzf0fjz76jmb Version April 22, 2025 2055 AMS Advanced Change Type Reference AMS Advanced Change Type Details flag in the tracing header is true, SNS sends X-Ray segment data to the topic owner account.", "enum": [ "Active", "PassThrough" ], "default": "PassThrough" } }, "metadata": { "ui:order": [ "DisplayName", "Policy", "ArchivePolicy", "DeliveryPolicy", "ContentBasedDeduplication", "DataProtectionPolicy", "KmsMasterKeyARN", "TracingConfig" ] }, "additionalProperties": false }, "Priority": { "description": "The priority of the request. See AMS \"RFC scheduling\" documentation for a definition of the priorities.", "type": "string", "enum": [ "Low", "Medium", "High" ] } }, "metadata": { "ui:order": [ "TopicArn", "Parameters", "Priority" ] }, "required": [ "TopicArn" ], ct-0zzf0fjz76jmb Version April 22, 2025 2056 AMS Advanced Change Type Reference AMS Advanced Change Type Details "additionalProperties": false } Schema for Change Type ct-1078jhyxq32dp Classifications: • Management | Directory Service | Computer object | Remove SPN { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Remove Service Principal Name", "description": "Remove the Service Principal Name (SPN) associated with a specified hostname or host alias in Microsoft Active Directory. For multi-account landing zone (MALZ), use this change type in the shared services account.", "type": "object", "properties": { "DocumentName": { "description": "AWSManagedServices-RemoveADComputerSPN-Admin", "type": "string", "enum": [ "AWSManagedServices-RemoveADComputerSPN-Admin" ], "default": "AWSManagedServices-RemoveADComputerSPN-Admin" }, "Region": { "description": "The AWS Region where the Microsoft AD in Directory Service is located, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "Hostname": { "description": "The hostname of the computer tagged with the SPN.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\-\\_]{1,15}$" }, "minItems": 1, ct-1078jhyxq32dp Version April 22, 2025 2057 AMS Advanced Change Type Reference AMS Advanced Change Type Details "maxItems": 1 }, "ServiceType": { "description": "The type of service, such as MSSQLSvc, HTTP, TERMSRV, HOST, WSMAN, RestrictedKrbHost.", "type": "array", "items": { "type": "string", "enum": [ "MSSQLSvc", "HTTP", "TERMSRV", "HOST", "WSMAN", "RestrictedKrbHost" ], "default": "HOST" }, "minItems": 1, "maxItems": 1 }, "AliasName": { "description": "The alias associated with the host.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\-\\_]{1,15}$" } }, "GroupManagedServiceAccountName": { "description": "The group Managed Service Account (gMSA) name used to run the specified ServiceType.", "type": "array", "items": { "type": "string", "pattern": "^[a-zA-Z0-9\\-\\_]{1,15}$" } }, "Port": { "description": "The port the service utilizes; for example, 1433.", "type": "array", "items": { "type": "string", ct-1078jhyxq32dp Version April 22, 2025 2058 AMS Advanced Change Type Reference AMS Advanced Change Type Details "pattern": "^\\$?()([1-9]|[1-5]?[0-9]{2,4}|6[1-4][0-9]{3}|65[1-4][0-9]{2}| 655[1-2][0-9]|6553[1-5])$" } } }, "metadata": { "ui:order": [ "Hostname", "ServiceType", "AliasName", "GroupManagedServiceAccountName", "Port" ] }, "additionalProperties": false, "required": [ "Hostname", "ServiceType" ] } }, "metadata": { "ui:order": [ "DocumentName", "Region", "Parameters" ] }, "additionalProperties": false, "required": [ "DocumentName", "Region", "Parameters" ] } Schema for Change Type ct-10nh4ztyxu8kz Classifications: • Management | Trusted Remediator | State | Enable or disable ct-10nh4ztyxu8kz Version April 22, 2025 2059 AMS Advanced Change Type Reference AMS Advanced Change Type Details { "$schema": "http://json-schema.org/draft-04/schema#", "name": "Enable or disable Trusted Remediator service", "description": "Enable or disable the Trusted Remediator service. Can only be used in the Trusted Remediator delegated administrator account. When disabled, remediations are not performed in all member accounts.", "type": "object", "properties": { "DocumentName": { "description": "Must be AWSManagedServices-EnableOrDisableTrustedRemediator.", "type": "string", "enum": [ "AWSManagedServices-EnableOrDisableTrustedRemediator" ], "default": "AWSManagedServices-EnableOrDisableTrustedRemediator" }, "Region": { "description": "The AWS Region, in the form us-east-1.", "type": "string", "pattern": "^([a-z]{2}((-gov))?-[a-z]+-\\d{1})$" }, "Parameters": { "type": "object", "properties": { "ServiceState": { "description": "Enable or disable the Trusted Remediator service.", "type": "string", "enum": [ "ENABLE", "DISABLE" ] } }, "metadata": { "ui:order": [ "ServiceState" ] }, "required": [ "ServiceState" ], "additionalProperties": false } ct-10nh4ztyxu8kz Version April 22, 2025 2060 AMS Advanced Change Type Reference AMS Advanced Change Type Details }, "metadata": |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.