Options
All
  • Public
  • Public/Protected
  • All
Menu

Transit Gateway peering accepter configuration

example
transitGatewayName: Network-Main
account: Network
region: us-east-1
routeTableAssociations: Network-Main-Core
autoAccept: true
applyTags: false

Hierarchy

  • TransitGatewayPeeringAccepterConfig

Implements

Index

Constructors

Properties

account: "" = ''

Accepter transit gateway account name

applyTags: false = false

Peering request apply tags flag. When this flag is on, requester attachment tags will be applied to peer or accepter attachment also. In peer or accepter attachment existing tags can't be changed, only given tags will be added or modified.

autoAccept: true = true

Peering request auto accept flag. When this flag is on, peering request will be accepted by LZA

region: "af-south-1" | "ap-east-1" | "ap-northeast-1" | "ap-northeast-2" | "ap-northeast-3" | "ap-south-1" | "ap-southeast-1" | "ap-southeast-2" | "ca-central-1" | "cn-north-1" | "cn-northwest-1" | "eu-central-1" | "eu-north-1" | "eu-south-1" | "eu-west-1" | "eu-west-2" | "eu-west-3" | "me-south-1" | "sa-east-1" | "us-east-1" | "us-east-2" | "us-gov-east-1" | "us-gov-west-1" | "us-west-1" | "us-west-2" | "us-iso-west-1" | "us-iso-east-1" | "us-isob-east-1" = 'us-east-1'

Accepter transit gateway region name

routeTableAssociations: "" = ''

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

transitGatewayName: "" = ''

Accepter transit gateway name

Generated using TypeDoc