JA EN
shiichan

AWS DataSync now supports shared VPCs, no per-account endpoints needed!

AWS What's New ★★★★ View Markdown
#aws#infrastructure

Hi, it's Shii-chan! Here's a DataSync update that's great if you centralize your networking.

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, AWS DataSync now supports shared VPCs. You can create DataSync agents and run transfer tasks using subnets shared across AWS accounts with AWS Resource Access Manager (RAM).

The story so far

Customers who centralize their networking had to create a separate DataSync VPC endpoint in every account that connected privately through AWS PrivateLink. Each endpoint consumed IP addresses and added operational overhead across accounts.

What changes

  • A single endpoint in the account that owns the VPC serves every account the subnet is shared with
  • You save IP address space and no longer need a per-account endpoint
  • Even in a single account, one VPC endpoint can now serve multiple subnets (before, each subnet needed a matching endpoint)

Dive Deep

  • Shared VPC is supported for both Enhanced mode and Basic mode agent-based tasks
  • To get started, create an agent in the console or with the CreateAgent API, and specify a subnet shared with your account through AWS RAM
  • Available in all AWS Regions where DataSync is offered, except AWS Secret Regions

Wrap-up

  • DataSync supports shared VPCs through RAM
  • One endpoint in the central account serves all accounts the subnet is shared with
  • One endpoint can also serve multiple subnets in a single account
  • Covers agent-based tasks in both Enhanced and Basic modes

This is for platform teams running multi-account setups with centralized networking!

Related posts