- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Please check to see if Versioning is enabled in the bucket.
Using versioning in S3 buckets - Amazon Simple Storage Service
Normal Amazon S3 rates apply for every version of an object stored and transferred. Each version of an object is the entire object; it is not just a diff from the previous version. Thus, if you have three versions of an object stored, you are charged for three objects.
It was indeed enabled. I don't know how it got enabled on that bucket. Thank you for your help, I forgot versioning was even something offered.
if you use multipart uploads, you may have failed uploads stored in your bucket. Those aren't shown in the bucket, but need to be seen another way. You can set a lifecycle rule on your bucket to delete these failed uploads. Here's an article on how to do that. I would set it to one day at first or you'll have to wait quite a while for it to take effect. You can always change it later after it takes effect.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 9 Monaten- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
Just to add some other ideas to this thread. If you have versioning enabled, you can configure a Lifecycle Policy to remove older versions either by date or to keep only the last x (some number) of versions. [1]
There is another answer on this post that talks about Multipart Uploads (MPUs). That is another source of common extra storage costs and can be removed also by Lifecycle Policies.
I also highly recommend enabling S3 Storage Lens [2]. The default settings are free (advanced metrics have a cost). This can help you find old versions and MPUs in your buckets.
[1] https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html [2] https://aws.amazon.com/blogs/aws/s3-storage-lens/