← Back to all announcements
★★☆☆☆ 09/06/2026

AWS Cost Explorer launches intelligent cost explanations powered by Amazon Q

One click now turns any Cost Explorer report into an AI-generated cost narrative—no manual digging required, at no extra charge.

View original announcement →

Visual Summary

graph TD A{{"Analyze with Amazon Q"}}:::announced B((Cloud User)):::external C(AWS Cost Explorer):::compute D(Amazon Q Developer):::compute E(Cost & Usage Reports):::storage F([Cost Trend Analysis]):::feature G([Anomaly Detection]):::feature H([Forecast Explanations]):::feature I([Conversational Follow-up]):::feature B ==>|"single click"| C C ==>|"passes context"| A A -->|"powered by"| D A -->|"reads from"| E A -->|"delivers"| F A -->|"surfaces"| G A -.->|"future dates"| H D -.->|"maintains context"| I I -.->|"drill deeper"| A classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0 classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32 classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100 classDef external fill:#f5f5f5,stroke:#616161,color:#616161

What's New

AWS Cost Explorer has introduced "Analyze with Amazon Q," a new capability that delivers AI-powered, comprehensive cost explanations directly within the Cost Explorer console. With a single button click, users receive detailed analysis from Amazon Q Developer covering cost trends, top cost drivers, and anomalies—all scoped to the exact filters and time period currently configured in their view. The feature also supports conversational follow-up questions, allowing users to iteratively explore cost insights without leaving the console.

How It Works

  • Context-aware analysis: When a user clicks "Analyze with Amazon Q," the feature reads the current Cost Explorer report configuration—including active filters, groupings, and selected date ranges—and passes that full context to Amazon Q Developer for analysis.
  • Adaptive explanation modes: Amazon Q automatically determines whether to deliver historical cost explanations, forward-looking forecast explanations, or a combined analysis depending on whether the selected time period covers past dates, future dates, or both.
  • Inline chat panel delivery: Analysis results are surfaced directly in Amazon Q's chat panel within the Cost Explorer console, keeping insights co-located with the underlying charts and tables rather than requiring a context switch to a separate tool.
  • Conversational follow-up: Amazon Q maintains full conversation context throughout the session, enabling users to ask natural-language follow-up questions to drill deeper into any identified trend, anomaly, or cost driver.
  • Bidirectional interactivity: Users can also use the "Ask question" button or suggested prompts to query costs in their own words, and Cost Explorer will automatically update its charts, tables, filters, groupings, and dates to reflect the analysis.
  • No additional data pipeline required: The feature operates on the same underlying dataset used by Cost Explorer, the AWS Cost and Usage Reports, and detailed billing reports—no separate data export or ingestion is needed.

Why It's Important

  • Eliminates manual investigation overhead: Previously, understanding cost spikes or trends required iterating across multiple filters, dimensions, and time windows manually; this feature collapses that workflow into a single click.
  • Democratizes cost analysis: Finance, operations, and engineering teams without deep AWS billing expertise can now obtain actionable, plain-language explanations of complex cost patterns without needing to be Cost Explorer power users.
  • Accelerates optimization cycles: By surfacing top cost drivers and anomalies proactively and guiding users toward optimization opportunities, the feature shortens the time between cost event and corrective action.
  • Reduces cognitive load at scale: As AWS environments grow in complexity—more accounts, services, and regions—manual cost analysis becomes exponentially harder; AI-assisted explanation scales with that complexity.
  • No cost barrier to adoption: The feature is available at no additional charge, removing any financial friction that might otherwise slow enterprise adoption of AI-assisted FinOps practices.

How It's Different

  • Single-click versus multi-step investigation: Traditional Cost Explorer usage required manually configuring filters, switching dimensions, and cross-referencing multiple reports; "Analyze with Amazon Q" delivers a synthesized explanation in one action.
  • Context-preserving AI versus generic chatbot: Unlike a standalone AI assistant, Amazon Q here is fully aware of the user's current report configuration—filters, groupings, and time period—making its analysis immediately relevant rather than requiring the user to re-describe their context.
  • Conversational depth versus static reports: Standard Cost Explorer reports are static outputs; the new feature enables an iterative dialogue where each follow-up question refines or extends the analysis within the same session.
  • Forecast-aware explanations: The feature uniquely adapts its analysis to future-dated views by providing forecast explanations, a capability not present in traditional cost reporting workflows.
  • Integrated versus external tooling: Compared to exporting data to a third-party BI or AI tool for analysis, this capability keeps the entire workflow inside the AWS console, reducing data movement and maintaining access controls.

