Hacker News new | ask | show | jobs
by byefruit 429 days ago
"In addition, S3 Express One Zone has reduced the per-GB charges for data uploads and retrievals by 60 percent, and these charges now apply to all bytes transferred rather than just portions of requests greater than 512 KB"

It's not clear but are there cases where this could be a significant price rise? If you exclusively had small objects (<512kb) being written and read then this could add up quickly.

1 comments

If all your GET requests are 512KB in response, this "price reduction" is effectively a price raising. GET requests go up to $0.000323 per 1K from $0.0002 per 1K.
The article states a new price of $0.00003 /1k requests, an order of magnitude lower than your indication. Maybe you have miscounted the number of zeroes, or did I miss something in the calculation?
Before this change, 1000 512KB GET requests cost $0.0002 ($2e-4).

After this change, 1000 512KB GET requests cost $0.00003 + $0.0006 / 1024*3 * 512 * 1024 * 1000 = $0.00003 ($3e-5) + $0.00029296875 (2.93e-4, dominates the cost) = $0.00032296875, so roughly $0.0003 ($3e-4).

It's because before this change all data transfer charge was waived as long as requests are smaller than 512KB.

The announcement did mention it explicitly, but it tried to downplay it, by starting the sentence with a price reduction:

> In addition, S3 Express One Zone has reduced the per-GB charges for data uploads and retrievals by 60 percent, and these charges now apply to all bytes transferred rather than just portions of requests greater than 512 KB.

This "and" should be a "BUUUUUUUUUUUUUUUUUUUUUUUT".