A retail company is migrating its regional store inventory management system to AWS. The architecture requires connecting spoke VPCs, each owned by a different AWS account within the same AWS Organization, to a shared on-premises system. A Solutions Architect plans to deploy AWS Transit Gateway in a dedicated network hub account.
Which TWO configurations must the architect perform to establish basic multi-account network connectivity between the spoke VPCs and the shared Transit Gateway? (Select TWO.)
- Create the Transit Gateway in the dedicated network hub account, and use AWS Resource Access Manager (RAM) to share the gateway with the AWS Organization.Cevap
- In each spoke account, create a Transit Gateway VPC attachment for the local VPC targeting the shared Transit Gateway.Cevap
- CEstablish VPC Peering connections between all spoke VPCs to allow transitive traffic to traverse a central Virtual Private Gateway.
- DDeploy a single NAT Gateway in a shared services VPC and route all inter-VPC traffic through it to perform network address translation.
- EAssociate a centralized Route 53 Private Hosted Zone directly with the Transit Gateway to manage cross-VPC IP address routing.
Cevap
The correct configurations are sharing the Transit Gateway using AWS Resource Access Manager (RAM) from the hub account, and creating Transit Gateway VPC attachments in each spoke account.
To connect VPCs across multiple AWS accounts to a centralized Transit Gateway, the gateway must be created in a central account and shared with the member accounts using AWS Resource Access Manager (RAM). Once shared, each spoke account must create a Transit Gateway VPC attachment to link its VPC to the Transit Gateway, enabling hub-and-spoke traffic flow.
Adım Adım Çözüm
Anahtar Kavram
Multi-account network connectivity using AWS Transit Gateway shared via AWS Resource Access Manager (RAM).