NetworkConfig / TransitGatewayPeeringConfig / TransitGatewayPeeringRequesterConfig

Transit Gateway (TGW) peering requester configuration. Use this configuration to define the requester side of the peering attachment.

Example

transitGatewayName: SharedServices-Main
account: SharedServices
region: us-west-2
routeTableAssociations: SharedServices-Main-Core
tags:
- key: Name
value: Network-Main-And-SharedServices-Main-Peering

Hierarchy

  • TransitGatewayPeeringRequesterConfig

Implements

Constructors

Properties

account: string = ''

The friendly name of the account of the requester transit gateway

Remarks

This is the logical account property of the requester transit gateway as defined in network-config.yaml.

See

TransitGatewayConfig

region: string = 'us-east-1'

The name of the region the accepter transit gateway resides in

See

TransitGatewayConfig

routeTableAssociations: string = ''

The friendly name of TGW route table to associate with this peering attachment.

Remarks

This is the logical name property of a route table for the requester TGW as defined in network-config.yaml.

See

TransitGatewayRouteTableConfig

tags: undefined | Tag[] = undefined

(OPTIONAL) An array of tag objects for the Transit Gateway Peering.

transitGatewayName: string = ''

The friendly name of the requester transit gateway

Remarks

This is the logical name property of the requester transit gateway as defined in network-config.yaml.

CAUTION: Changing this property after initial deployment will cause the peering attachment to be recreated. Please be aware that any downstream dependencies may cause this property update to fail.

See

TransitGatewayConfig

Generated using TypeDoc