- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I think I figured it out! When looking through my objects in my bucket, I noticed there is a toggle to view versions of the objects. I learned that two objects which are in the glacier storage tier had an old version of the same object in the standard tier storage class, so I deleted those standard tier storage versions of the objects. I'm not sure how or why versions were created on those two objects but none of the other objects. Working backwards from the charges on the bill and rate for the standard storage tier, the size billed matched the size of those standard tier version objects. I'll find out on my next bill, but I'm pretty sure I'll only get glacier storage tier charges moving forward.
Hi There
There are a few reasons (versioning might be turned on, etc), but the easiest way to see exactly why you are getting charged is by using the cost explorer.
- Go to the Cost Explorer Service
- Change the date range to the past month
- Change the Group By Dimension to Usage Type
- In the Filters, under Service, choose Glacier and S3
Below is a screenshot showing you how to setup your report. From there you will see the breakdown of charges by service. You can also change the Dimension to API Operation to get more info.
Thanks so much - this is helpful to learn that all of my data is being charged as S3 instead of Glacier. If my bucket is in S3, but then the objects in the bucket are under the Glacier Deep Archive storage class, why is the data being charged as S3? Do the objects have to be in an S3 Glacier Vault instead of an S3 Bucket? If so, what's the point of having a glacier deep archive storage class for objects in S3 buckets?