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:

- destinationCidrBlock: 0.0.0.0/0
attachment:
account: Network
vpcName: Network-Inspection

Destination prefix list:

- destinationPrefixList: accelerator-pl
attachment:
vpnConnectionName: accelerator-vpn

Blackhole route:

- destinationCidrBlock: 1.1.1.1/32
blackhole: true

Hierarchy

  • TransitGatewayRouteEntryConfig

Implements

Constructors

Properties

The target Transit Gateway attachment for the route table entry. Supported attachment types include:

  • VPC
  • Direct Connect Gateway
  • VPN
  • Transit Gateway Peering

Remarks

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.

See

TransitGatewayRouteTableVpcEntryConfig TransitGatewayRouteTableDxGatewayEntryConfig TransitGatewayRouteTableVpnEntryConfig

blackhole: undefined | boolean = undefined

(OPTIONAL) Enable to create a blackhole for the destination CIDR. Leave undefined if specifying a VPC destination.

destinationCidrBlock: undefined | string = undefined

The destination CIDR block for the route table entry.

Remarks

Use CIDR notation, i.e. 10.0.0.0/16. Leave undefined if specifying a destination prefix list.

destinationPrefixList: undefined | string = undefined

The friendly name of a prefix list for the route table entry.

Remarks

This is the logical name property of a prefix list as defined in network-config.yaml. Leave undefined if specifying a CIDR destination.

See

PrefixListConfig

Generated using TypeDoc