NetworkConfig / TransitGatewayPeeringConfig

Transit Gateway (TGW) peering configuration. Use this configuration to define a peering attachment between two TGWs.

Remarks

Use autoAccept true if you'd like the accelerator to automatically accept the peering attachment Use applyTags `true' if you'd like the requester attachment tags to be replicated to the accepter attachment

Note: accepter property autoAccept and applyTags are optional. Default value for autoAccept is true and applyTags is false.

The following example creates a cross-account and cross-region peering connection between a requester TGW named SharedServices-Main and accepter TGW named Network-Main:

Example

transitGatewayPeering:
- name: Network-Main-And-SharedServices-Main-Peering
autoAccept: false
requester:
transitGatewayName: SharedServices-Main
account: SharedServices
region: us-west-2
routeTableAssociations: SharedServices-Main-Core
tags:
- key: Name
value: Network-Main-And-SharedServices-Main-Peering
accepter:
transitGatewayName: Network-Main
account: Network
region: us-east-1
routeTableAssociations: Network-Main-Core
autoAccept: true
applyTags: false

Hierarchy

  • TransitGatewayPeeringConfig

Implements

Constructors

Properties

Constructors

Properties

Peering attachment accepter configuration

See

TransitGatewayPeeringAccepterConfig

name: string = ''

The friendly name of TGW peering.

Peering attachment requester configuration.

See

TransitGatewayPeeringRequesterConfig

Generated using TypeDoc