{"id":12750,"date":"2022-04-22T23:32:49","date_gmt":"2022-04-23T05:32:49","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=12750"},"modified":"2026-03-05T23:32:02","modified_gmt":"2026-03-06T05:32:02","slug":"migrating-data-between-amazon-s3-buckets-using-aws-datasync","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/migrating-data-between-amazon-s3-buckets-using-aws-datasync\/","title":{"rendered":"How to Transfer Data Between Amazon S3 Buckets Using AWS DataSync"},"content":{"rendered":"
\n
\"\"<\/a><\/figure>\n<\/div>\n\n\n

Migration of data is an inevitable process in website hosting. In conventional methods, we will do the migrations manually across the servers, which is hectic in a way. In AWS we have a new feature called AWS DataSync which will transfer the data in S3 buckets between two AWS instances, regions, accounts, etc. With DataSync we can do a one-time data transfer and also can schedule the migration whenever we needed.<\/p>\n\n\n\n

We will see some examples of data transfer below, thus we can have a proper understanding of the AWS DataSync.<\/p>\n\n\n\n

Transferring data within the same Amazon S3 account<\/strong><\/h3>\n\n\n\n

Select the DataSync page in the AWS console and create a task using the \u2018Task\u2019 option in the left menu bar. Then choose \u2018Create a new location\u2019 and for location type select \u2018Amazon S3\u2019 from the source location option. <\/p>\n\n\n\n

After that, we have to select the AWS region, S3 bucket. Storage class and the directory from which we have to transfer the data. Then for the IAM role, we have to click on the Autogenerate button.<\/p>\n\n\n\n

The same is followed in destination location options. Choose the destination accordingly with the Location type as \u2018Amazon S3\u2019<\/p>\n\n\n\n

After that we need to name the task that we are going to execute.<\/p>\n\n\n\n

After the last check of the configurations, we have input earlier, we need to start the task by clicking on the \u2018Create Task\u2019 button.<\/p>\n\n\n\n

Transferring data across accounts<\/strong><\/h3>\n\n\n\n

The first step we need to do is <\/strong>to create the necessary IAM role in the destination AWS account. This is to access the source S3 bucket, then we need to attach a new policy for the created IAM role in the source S3 bucket.<\/p>\n\n\n\n

{    “Version”: “2012-10-17”,    “Statement”: [        {            “Action”: [                “s3:GetBucketLocation”,                “s3:ListBucket”,                “s3:ListBucketMultipartUploads”            ],            “Effect”: “Allow”,            “Resource”: “arn:aws:s3:::SOURCEBUCKET”        },        {            “Action”: [                “s3:AbortMultipartUpload”,                “s3:DeleteObject”,                “s3:GetObject”,                “s3:ListMultipartUploadParts”,                “s3:PutObjectTagging”,                “s3:GetObjectTagging”,                “s3:PutObject”            ],            “Effect”: “Allow”,            “Resource”: “arn:aws:s3:::SOURCEBUCKET\/*”        }    ]}<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n

After that, we need to add the trust relationship in the IAM role.<\/p>\n\n\n\n

{  “Version”: “2012-10-17”,  “Statement”: [    {      “Effect”: “Allow”,      “Principal”: {        “Service”: “datasync.amazonaws.com”      },      “Action”: “sts:AssumeRole”    }  ]}<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n

From the AWS command line, we need to create S3 bucket location in the source for DataSync. Please have a note on the Amazon resource names(ARN) while creating the DataSync location and then use it on the following S3 bucket policy.<\/p>\n\n\n\n

{    “Version”: “2012-10-17”,    “Statement”: [        {            “Sid”: “BucketPolicyForDataSync”,            “Effect”: “Allow”,            “Principal”: {                “AWS”: [                “arn:aws:iam::DEST-ACCOUNT-ID:role\/DEST-ACCOUNT-ROLE”,                “arn:aws:iam::DEST-ACCOUNT-ID:role\/DEST-ACCOUNT-USER”]            },            “Action”: [                “s3:GetBucketLocation”,                “s3:ListBucket”,                “s3:ListBucketMultipartUploads”,                “s3:AbortMultipartUpload”,                “s3:DeleteObject”,                “s3:GetObject”,                “s3:ListMultipartUploadParts”,                “s3:PutObject”,                “s3:GetObjectTagging”,                “s3:PutObjectTagging”            ],            “Resource”: [                “arn:aws:s3:::SOURCEBUCKET”,                “arn:aws:s3:::SOURCEBUCKET\/*”            ]        }    ]}<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n

Now using the IAM role specified in the source S3 bucket policy, open the command line and run the following for the ARN.<\/p>\n\n\n\n

aws sts get-caller-identity<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n
aws datasync create-location-s3 –s3-bucket-arn arn:aws:s3:::SOURCEBUCKET –s3-config ‘{“BucketAccessRoleArn”:”arn:aws:iam::DEST-ACCOUNT-ID:role\/DEST-ACCOUNT-ROLE”}’<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n

This will give a similar output to the following, which means the source S3 bucket has been created.<\/p>\n\n\n\n

{“LocationArn”: “arn:aws:datasync:Region:DEST-ACCOUNT-ID:location\/loc-xxxxxxxxxxxxxx”}<\/td><\/tr><\/tbody><\/table><\/div><\/figure>\n\n\n\n

Except for the following location choose option the other steps are the same as we did on the data transfer on the same account. Since we have already created the source and destination locations we need to choose the location as the existing source location.<\/p>\n\n\n\n

After configuring the source and destination, click on the \u2018Create task\u2019 which will start the data transfer.<\/p>\n\n\n\n

If you require help, contact SupportPRO Server Admin<\/a><\/p>\n\n\n\n

\n

Facing issues? <\/p>\n\n\n\n

Our technical support
engineers can solve it. <\/p>\n\n\n\n\"Contact<\/a><\/span>