A company uses AWS Organizations. Each development team has its own AWS account, each with a single VPC and nonoverlapping CIDR blocks. An Amazon Aurora DB cluster resides in a shared services account, and all development teams must access live data from that cluster. Which solution provides the required connectivity to the DB cluster with the least operational overhead?

The correct answer is to use a Transit Gateway because it centralizes network connectivity for multiple VPCs, simplifying routing and management. By creating the Transit Gateway in the shared services account and sharing it via AWS Resource Access Manager (AWS RAM), development accounts can attach their VPCs to the Transit Gateway, enabling direct, private connectivity to the Aurora DB cluster without complex peering relationships. This approach minimizes operational overhead compared to managing individual VPC peering connections or other solutions. Using AWS RAM to share the DB cluster directly is incorrect because Aurora is a managed service and cannot be directly shared via AWS RAM for cross-account access in this manner. An Application Load Balancer (ALB) and AWS PrivateLink are designed for HTTP/S or TCP services, but Aurora is a database, and while PrivateLink can be used with database endpoints, it's typically for specific service consumption, not general cross-VPC connectivity for a shared resource like this. Site-to-Site VPN is for connecting on-premises networks to AWS or between VPCs, but using client VPN software for each development account introduces significant client-side overhead and is not the most efficient solution for inter-VPC communication within AWS.