4 ms·
> If you've got an old account charging you 22¢ a month, don't get mad. Start a snarky Twitter account and make sure you cost them orders of magnitude more than
by Scoundreller 7y ago
> If you've got an old account charging you 22¢ a month, don't get mad. Start a snarky Twitter account and make sure you cost them orders of magnitude more than that in doing damage control each month instead.
I use S3 for hosting static sites only, and only in North American zones.
Some time ago, I see some billing lines stating:
"US West (Oregon) data transfer to Asia Pacific (Tokyo) 0.001 GB $0.01"
I had no idea why I'd be paying for transfer to a zone outside my own. Obviously I don't care about the 1cent, but my small problem may be someone else's big problem.
Instead of looking into it, they refunded me a month of service (a few dollars).
I guess that's the opposite of @QuinnPig's thought, but seriously, what was the charge for? Someone running their own crawler on EC2 so I paid for internal DC-DC charges?
- wj 7y agoI saw that too and figured it was due to Cloudfront.
- Scoundreller 7y agoNot using Cloudfront though.
- QuinnyPig 7y agoYou got it. It's someone else on an AWS account somewhere. Maybe they're VPNing in. Maddening, no?
- cthalupa 7y ago>I guess that's the opposite of @QuinnPig's thought, but seriously, what was the charge for? Someone running their own crawler on EC2 so I paid for internal DC-DC charges? Yes. Other customers accessing your publicly available resources pay the internal AWS fees. Which is nice in that it saves you money, not nice in that it's not super intuitive so if you see it you think you've got some resource sitting around somewhere that shouldn't be.