When to Prefer It

  • Investigating unexpected cost spikes: When a cost anomaly appears in a report and the root cause is not immediately obvious, "Analyze with Amazon Q" can quickly surface the top contributing factors without manual dimension-by-dimension drilling.
  • Monthly or quarterly cost reviews: Finance and FinOps teams conducting periodic cost reviews can use the feature to generate a structured narrative explanation of cost trends to share with stakeholders.
  • Onboarding new team members: Engineers or analysts new to AWS billing can use the conversational interface to learn what is driving costs in their environment without requiring deep Cost Explorer expertise.
  • Pre-budget planning: When viewing forecast periods, teams can use the feature to understand projected spend trajectories and identify services likely to exceed budget thresholds before they do.
  • Multi-service or multi-account environments: Organizations running complex, multi-account AWS environments benefit most from AI-assisted synthesis, where manually correlating costs across accounts and services is time-consuming.
  • Ad hoc cost questions during architecture reviews: Engineers evaluating architectural changes can quickly query cost implications of current usage patterns as part of a design or optimization discussion.

Availability

  • GA status: Generally available as of June 9, 2026; this is not a preview or beta release.
  • Regional availability: Available in all commercial AWS Regions; not currently listed for AWS GovCloud or China Regions based on the announcement.
  • Pricing: Available at no additional charge; standard Cost Explorer API usage fees ($0.01 per paginated API request) still apply for programmatic access, but the console feature itself is free.
  • Prerequisites: Cost Explorer must be enabled on the AWS account; once enabled, it cannot be disabled, and initial data preparation takes up to a few days for historical data.
  • Data freshness: Cost Explorer refreshes underlying cost data at least once every 24 hours, so Amazon Q's analysis reflects data with up to a 24-hour lag depending on upstream billing data availability.
  • Access point: Available directly in the AWS Cost Explorer console at https://console.aws.amazon.com/cost-management/home.

Tags

Servicesq-developer
Typenew-featurega-launch
Conceptsgenaiconversational-aidata-analytics
Use Casescost-optimizationobservability
GeographyGlobal

Related Resources

AI Radar AWS

AWS AI/ML news — curated, researched, explained

An automated intelligence platform that curates, researches, and analyzes AWS AI/ML/GenAI announcements daily. Every report is backed by real research — the system reads linked blog posts and documentation to provide accurate, in-depth analysis.

How Each Report Is Generated

  1. Collection — Daily monitoring of the AWS "What's New" RSS feed
  2. Filtering — AI-powered relevance detection for AI/ML/GenAI topics
  3. Taxonomy Tagging — LLM-based classification across 6 dimensions
  4. Importance Scoring — Point-based system with tag bonuses (1-5 stars)
  5. Research Phase — Follows links to blog posts and documentation
  6. Report Generation — Claude Sonnet produces structured 6-section analysis
  7. Visual Summary — Claude Opus generates Mermaid diagrams for key items
  8. Publishing — Static website rebuilt and deployed via CloudFront

Features

  • Faceted filtering by service, type, concept, and more
  • Multi-dimensional taxonomy with 80+ tags across 6 dimensions
  • Geographic availability badges (Global, APJ, EMEA, AMER) with filtering
  • Timeline visualization of announcement volume
  • PDF export for offline reading
  • Mermaid visual summaries for key announcements
  • Daily automated updates — no manual curation
What makes this different: Each report involves a dedicated research phase where the system reads linked blog posts and AWS documentation pages. This produces analysis that goes beyond the original announcement text.

Technology

Built with Python, AWS Lambda, Amazon Bedrock (Claude Sonnet 4.6, Opus 4.6, Haiku 4.5), S3, CloudFront, WAF, EventBridge, and CDK.

Open Source

This project is open source. Fork it, customize it for your needs, and deploy your own instance.
📦 github.com/bbonik/ai-radar-aws

How Importance Scoring Works

Each announcement receives a point score based on multiple factors. The total score maps to a 1-5 star rating:

1★ < 2 pts 2★ ≥ 2 pts 3★ ≥ 3.5 pts 4★ ≥ 5 pts 5★ ≥ 6.5 pts

Point Breakdown

FactorPointsWhen
Core AI service (Bedrock, AgentCore, SageMaker AI)+4Service named in title
Key AI service (SageMaker, Kiro, QuickSight)+2Service named in title
Other AI-related service+1Default
Blog post link+3Link to aws.amazon.com/blogs/
GitHub samples link+2Link to github.com/aws*
Documentation link+1Link to docs.aws.amazon.com/
New model+1.5Tagged as "new-model"
New service+1Tagged as "new-service"
New feature+0.5Tagged as "new-feature"
Anthropic / OpenAI provider+2Provider explicitly mentioned
Instance / notebook announcement-2Hardware/capacity, not feature
Performance / pricing / security-0.5Incremental updates
Region expansion to APJ+1Expands to Asia Pacific
Region expansion (non-APJ only)-1.5Only expands to other regions

Geographic Relevance Badges

Each announcement card shows a small badge indicating whether the feature is available in your region:

🌐 Global Available in all regions
🌏 APJ Asia Pacific
🌍 EMEA Europe / Middle East / Africa
🌎 AMER Americas (US, Canada, South America)
No badge Geography unknown
How geography is detected: The system detects ALL geographies mentioned in each announcement. If the text mentions specific regions (Tokyo, Frankfurt, Oregon, etc.), the corresponding geography badges are shown. If it says "all regions" or is a new feature with no region specified, it gets the Global badge. Geography is also filterable — click a geo chip to see only announcements available in that region.