Options
All
  • Public
  • Public/Protected
  • All
Menu

Class TransitGatewayPeeringConfig

NetworkConfig / TransitGatewayPeeringConfig

Transit Gateway peering configuration

To use TGW peering with requester TGW SharedServices-Main of SharedServices account in us-west-2 region with SharedServices-Main-Core TGW route table association and accepter TGW Network-Main of Network account in us-east-1 region with Network-Main-Core TGW route table association, please use following configuration. Please use following configuration. With autoAccept true LZA will make sure accepter account accepts the peering request. Flag applyTags set to false will not apply tags provided in requester of peering attachment to the accepter attachment

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

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

Index

Constructors

Properties

Constructors

constructor

Properties

Readonly accepter

accepter: TransitGatewayPeeringAccepterConfig = ...

Peering attachment accepter configuration

see

TransitGatewayPeeringAccepterConfig

Readonly autoAccept

autoAccept: true = true

Auto accept of transit gateway peering.

Readonly name

name: "" = ''

The friendly name of TGW peering.

Readonly requester

requester: TransitGatewayPeeringRequesterConfig = ...

Peering attachment requester configuration.

see

TransitGatewayPeeringRequesterConfig

Generated using TypeDoc