Hacker News Reader

Those fees for "operations" are there for a good reason. Otherwise, us smart techies would hack it.

I heard a talk by someone at a mega tech company that has their own internal cloud for their teams, and they "charge" each team based on usage. One team stored lots of file with 12,000 character filenames with zero contents. Since the company only "charged" for file size, that team had a tiny charge!

>> No fees for PUT, POST, LIST, HEAD, GET, DELETE...no extra fees for Akamai CDN requests

or you can say the fee is bundled, i.e.

(Rackspace) vs (S3 us-east-1)

Storage: 0.105/GB/mo vs 0.085/GB/mo

Bandwidth out: 0.20/GB/mo vs 0.120/GB/mo

The problem was people implemented a file system on top of s3. From what I understand, Amazon added the charges, which are pretty nominal, to prevent people from hammering s3 as a block storage system.

What are the hidden fees in the S3 use case?