Layer E · Hyperscalers
AWS
Native AI billing combines model-level Bedrock pricing with AWS tagging, Cost Explorer, and compute optimisation tooling.
Last checked . Visit AWS
At a glance
- Category
- Hyperscalers
- Control layer
- E: Native provider controls
- Five-Layer model
- Usage Transparency, Delivery Alignment
- Status
- Active
- Typical buyers
- FinOps, Engineering and platform
- Delivery
- Built into a cloud or provider console
Buyer fit
Best native AI cost governance of the three major hyperscalers for organisations already committed to AWS. Note that deep AI workload integration with Bedrock creates meaningful switching costs if architecture decisions change. Native tooling is comprehensive but designed to keep you within the AWS ecosystem.
Market outlook
Market-leading hyperscaler. Not a consolidation target. The risk is not market stability. It is increasing dependency on AWS architecture as AI workloads deepen.
What to check
- Bedrock pricing exposes per-model token, query, guardrail, and throughput charges.
- Bedrock resources and some inference paths support tagging. AWS cost allocation tags flow into cost reporting.
- Cost Explorer, Cost Optimisation Hub, rightsizing recommendations, and Compute Optimizer support broader AI infrastructure control.
Sources
The map describes vendors from public sources; it does not rate, rank or recommend them, and no listing is paid for. Confirm pricing and capabilities with the vendor. See how the map is built.
By Ed Epstein, who works at IBM. The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. About and disclosure · Methodology