There are a variety of options you can use to empty a bucket. They are listed here.
A really good option is to have lifecycle policies do the deletion (expiration) for you. See this link for setting up a lifecycle policy and this link specifically covers expiration. With this you can have the policy expire/delete any objects that are older than X. That should help you remove anything old. One thing to keep in mind is that there might be a delay between the expiration date and the date at which Amazon S3 removes an object. You are not charged for expiration or the storage time associated with an object that has expired.
Thank you, Paul! So far all my files are still there, so I just added a noncurrent rule to try that. I'll leave it over the weekend and hope to come back to an empty bucket next week. Thanks again.
How can I explicitly specify the size of the files to be split or the number of files?Accepted Answerasked 4 months ago
Access to S3- thousands of usersasked a month ago
Empty bucket not really empty?asked 8 months ago
Options to accelerate s3 copy of 4TB worth files between S3 buckets in same regionAccepted Answerasked 2 years ago
S3 Inventory : Is there a limit to the number of objects in a bucket that will show up in the inventory?Accepted Answerasked 4 years ago
used lifecycle rule to empty bucket, cw show size 0(ish), files still thereasked 3 years ago
Rotation of bitnami Apache log filesasked 2 years ago
unable to access S3 log files owned by "s3-log-service"asked 3 years ago
Cannot see files in S3/Glacier when using Synology Glacier app for backupasked 3 months ago
Can't empty (full!) bucketAccepted Answerasked a month ago