Networking Account | Add Static Route

Create a static route on transit gateway (TGW) route table. Use this change type for multi-account landing zone (MALZ) Networking accounts only.

Full classification: Deployment | Managed landing zone | Networking account | Add static route

Change Type Details

Change type ID	ct-3r2ckznmt0a59
Current version	1.0
Expected execution duration	60 minutes
AWS approval	Required
Customer approval	Not required
Execution mode	Automated

Additional Information

Add a static route

Networking account: Adding a static route 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.

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: Adding a 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\" : [\"[e-mail]\"]}}" 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-3r2ckznmt0a59" --change-type-version "1.0" --title "Create a static route on Transit Gateway Route Table" --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 AddStaticRouteParams.json:

   aws amscm get-change-type-version --change-type-id "ct-3r2ckznmt0a59" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > AddStaticRouteParams.json

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

   {
     "DocumentName": "AWSManagedServices-CreateRouteInTGWRouteTable",
     "Region": "us-east-1",
     "Parameters": {
       "DestinationCidrBlock" : [ "10.0.0.0/24" ],
       "Blackhole" : [ "false" ],
       "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ],
       "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ]
     }
   }

3. Output the RFC template JSON file to a file; this example names it AddStaticRouteRfc.json:

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

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

   {
     "ChangeTypeVersion": "1.0",
     "ChangeTypeId": "ct-3r2ckznmt0a59",
     "Title": "Create a static route on Transit Gateway Route Table"
   }

5. Create the RFC, specifying the AddStaticRouteRfc file and the AddStaticRouteParams file:

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

Before you run this Change Type, confirm the following points:

• The TGW route table exists and is available.

• The TGW route table is not DMZBastionsRouteDomain or EgressRouteDomain.

• The TGW attachment exists.

• The CIDR is not default (0.0.0.0/0), invalid, or that the route already exists.

Note

If you want to add a route in the DMZBastionsRouteDomain or EgressRouteDomain route table, then use the ct-0xdawir96cy7k to open a MOO RFC.

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

Example: Required Parameters

{
  "DocumentName": "AWSManagedServices-CreateRouteInTGWRouteTable",
  "Region": "us-east-1",
  "Parameters": {
    "DestinationCidrBlock": ["10.0.2.0/24"],
    "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ]
  }
}

Example: All Parameters

{
  "DocumentName": "AWSManagedServices-CreateRouteInTGWRouteTable",
  "Region": "us-east-1",
  "Parameters": {
    "Blackhole": [false],
    "DestinationCidrBlock": ["10.0.2.0/24"],
    "TransitGatewayAttachmentId": [ "tgw-attach-0878cf82a40721d19" ],
    "TransitGatewayRouteTableId": [ "tgw-rtb-06ddc751c0c0c881c" ]
  }
}