AWS pricing changes and billing changes since 2026-01-01, as a dated log: one row per change to a price list, a commitment programme, an export format or a billing mechanism, with who it affects and the AWS announcement behind it. A product launch without an effect on the bill is not a row. The log starts on 2026-01-01, is extended by the handbook's monthly rescan, and never loses a row: a correction is a new row with its own date.
Changes
| Date | What changed | Who is affected | Source |
|---|---|---|---|
| 2026-10-08 | Cost Explorer, AWS Budgets and the Billing and Cost Management dashboards group and filter Amazon Bedrock cost by product attributes: model, model provider, inference type and feature; a budget can be narrowed to them | Bedrock users who allocate or cap spend per model | Bedrock product attributes in Cost Explorer |
| 2026-09-25 | The new ListBillingViewSegments API returns an account's billing context over a period: payer or member, billing group, billable or pro forma rates, split into time segments where the context changed | Accounts that moved between organizations or billing groups | Billing context API |
| 2026-09-22 | Billing Transfer creates billing groups automatically for two-level transfers, with a pricing plan set once per inbound transfer relationship | Distributors and partners billing through Billing Transfer | Automatic billing group creation |
| 2026-09-15 | Billing Conductor pricing rules take exact custom rates and usage tier breaks per SKU instead of percentage markups or markdowns on public on-demand prices | Pro forma bills for subsidiaries and end customers | Custom rates and usage tiers |
| 2026-08-21 | AWS Glue 6.0 is generally available at a price 30 percent below the earlier versions; the reduction applies to jobs that select Glue 6.0 | Glue ETL jobs | Glue 6.0 price reduction |
| 2026-08-21 | Amazon Bedrock passes on OpenAI's cut for GPT-5.6 Sol: USD 4 per million input and USD 20 per million output tokens, promotional at least until 2026-11-21 | Bedrock users of the OpenAI models | Bedrock pricing for GPT-5.6 Sol |
| 2026-08-11 | Cost allocation by IAM principal also covers inference through the bedrock-mantle endpoint, as it has for bedrock-runtime since April | Bedrock users allocating by user or role | IAM principal allocation for bedrock-mantle |
| 2026-07-20 | Data Exports carry standardized Bedrock product metadata in CUR 2.0: model provider, model name, pricing unit, inference type and feature, under one Amazon Bedrock product family | Everyone attributing Bedrock spend from CUR 2.0 | Bedrock product metadata in Data Exports |
| 2026-07-01 | EKS Auto Mode and ECS Managed Instances charge lower management fees on GPU and accelerated instances: G-series minus 35 percent, P-series and Trainium minus 60 percent; announced on 2026-07-07 | GPU nodes under Auto Mode or Managed Instances | EKS Auto Mode GPU fees |
| 2026-06-16 | S3 Vectors query data-processing charges fall by up to 80 percent for indexes above 10 million vectors, automatically | S3 Vectors users with large indexes | S3 Vectors query charges |
| 2026-06-15 | Accounts in Billing Conductor or Billing Transfer billing groups keep their history in Cost Explorer at billable rates, which the billing group used to hide | Accounts moved into billing groups | Cost Explorer history in billing groups |
| 2026-06-10 | A CUR 2.0 export's table configuration (content, granularity, columns, format, destination) can be changed on the existing export; the next delivery uses the new settings | CUR 2.0 export owners | CUR 2.0 table configuration updates |
| 2026-06-02 | CUR 2.0 exports can be delivered for Athena or Redshift in Parquet with table definitions and templates, as CUR 1.0 could | Teams querying CUR 2.0 with SQL | CUR 2.0 Athena and Redshift integration |
| 2026-04-27 | Billing Conductor's Passthrough Pricing Plan shows every account of a Billing Transfer group the AWS invoice values, at no charge, in US East (N. Virginia) | Billing Transfer users without custom pricing | Passthrough Pricing Plan |
| 2026-04-14 | Data Exports deliver Standard exports (CUR 2.0, FOCUS, cost optimization recommendations, carbon emissions) to an S3 bucket in another authorized account | Organizations centralising billing data | Cross-account delivery |
| 2026-04-09 | Amazon Bedrock inference cost can be allocated by IAM user and role: tag the principals, activate the tags, and select the caller identity allocation data in a CUR 2.0 export | Bedrock users with shared accounts | Cost allocation by IAM user and role |
| 2026-03-05 | Database Savings Plans cover Amazon OpenSearch Service and Amazon Neptune Analytics: up to 35 percent for a one-year commitment in USD per hour, no upfront payment | OpenSearch Service and Neptune Analytics usage | Database Savings Plans expansion |
| 2026-02-06 | AWS Network Firewall applies the NAT Gateway discounts behind secondary endpoints too and drops the Advanced Inspection data charge of USD 0.001 to 0.009 per GB in 13 regions, EU (Milan) among them | Network Firewall with TLS inspection or several endpoints | Network Firewall price reductions |
| 2026-01-15 | Data Exports name Bedrock operations: line_item_operation in CUR and x_Operation in FOCUS show InvokeModelInference or InvokeModelStreamingInference instead of Usage | Everyone filtering Bedrock rows by operation | Bedrock operation types in Data Exports |
How to read your bill after a change
A price-list change (Glue 6.0, S3 Vectors, the GPU management fees, Network Firewall, a Bedrock model price) keeps the usage types and lowers the rate. The check is therefore the rate per usage type on either side of the effective date: line_item_unblended_rate grouped by line_item_usage_type in CUR 2.0, ListUnitPrice and ContractedUnitPrice in the FOCUS export. A reduction that starts mid-month shows as two rates for one usage type in one month. Nothing has to be done, unless the reduction applies only to a new version, as with Glue 6.0: then the job has to move first. Where the columns sit is in the AWS Cost and Usage Report and FOCUS columns.
A commitment programme change (Database Savings Plans) adds rows with line_item_line_item_type SavingsPlanCoveredUsage and SavingsPlanNegation for the services that joined, and the plan's coverage and utilisation move with them. Both are explained in AWS Savings Plans and commitment coverage and utilisation. A plan bought before the date covers the new services as soon as the rows appear; the console's recommendation only recalculates on its next run.
An export format change (cross-account delivery, configuration on the existing export, delivery for Athena and Redshift, Bedrock metadata and operation types) reaches an existing export only once its configuration is updated. From then on, queries that filter line_item_operation on Usage for Bedrock return nothing, and the new product attributes sit in the product map column. The queries behind the monthly report are best run against one month of the new export before the switch. The export's structure is in the AWS Cost and Usage Report, and what Bedrock meters in AI and machine learning services.
A cost allocation change (IAM principal tags, product attributes) applies from activation forward; earlier months are not backfilled. The principal tags appear in the resource_tags columns after the first full day, and the share without a tag shows which roles are still missing. The rules for tags as a whole are under tags and labels.
A billing hierarchy change (Billing Conductor rates, Billing Transfer groups, the billing context API) separates pro forma data from billable data by design; the API says which view an account had in which period, and comparing the two views shows the markup or markdown built in. The accounts and their relationships are explained in billing accounts and hierarchies.
Sources
Read on 2026-10-21. AWS What's New, filtered to billing, cost management and pricing, AWS Cost Management User Guide document history, AWS Data Exports User Guide, AWS Savings Plans pricing, AWS pricing; each row links its announcement.