AWS Security ChangesHomeSearch

AWS datasync: DataSync VPC endpoint multi-subnet and shared subnet support

Service: datasync · 2026-09-29 · Documentation medium

File: datasync/latest/userguide/choose-service-endpoint.md · Type: network

Summary

Clarifies that a single DataSync VPC service endpoint can serve agents across multiple subnets, adds support for RAM-shared VPC subnets, and notes security group/private IP requirements.

Security assessment

The added guidance documents network configuration for VPC endpoints and explicitly requires security groups to allow traffic between agents and endpoint/network interfaces; it is security-adjacent but does not reference a specific vulnerability or incident.

Evidence

+  * Your [security group](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html) must allow traffic between your agent and the private IP addresses of the VPC service endpoint. It must also allow traffic between your agent and the network interfaces that DataSync creates in the subnet that you specify when creating an agent.

Diff

diff --git a/datasync/latest/userguide/choose-service-endpoint.md b/datasync/latest/userguide/choose-service-endpoint.md
index 190ab6539..07d12af8e 100644
--- a//datasync/latest/userguide/choose-service-endpoint.md
+++ b//datasync/latest/userguide/choose-service-endpoint.md
@@ -70,0 +71,2 @@ If you use a VPC service endpoint, your data isn't transferred across the public
+  * [Using a single VPC service endpoint across multiple subnets](./choose-service-endpoint.html#vpc-endpoint-multiple-subnets)
+
@@ -84,2 +85,0 @@ The VPC service endpoint (along with the [network interfaces](./required-network
-  * DataSync doesn't support [shared VPCs](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-sharing.html).
-
@@ -91 +91,5 @@ The VPC service endpoint (along with the [network interfaces](./required-network
-You create a VPC service endpoint for DataSync in a VPC that you manage. Your service endpoint, VPC, and DataSync agent must belong to the same AWS account.
+You create a VPC service endpoint for DataSync in a VPC that you manage.
+
+###### Note
+
+DataSync now supports using a VPC subnet shared through [AWS Resource Access Manager (RAM)](https://docs.aws.amazon.com/ram/latest/userguide/what-is.html). A shared subnet can be used when creating an agent.
@@ -119 +123,3 @@ We recommend disabling this setting in case you have agents in the same VPC that
-    7. For **Subnet** , choose the subnet where you want to create the VPC service endpoint. Take note of the subnet ARN (you need this when activating your agent).
+    7. For **Subnet** , choose the subnet where you want to create the VPC service endpoint.
+
+The subnet where you create the VPC service endpoint doesn't need to be the subnet that you specify when creating an agent. For more information, see Using a single VPC service endpoint across multiple subnets.
@@ -131,0 +138,34 @@ The security group must allow your agent to connect with the private IP addresse
+### Using a single VPC service endpoint across multiple subnets
+
+You don't need a separate DataSync VPC service endpoint for every subnet that you use with DataSync. A single VPC service endpoint can serve agents across multiple subnets.
+
+This works because the subnet that you specify when creating an agent and the subnet that contains your VPC service endpoint serve two different purposes:
+
+  * **The subnet that you specify when creating an agent** determines where DataSync creates the [network interfaces](./required-network-interfaces.html) that handle data transfer traffic for your tasks.
+
+  * **The subnet that contains your VPC service endpoint** determines the private IP addresses that your agent uses to communicate with the DataSync service. You provide one of these IP addresses as `privateLinkEndpoint` when you [get an activation key](./activate-agent.html#get-activation-key).
+
+
+
+
+###### Note
+
+The subnet that you specify when creating an agent is where DataSync creates network interfaces when your AWS storage location is Amazon S3. For other AWS storage locations, DataSync creates the network interfaces in the same subnet as your file system. For more information, see [Network interfaces for AWS DataSync transfers](./required-network-interfaces.html).
+
+Neither subnet has to be the subnet where you deployed your agent VM or Amazon EC2 instance.
+
+###### Note
+
+When you create an agent, the VPC service endpoint ID that you specify is recorded for informational purposes only. Your agent communicates through the private IP address that you provide as `privateLinkEndpoint` when you [get an activation key](./activate-agent.html#get-activation-key). If you use several VPC service endpoints in the same VPC, make sure that this IP address belongs to the endpoint that you intend the agent to use.
+
+When using a single VPC service endpoint across multiple subnets, keep the following in mind:
+
+  * The VPC service endpoint can be in a different VPC from the subnet that you specify when creating an agent.
+
+  * Your [security group](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html) must allow traffic between your agent and the private IP addresses of the VPC service endpoint. It must also allow traffic between your agent and the network interfaces that DataSync creates in the subnet that you specify when creating an agent.
+
+  * Your agent must be able to reach the private IP addresses of the VPC service endpoint. By default, a VPC service endpoint is routable from any subnet in the same VPC.
+
+
+
+