A company hosts its core network services, including directory services and DNS, in its on- premises data center. The data center is connected to the AWS Cloud using AWS Direct Connect (DX). Additiona

Creating a separate Direct Connect connection for each new account would be prohibitively expensive, complex to manage, and result in very high operational overhead, directly contradicting the requirements.

VPC endpoints are used to privately access AWS services (like S3, DynamoDB) from within a VPC without traversing the internet. They are not used to route traffic from AWS accounts to on-premises network services via Direct Connect.

Creating individual VPN connections between each new account and a central DX VPC would increase complexity, potentially add latency, and incur more management overhead than a centralized Transit Gateway solution, which is designed for this multi-account connectivity pattern.

AWS Transit Gateway is purpose-built to act as a central hub for connecting multiple VPCs across different AWS accounts and on-premises networks via AWS Direct Connect or VPN. By attaching the Direct Connect gateway to the Transit Gateway, all connected AWS accounts can consistently and cost-effectively route traffic to the on-premises core network services through a single, managed connection point, significantly reducing operational overhead compared to managing individual network connections for each account.