Troubleshooting higher than expected S3 storage costs with DataSync - AWS DataSync

Troubleshooting higher than expected S3 storage costs with DataSync

If your Amazon S3 storage costs are higher than you thought they would be following an AWS DataSync transfer, it might be due to one or more of the following reasons:

  • When transferring to or from S3 buckets, you incur costs related to S3 API requests made by DataSync.

  • DataSync uses the Amazon S3 multipart upload feature to upload objects to S3 buckets. This approach can result in unexpected storage charges for uploads that don't complete successfully.

  • DataSync copies object tags from source and destination objects when Copy object tags is enabled on the console or ObjectTags is set to PRESERVE. Copying of these object tags can incur S3 API request costs.

  • Object versioning might be enabled on your S3 bucket. Object versioning results in Amazon S3 storing multiple copies of objects that have the same name.

Actions to take

In these cases, you can take the following steps:

  • Make sure you understand how DataSync uses S3 requests and how they might be affecting your storage costs. For more information, see Evaluating S3 request costs when using DataSync.

  • If the issue is related to multipart uploads, configure a policy for multipart uploads for your S3 bucket to clean up incomplete multipart uploads to reduce storage cost. For more information, see the AWS blog post S3 Lifecycle Management Update - Support for Multipart Uploads and Delete Markers.

  • If the issue is related to copying object tags and you don't need object tags, clear the Copy object tags checkbox in the DataSync console or set ObjectTags to None when creating, starting, or updating a task.

  • If the issue is related to object versioning, disable object versioning on your S3 bucket.

f you need additional help, contact AWS Support Center.