A company is using AWS Organizations to manage multiple AWS accounts. A SysOps Administrator in the primary network management account creates an AWS Transit Gateway and shares it with a member account using AWS Resource Access Manager (RAM). A SysOps Administrator in the member account accepts the resource share and creates a Transit Gateway VPC attachment. However, traffic is not routing between the member VPC and other VPCs connected to the Transit Gateway. In the member account, the Transit Gateway attachment state is displayed as 'pendingAcceptance'. Which action is required to resolve this issue and enable network transit?
- AThe SysOps Administrator in the member account must update the subnet route tables to target the Transit Gateway attachment.
- BThe SysOps Administrator in the member account must configure the AWS Resource Access Manager (RAM) resource share to enable automatic attachment acceptance.
- The SysOps Administrator in the primary network management account must accept the shared attachment request.Cevap
- DThe SysOps Administrator in the member account must add an inbound rule to the stateless Network ACL of the attachment subnets to allow ephemeral port range traffic.
Cevap
The SysOps Administrator in the primary network management account must accept the shared attachment request.
The correct action is for the administrator in the primary network management account to accept the shared attachment request. When a Transit Gateway is shared with another AWS account via AWS Resource Access Manager (RAM), any VPC attachments created by the recipient account are placed in a 'pendingAcceptance' state. The owner of the Transit Gateway must explicitly accept the attachment request before the VPC can route traffic through the gateway, unless auto-acceptance of shared attachments has been pre-configured on the Transit Gateway.
Adım Adım Çözüm
Anahtar Kavram
Acceptance workflow for shared Transit Gateway attachments across AWS accounts