# AWS DataSync adds shared-VPC support for centralized private endpoints > Accounts sharing a subnet can now use one centrally managed DataSync VPC endpoint instead of separate endpoints for private connectivity. Canonical URL: https://www.devobs.io/news/news-event-66bc873cad95b58eae612e62/ By: Arjun Shah Published: 2026-10-02T09:32:54.373Z Updated: 2026-10-02T09:32:54.373Z Event date: 2026-09-29 Section: Cloud AWS announced shared Virtual Private Cloud (VPC) support for DataSync on September 29, 2026. The update lets customers create DataSync agents and run transfer tasks using subnets shared across AWS accounts through AWS Resource Access Manager (RAM). According to the [AWS announcement](https://aws.amazon.com/about-aws/whats-new/2026/09/aws-datasync-shared-vpcs/), participating accounts can transfer data privately through a shared subnet and a centrally managed DataSync VPC endpoint. ## What changes in the endpoint model AWS says customers with centralized networking previously needed a separate DataSync VPC endpoint in each account connecting privately through AWS PrivateLink. With shared-VPC support, a single endpoint in the account that owns the VPC can serve every account with which the subnet is shared. AWS identifies reduced endpoint maintenance and conserved IP-address space as benefits. The launch also changes single-account configurations: one VPC endpoint can now serve multiple subnets, replacing the previous requirement for a matching endpoint in each subnet. Both changes are described in the [launch notice](https://aws.amazon.com/about-aws/whats-new/2026/09/aws-datasync-shared-vpcs/). ## What network teams should evaluate The architectural change is endpoint consolidation: DataSync connectivity can follow a shared-network design rather than requiring an endpoint in each consuming account. Before consolidating existing connectivity, teams should identify which accounts and transfer workflows would depend on the shared endpoint. They should also establish who owns endpoint configuration and coordinates changes. Those dependency and ownership questions are worth addressing alongside the reduction in endpoint resources. ## Availability and setup AWS says shared-VPC support is available for both Enhanced mode and Basic mode agent-based tasks in all AWS Regions where DataSync is offered, except AWS Secret Regions. To get started, AWS directs users to create a DataSync agent through the console or the `CreateAgent` API and specify a subnet shared with their account through AWS RAM. The [announcement](https://aws.amazon.com/about-aws/whats-new/2026/09/aws-datasync-shared-vpcs/) provides the availability scope and starting instructions. ## Source references -