AWS S3 Deep Archive objects charged at standard rate.

Question

I uploaded a few objects to my standard S3 buckets and manually converted them to Deep Archive by changing their storage class from the console.

For some reason I am seeing storage charges for these objects in standard class (USE2-TimedStorage-ByteHrs) instead of Deep Archive (USE2-TimedStorage-GDA-ByteHrs	
). Is this expected? How do I stop incurring those charges?

FWIW, object lock and encryption is enabled on the bucket.

![Enter image description here](/media/postImages/original/IMQWQqcDPsQgaUjH-mEPt-zQ)
![Enter image description here](/media/postImages/original/IMTe-sEKuRQ_iNH5CS75WbJw)

Answer

Hi,

Since you have uploaded an object to an Amazon S3 standard storage and them you have manually moved into an Amazon S3 Glacier Deep Archive storage class, you need to pay for the standard storage and storage-class transition costs.

The best option to avoid this costs is to [upload the file directly to Amazon S3](https://docs.aws.amazon.com/amazonglacier/latest/dev/uploading-an-archive.html) Glacier. However, you cannot upload archives to S3 Glacier by using the management console, so you must use the AWS CLI, the REST API, or the Amazon SDKs.

I recommend you take a look at the following links to understand it in more detail.
* [Can you write data directly to a Glacier IR bucket without the data going into a Standard S3 bucket first?](https://repost.aws/es/questions/QUMxf8hodJQUGru0Mc5BccHA/can-you-write-data-directly-to-a-glacier-ir-bucket-without-the-data-going-into-a-standard-s3-bucket-first)
* [Direct Upload to Glacier vs Upload through Amazon S3](https://www.msp360.com/resources/blog/compare-amazon-glacier-direct-upload-and-glacier-upload-through-amazon-s3/)

AWS S3 Deep Archive objects charged at standard rate.

相關內容