- Newest
- Most votes
- Most comments
Yes. Your calculations are correct. The requests are counted on per object basis. However, do not forget to consider the overhead. https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-transition-general-considerations.html
S3 Glacier and S3 Glacier Deep Archive transition request charges— Each object that you transition to the S3 Glacier or S3 Glacier Deep Archive storage class constitutes one transition request. There is a cost for each such request. If you plan to transition a large number of objects, consider the request costs. If you are archiving small objects, consider aggregating many small objects into a smaller number of large objects to reduce transition request costs.
Storage overhead charges – When you transition objects to the S3 Glacier or S3 Glacier Deep Archive storage class, a fixed amount of storage is added to each object to accommodate metadata for managing the object.
For each object archived to S3 Glacier or S3 Glacier Deep Archive, Amazon S3 uses 8 KB of storage for the name of the object and other metadata. Amazon S3 stores this metadata so that you can get a real-time list of your archived objects by using the Amazon S3 API. For more information, see Get Bucket (List Objects). You are charged Amazon S3 Standard rates for this additional storage.
For each object that is archived to S3 Glacier or S3 Glacier Deep Archive, Amazon S3 adds 32 KB of storage for index and related metadata. This extra data is necessary to identify and restore your object. You are charged S3 Glacier or S3 Glacier Deep Archive rates for this additional storage.
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated a year ago