Transit Gateway DNS Config
arrayList of mappings from remote DNS server IP address sets to proxied internal domains, for a transit gateway
attachment.
Remote DNS Server IP Addresses to connect to for resolving internal DNS via a transit gateway.
Example:10.0.0.2
Internal domain names to proxy for DNS resolution from the listed remote DNS server IP addresses,
for a transit gateway.
Example:foobar.com
Transit Gateway Name
stringHuman-readable name of the transit gateway.
Transit Gateway CIDR Blocks
arrayCIDR blocks for constructing a route table for the transit gateway, when attaching to the owning
network.
PrivateDnsResponse
One OfExample:1850820b-c69f-4a2a-b9be-bbcdbc5cd618
The current state of the Private DNS attachment. Possible values:
created- The attachment has been created but is not attached to Private DNS.initializing- The attachment is in the process of being initialized and is setting up necessary resources.pending-associationThe attachment request is awaiting association to the cloud provider infrastructure in order for provisioning to proceed.ready- The attachment is fully operational and can route traffic as configured.error- The attachment is in an error state, and is not operational.terminating- The attachment is in the process of being deleted.terminated- The attachment has been fully deleted and is no longer available.
Allowed values:createdinitializingpending-associationreadyerrorterminatingterminated
Metadata describing the backing state of the Private Dns and why it may be in an erroneous state.
Show Child Parameters
Monotonically-increasing version count of the Private DNS, to indicate the order of updates to the
Private DNS.
Example:1
An RFC-3339 timestamp representation of Private DNS creation date.
Example:2022-11-04T20:10:06.927Z
An RFC-3339 timestamp representation of Private DNS update date.
Example:2022-11-04T20:10:06.927Z
Human-readable name of the Private DNS.
Example:us-east-2 private dns
Show Child Parameters
AwsPrivateHostedZoneResponse
objectExample:1850820b-c69f-4a2a-b9be-bbcdbc5cd618
The current state of the Private DNS attachment. Possible values:
created- The attachment has been created but is not attached to Private DNS.initializing- The attachment is in the process of being initialized and is setting up necessary resources.pending-associationThe attachment request is awaiting association to the cloud provider infrastructure in order for provisioning to proceed.ready- The attachment is fully operational and can route traffic as configured.error- The attachment is in an error state, and is not operational.terminating- The attachment is in the process of being deleted.terminated- The attachment has been fully deleted and is no longer available.
Allowed values:createdinitializingpending-associationreadyerrorterminatingterminated
Metadata describing the backing state of the Private Dns and why it may be in an erroneous state.
Show Child Parameters
Monotonically-increasing version count of the Private DNS, to indicate the order of updates to the
Private DNS.
Example:1
An RFC-3339 timestamp representation of Private DNS creation date.
Example:2022-11-04T20:10:06.927Z
An RFC-3339 timestamp representation of Private DNS update date.
Example:2022-11-04T20:10:06.927Z
Human-readable name of the Private DNS.
Example:us-east-2 private dns