Does moving data from S3 Standard to S3 Glacier Deep Archive affect DataTransfer-Out-Bytes?

Question

I recently moved data (~100TB) from s3 Standard to s3 Glacier Deep Archive via a Lifecycle policy. However, I also noticed a huge spike in the DataTransfer-Out-Bytes category of the S3 billing console from the same day. Does moving data from S3 Standard to S3 Glacier Deep Archive get billed to DataTransfer-Out-Bytes?

secondabhi_aws · Accepted Answer

Sorry I had to edit my answer as I missed s3 billing console part at first place.

Data transfer from s3 standard to glacier deep archive would not be charged, however in s3 billing you'll see spike in DataTransfer-Out-Bytes. This is a correlation but certainly not the cause. You'll be charged for Lifecycle Transition requests into (per 1,000 requests) but there is no data transfer cost involved it, please refer [S3 Pricing FAQ](https://aws.amazon.com/s3/pricing/)

Hope you find this helpful.

Comment here if you have additional questions.

Abhishek

AWS-User-alantam · Answer

Agree with the answers provided above. If you see a spike on DataTransfer-Out-Bytes, that means there has been data transferred out from your S3 buckets to the Internet. The region code in front of "DataTransfer-Out-Bytes" (e.g. USW2-DataTransfer-Out-Bytes) indicates the source region (US-WEST-2) the data is transferred out from. If there is no region code, it defaults to US-EAST-1. Please refer to https://aws.amazon.com/blogs/networking-and-content-delivery/understand-aws-data-transfer-details-in-depth-from-cost-and-usage-report-using-athena-query-and-quicksight/.

Does moving data from S3 Standard to S3 Glacier Deep Archive affect DataTransfer-Out-Bytes?

Contenus pertinents