- 최신
- 최다 투표
- 가장 많은 댓글
Hi, DataSync can natively support cross region EFS transfers in the same account for regions that are enabled by default. https://docs.aws.amazon.com/datasync/latest/userguide/working-with-locations.html#working-with-locations-cross-regions
For transfers between EFS with an agent, you can reference this blog to verify configuration. https://aws.amazon.com/blogs/storage/transferring-file-data-across-aws-regions-and-accounts-using-aws-datasync/
Hello! I needed to transfer files from EFS to EFS between different regions in different accounts and I used the following article also mentioned above. https://docs.aws.amazon.com/datasync/latest/userguide/datasync-limits.html In the end I got the same error as the OP. I checked several time the post and my settings, everethyng looked OK. Data sync agent was green and ready to connect, VPC peering connection, endpoint, security groups etc were configured. But I missed only one thing from here https://docs.aws.amazon.com/datasync/latest/userguide/datasync-in-vpc.html
Make sure that you allow outbound traffic from the agent to these interfaces by using port 443.
So the security group in the destination account should allow connections from the VPC endpoint to EFS over TCP 2049 and from the DataSync EC2 instance (or subnet) from the source account over TCP 443. When I added the rules to the group, I was able to transfer data. Hope this helps someone.
Okay so the solution is actually user need to create location in the dedicated region separately or create location directly when you are creating task to replicate cross-region data.
When creating a task in the AWS DataSync management console, you can independently select which region the source and destination Amazon EFS locations reside in. You can choose to create a new EFS location in the selected region, or use an existing location that exists in the selected region.