Amazon gives customers more detailed billing of their cloud services
Updated: Amazon is still not carving out EC2 compute instances in smaller-than-an-hour increments as we speculated it might, and as Cloud Sigma and ProfitBricks already do. But now it is offering customers …
Context & Ripple Effects
Amazon's 2009 EC2 pricing adjustments marked an earlier step toward serving enterprise cloud buyers. The new billing detail improves customers' ability to trace cloud-service charges, while EC2 compute remains billed in one-hour increments.
That leaves Cloud Sigma and ProfitBricks differentiated on a separate dimension: both already offer compute billing in increments shorter than an hour. The broad same-day pickup across cloud and developer outlets underscores that billing mechanics had become a meaningful competitive issue.
First-order effects
- Amazon customers gain more granular visibility into their cloud-service charges, improving internal allocation and review of usage costs.
- Amazon preserves hourly EC2 billing, so the change clarifies charges without reducing the minimum billing increment for compute users.
Second-order effects
- Cloud Sigma and ProfitBricks retain a concrete pitch to workloads that need sub-hour compute increments; Amazon's better bills do not erase that usage-granularity difference.
- Enterprise cloud buyers can compare providers on both invoice transparency and billing increments, rather than treating published compute rates as the full cost signal.
Third-order effects
- If providers pair clearer bills with more granular consumption models, cloud competition shifts toward how accurately customers can measure and match infrastructure use, not only headline instance prices.
The trend: Cloud infrastructure pricing is evolving from simple posted rates toward finer-grained measurement, billing, and customer cost attribution.