[vdm]

"Requests & data retrievals" tab footnote, above the grid:

> LIST requests for any storage class are charged at the same rate as S3 Standard PUT, COPY, and POST requests.

I read this as LISTs do not cost double for infrequent access, even though other Tier 1 requests do.

[jffry]

What a confusing mess. If LIST pricing is separate then it's strange to include it in the column of a table of storage-class pricing like that. But I agree that's what that statement seems to be saying.

AWS's own pricing calculator doesn't split out LIST requests: https://calculator.aws/#/createCalculator/S3

Either way, the takeaway is that using LIST or a bucket inventory, will still be O(N) cost and there's only a factor-of-2-ish difference between the two.

Then again, a billion objects is $5 territory to delete, and if you have a trillion objects to delete and no pre-existing listing to go off of, then odds are you can stomach the $5000 hit more easily than you could stomach the staff time spent trying to reduce that cost!