Well hold on now. AWS has never, to my knowledge, increased prices for an existing service. They'll introduce new EC2 instance types that aren't as cheap as you were expecting, but the existing types you're already using don't get more expensive. Nobody gets hit with a price increase unless they choose to switch types. If you keep doing the same thing, you'll keep getting the same prices.
On the other hand, this Google BigQuery price increase is a real, honest-to-god price hike for existing customers. If you keep doing the same thing, the cost will change.
They've consistently lowered them. But that makes sense, as they want as many companies to go all-in as possible. Because the egress is still egregiously high, there's terrific lock-in for big clients. They wouldn't raise prices until the exact right moment.
AWS has never increased prices though, like since they started. Atleast I can't find any references to any price increase.
The link showing "price/performance ratio for newer instances is rising" is deceptive. It just shows vcpu/hour, which doesn't really measure real world performance. Like m5.large is a significant performance improvement over m4.large. Newer instances also carry improvements not shown in the link.
Data Transfer
-------------
$0.20 per GB - data uploaded
$0.20 per GB - data downloaded
to:
Data Transfer
-------------
$0.10 per GB - all data transfer in
$0.18 per GB - first 10 TB / month data transfer out
$0.16 per GB - next 40 TB / month data transfer out
$0.13 per GB - data transfer out / month over 50 TB
Requests
-------------
$0.01 per 1,000 PUT or LIST requests
$0.01 per 10,000 GET and all other requests
(No charge for delete requests)
It hasn't disappeared from my memory! There were people who did very, umm, "creative" things with S3 (classic example, creating a virtual disk by storing each 512-byte sector as an S3 object) who suddenly changed direction after the pricing changed.
I agree that AWS does much better than Google though -- the S3 change was a big wakeup call to them about pricing all the dimensions rather than assuming people will use a service the same way as Amazon uses it internally.
Interesting that the differential between different regions is remaining the same.
You would imagine that if some big user were slurping up all the spot instances worldwide, then it would level out regional pricing differences. Or, if not level it out, change it based on that users sensitivity to bandwidth costs in/out of each region.
That makes me think that the spot pricing change is a gradual AWS algorithm change instead - I'm sure they'd be smart enough to apply a pricing change with some smooth function based on date.
You can shop around a bit for AWS for spot instances. Spot prices in eu-west-3 (Paris) are not that wild yet for the same c5a instances. Somteimes, a region has all its spot instances near the on-demand price. At least they seem to be smoothing out their changes over days. (I think it used to be more wild in the past.)
The problem is there's been growing demand across the world and/or more people optimizing costs and moving from on-demand -> spot. It's not a single user doing this.
There were hardware shortages earlier. I think it's just a case of AWS can't expand fast enough to meet demand for now.
Important to note that AWS doesn’t control spot prices: it’s a market where you bid on what you’re willing to pay. Customers control the cost through their bids.
edit; and prices tend to surge at end of quarter, regardless of provider. I’ve seen that for years at AWS and it’s only increased year over year.
For AWS, one of the people behind https://ec2instances.info showed that the price/performance ratio for newer instances is rising, https://github.com/patmyron/cloud/#compute--memory-unit-pric... meaning cloud users are paying more for less.