Follow

S3 - How To - Move objects from one bucket to another

Process:

Create a new S3 bucket

  1. Open the Amazon S3 console.
  2. Choose Create Bucket.
  3. Choose a DNS-compliant name for your new bucket.
  4. Select your AWS Region.
    Note: It's best practice to create the new bucket in the same region as the source bucket to avoid performance issues associated with cross-region traffic.
  5. If needed, choose Copy settings from an existing bucket to mirror the configuration of the source bucket.

Install and configure the AWS Command Line Interface (AWS CLI)

  1. Install the AWS Command Line Interface.
  2. Configure the AWS CLI by running the following command:
aws configure
  1. Enter your Access Keys (Access Key ID and Secret Access Key).
  2. Press Enter to skip the default region and default output options. For information about region parameters, see AWS Regions and Endpoints for Amazon S3.
    Note: The AWS CLI outputs are json, text, or table, but not all the commands support each type of output. If the command output doesn't support your chosen format, it defaults to its own format. For more information, see Controlling Command Output from the AWS Command Line Interface.

Copy the objects between the S3 buckets

  1. If you have archived S3 objects in Amazon Glacier, restore the objects stored in Amazon Glacier.
  2. Copy the objects between the source and target buckets by running the following sync command:
aws s3 sync s3://SOURCE_BUCKET_NAME s3://NEW_BUCKET_NAME

Note: Update the command to include your target and source bucket names.

The sync command uses the CopyObject APIs to move objects between S3 buckets. The sync command lists the source and target buckets to identify objects that are in the source but not the target bucket, or to identify objects in the source bucket that have different LastModified dates than the objects in the target bucket. The sync command on a versioned bucket copies only the current version of the object—previous versions are not copied. By default, this preserves object metadata, but the access control lists (ACLs) are set to FULL_CONTROL for your AWS account, which removes any additional ACLs. If the operation fails, you can run the sync command again without duplicating previously copied objects.

Verify that the objects are moved

  1. Verify the contents of the source and target buckets by running the following command:
aws s3 ls --recursive s3://SOURCE_BUCKET_NAME --summarize > bucket-contents-source.txt
aws s3 ls --recursive s3://NEW_BUCKET_NAME --summarize > bucket-contents-new.txt

Note: Update the command to include your target and source bucket names.

  1. Compare objects in the source and target buckets by using the outputs that are saved to files in the AWS CLI directory. See the following example output:
$ aws s3 ls --recursive s3://BUCKETNAME –summarize
2017-11-20 21:17:39      15362 s3logo.png
Total Objects: 1        Total Size: 15362

Update existing API calls to the new bucket name

Update any existing applications or workloads so that they use the new bucket name. You might need to run sync commands to address discrepancies between source and target buckets if you have frequent writes.

 

If you continue to experience difficulties, please open a case with the DLT Opscenter using the following contact information:

1-888-358-7658

Opscenter@dlt.com

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk