Consider the following network architectures when using AWS Direct Connect with your AWS DataSync transfers.
TipIf your network uses a transit gateway, we recommend separating your DataSync transfer's logical path to optimize costs (particularly if you're migrating a large amount of data).
For example, if you use AWS Transit Gateway for normal traffic between your on-premises networks and virtual private clouds (VPCs), you can configure your network so that DataSync traffic bypasses the transit gateway and its data processing charges.
Using Direct Connect with a DataSync VPC service endpointIf your DataSync agent uses a VPC service endpoint, you need a Direct Connect gateway to connect to your VPC.
Direct Connect architecture with VPC endpoint and S3 destinationThe following Direct Connect architecture shows a DataSync transfer from an on-premises storage system to an S3 bucket.
The DataSync agent routes DataSync traffic from the on-premises storage system (source location) to the Direct Connect connection.
DataSync traffic routes to a Direct Connect gateway thatâs used for your transfer. To set this up, you must:
DataSync traffic (control plane) routes through the DataSync VPC endpoint.
DataSync traffic (data plane) routes through the DataSync network interfaces in the subnet that you specify when creating the DataSync agent.
DataSync traffic routes through the DataSync service to the S3 bucket (destination location).
When transferring to or from an Amazon EFS or Amazon FSx file system, your file system and DataSync VPC endpoint can be in the same subnet.
The following Direct Connect architecture shows a DataSync transfer from an on-premises storage system to an Amazon EFS or Amazon FSx file system.
The DataSync agent routes DataSync traffic from the on-premises storage system (source location) to the Direct Connect connection.
DataSync traffic routes to a Direct Connect gateway that's used for your transfer. To set this up, you must:
DataSync traffic (control plane) routes through the DataSync VPC endpoint.
DataSync traffic (data plane) routes through the DataSync network interfaces in the file system's subnet. This is the same subnet where the DataSync VPC endpoint is located.
DataSync traffic routes through the DataSync service to the file system (destination location).
When transferring to or from an Amazon EFS or Amazon FSx file system, your file system and DataSync VPC endpoint can be in different subnets.
The following Direct Connect architecture shows a DataSync transfer from an on-premises storage system to an Amazon EFS or Amazon FSx file system.
The DataSync agent routes DataSync traffic from the on-premises storage system (source location) to the Direct Connect connection.
DataSync traffic routes to a Direct Connect gateway that's used for your transfer. To set this up, you must:
DataSync traffic (control plane) routes through the DataSync VPC endpoint.
DataSync traffic (data plane) routes through the DataSync network interfaces in the file system's subnet. This is a different subnet than where the DataSync VPC endpoint is located.
DataSync traffic routes through the DataSync service to the file system (destination location).
If your DataSync agent uses a public or Federal Information Processing Standard (FIPS) service endpoint, you can route your data transfer traffic through a Direct Connect connection by using a public virtual interface.
While Direct Connect advertises all local and remote AWS Region prefixes by default, you can use BGP community tags to control the scope (Regional or global) and route preference of traffic on the public virtual interface. You must advertise at least one public prefix to create your DataSync agent.
The following Direct Connect architecture shows a DataSync transfer from an on-premises storage system through a public or FIPS endpoint to an S3 bucket.
The DataSync agent routes DataSync traffic from the on-premises storage system (source location) to the Direct Connect connection.
DataSync traffic routes to the DataSync service through a public virtual interface.
DataSync traffic to the S3 bucket (destination location).
If you need a DataSync agent and haven't created one yet, deploy the agent, choose a service endpoint for the agent, and then activate the agent.
Once you create the agent, you can configure your network for DataSync.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4