- Newest
- Most votes
- Most comments
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
Hope you find this helpful.
Comment here if you have additional questions.
Abhishek
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/.
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
Sorry I had to edit my answer as I missed s3 billing console part at first place.
Great, thank you for the information Abhishek