Readonly
attachmentThe target Transit Gateway attachment for the route table entry. Supported attachment types include:
CAUTION: Changing the attachment type or target after initial deployment creates a new route table entry. To avoid core pipeline failures, use multiple core pipeline runs to 1) delete the existing route entry and then 2) add the new route entry.
Note: Leave undefined if specifying a blackhole destination.
TransitGatewayRouteTableVpcEntryConfig TransitGatewayRouteTableDxGatewayEntryConfig TransitGatewayRouteTableVpnEntryConfig
Readonly
blackhole(OPTIONAL) Enable to create a blackhole for the destination CIDR. Leave undefined if specifying a VPC destination.
Readonly
destinationThe destination CIDR block for the route table entry.
Use CIDR notation, i.e. 10.0.0.0/16. Leave undefined if specifying a destination prefix list.
Readonly
destinationThe friendly name of a prefix list for the route table entry.
This is the logical name
property of a prefix list as defined in network-config.yaml.
Leave undefined if specifying a CIDR destination.
Generated using TypeDoc
NetworkConfig / TransitGatewayConfig / TransitGatewayRouteTableConfig / TransitGatewayRouteEntryConfig
Transit Gateway static route entry configuration. Use this configuration to define static route entries in a Transit Gateway route table.
Example
Destination CIDR:
Destination prefix list:
Blackhole route: