A company has two AWS accounts one for Production and one for Connectivity. A network engineer needs to connect the Production account VPC to a…

The correct procedure involves the owner of the resource initiating the sharing process. The Transit Gateway (TGW) resides in the Connectivity account, making it the owner. The Connectivity account must first share the TGW with the Production account using AWS Resource Access Manager (RAM). The Production account must then accept this resource share.

Once the share is accepted, the Production account (VPC owner) can create a VPC attachment to the shared TGW. Because the TGW is not configured to auto-accept attachments, the TGW owner (Connectivity account) must manually accept the pending attachment request. Finally, the Connectivity account associates the attachment with a TGW route table to control traffic flow.

A. The resource share for the Transit Gateway must be initiated from the owner account (Connectivity), not the consumer account (Production).

B. The resource that must be shared is the Transit Gateway itself, not the VPC subnets from the Production account.

C. The resource that must be shared is the Transit Gateway, not the VPC subnets. The share must be initiated by the TGW owner.

1. AWS Transit Gateway User Guide, "Share a transit gateway": This document outlines the process, stating, "The owner of the transit gateway (sharer) shares it with another account (sharee). The sharer is always the owner of the transit gateway. The sharee can't view, modify, or delete the shared transit gateway, but the sharee can create attachments to it." This confirms steps 1 and 2.

2. AWS Transit Gateway User Guide, "Work with transit gateway attachments", section "VPC attachments": This guide specifies, "If you attach a VPC in a different account from the transit gateway owner account, the attachment must be accepted by the transit gateway owner." This confirms step 4, which is necessary because auto-accept is disabled.

3. AWS Resource Access Manager User Guide, "Sharing your AWS resources", section "Sharing process": This document details the fundamental RAM workflow: "The account that owns a resource (the owner) can share it with another account (the consumer)... The consumer can't perform any actions on the shared resource until they accept the invitation to the resource share." This supports the overall sequence of sharing and accepting.