AWS Billing and Cost Management is not one service. It is a financial management console made of several tools that help you do five major things:
1. Pay and manage invoices
2. Understand what AWS is costing
3. Organize cost by account, team, product, environment, or tag
4. Alert and plan against budget
5. Optimize spend using commitments and savings recommendations
AWS describes Billing and Cost Management as a suite for setting up billing, retrieving and paying invoices, analyzing, organizing, planning, and optimizing AWS costs. In larger organizations, AWS Organizations is normally used to consolidate charges across multiple AWS accounts. (AWS Documentation)
For your AWS multi-environment setup, think of it like this:
AWS Accounts
Dev / Stage / UAT / Prod / Shared
↓
AWS Organizations Management or Payer Account
↓
Billing and Cost Management
↓
Bills, Cost Explorer, Budgets, Data Exports, Cost Categories, Tags,
Cost Anomaly Detection, Cost Optimization Hub, Savings Plans, Reservations
The management/payer account is usually the right place to manage organization-wide billing, budgets, Cost Explorer, Data Exports, cost allocation tags, cost categories, and savings visibility.
1. The correct mental model
AWS cost data flows like this:
AWS services create usage
EC2, EKS, RDS, NAT Gateway, S3, CloudWatch, ALB, Route 53, etc.
↓
AWS billing pipeline calculates charges
↓
Billing and Cost Management
↓
Cost Explorer / Bills / Budgets / Data Exports / Cost Categories / Tags
↓
Dashboards, reports, alerts, chargeback, optimization
Important distinction:
| Need | Correct AWS feature |
|---|---|
| Final invoice and payment record | Bills / Payments |
| Daily/monthly spend investigation | Cost Explorer |
| Budget alerting | AWS Budgets |
| Unexpected spike detection | Cost Anomaly Detection |
| Long-term historical raw billing data | Data Exports / CUR 2.0 to S3 |
| Cost by team/product/environment | Cost Allocation Tags + Cost Categories |
| Savings recommendations | Cost Optimization Hub |
| Commitment discount management | Savings Plans / Reservations |
| Internal pro-forma billing | Billing Conductor |
AWS Billing Home may not always match the invoice view exactly because some widgets use Cost Explorer-style cost data and can exclude credits/refunds, while Bills/invoices are the final billing view. (AWS Documentation)
2. Home
What is it?
Home is the executive landing page for AWS cost. It gives a quick summary of current cost, forecast, cost trends, recommended actions, savings opportunities, cost monitor, and breakdowns. AWS documents widgets such as Cost summary, Cost monitor, Cost breakdown, Recommended actions, Savings opportunities, and Top trends. (AWS Documentation)
Why use it?
Use it for a quick daily overview:
Are we spending more than last month?
Are we forecasted to exceed normal spend?
Which services or accounts are trending up?
Are there savings opportunities?
Are there budget or anomaly issues?
What you get
| Area | What it gives |
|---|---|
| Cost summary | Current month cost trend and forecast |
| Cost monitor | Budget/anomaly-style financial health |
| Cost breakdown | Spend by important dimensions |
| Recommended actions | Suggested billing/cost tasks |
| Savings opportunities | Optimization opportunities from Cost Optimization Hub |
| Top trends | Biggest positive/negative cost movements |
High-level steps
Billing and Cost Management
→ Home
→ Review current month cost
→ Check forecast
→ Check cost monitor
→ Open Cost Explorer / Budgets / Cost Optimization Hub for details
Practical use
For your setup, Home is good for a daily visual check, but not enough for real FinOps control. Use it as the top page, then investigate in Cost Explorer, Budgets, or Data Exports.
3. Getting Started
What is it?
Getting Started is the onboarding area for setting up AWS Billing and Cost Management features. It helps you configure billing access, payment settings, cost tools, and recommended next steps. AWS’s getting-started guidance covers account setup, IAM users/roles, reviewing bills, and accessing billing features. (AWS Documentation)
Why use it?
Use it when you are setting up a new AWS account or AWS Organization.
What you get
Billing setup checklist
IAM billing-access guidance
Links to Bills, Payments, Cost Explorer, Budgets, Data Exports
Recommended setup actions
High-level steps
Root/admin user
→ Enable IAM access to Billing if required
→ Create IAM roles for billing/cost access
→ Configure payment and tax settings
→ Enable Cost Explorer
→ Create first budget
→ Enable Data Exports if needed
Practical use
In real companies, do not let engineers use the root account for billing. Create IAM roles like:
FinOpsAdmin
BillingAdmin
BillingReadOnly
EngineeringCostViewer
BudgetManager
4. Dashboards — New
What is it?
Dashboards let you create custom pages of billing and cost widgets. AWS describes Billing and Cost Management Dashboards as customizable views of cost and usage data. Dashboards can combine Cost Explorer data, Savings Plans and Reserved Instance coverage/utilization metrics, and Budgets data in one page. (AWS Documentation)
AWS also says dashboards can contain widgets that show costs, usage, Savings Plans/RI coverage and utilization, and budget data. (AWS Documentation)
Why use it?
Use Dashboards when different audiences need different cost views:
| Audience | Dashboard example |
|---|---|
| Leadership | Total AWS cost, forecast, budget health |
| Platform/DevOps | EKS, EC2, NAT Gateway, CloudWatch, RDS cost |
| Engineering managers | Cost by product/team/environment |
| Finance | Account/service/monthly trend |
| FinOps | Unallocated cost, anomalies, savings, commitments |
What you get
Custom cost widgets
Budget widgets
Service/account/region/tag breakdowns
Savings Plans and RI coverage/utilization widgets
Shareable dashboards
Scheduled reports, depending on configuration
High-level steps
Billing and Cost Management
→ Dashboards
→ Create dashboard
→ Add widgets
→ Select Cost Explorer / Budget / Savings / RI data
→ Save
→ Share or schedule
Recommended dashboards for your AWS estate
1. Executive AWS Monthly Cost Dashboard
2. Environment Cost Dashboard: Dev / Stage / UAT / Prod
3. EKS Cost Dashboard
4. NAT Gateway and Data Transfer Dashboard
5. RDS/Aurora Cost Dashboard
6. CloudWatch Logs and Metrics Cost Dashboard
7. Budget Health Dashboard
8. Savings and Commitments Dashboard
5. FinOps Agent — Preview
What is it?
AWS FinOps Agent is a newer preview feature. AWS describes it as a frontier agent that helps customers continuously monitor costs, investigate anomalies, and surface optimization opportunities across cloud environments. It is explicitly marked as preview, which means behavior and availability can change. (AWS Documentation)
Why use it?
Use it when you want natural-language FinOps help:
Why did AWS cost increase this week?
Which account caused the anomaly?
Create a cost report for leadership.
Find optimization opportunities.
Summarize cost by service, account, region, or tag.
Investigate anomalies and create follow-up tasks.
AWS says the FinOps Agent can ask about costs, investigate anomalies, surface optimization recommendations, generate reports, and integrate with workflows such as Jira and Slack. (AWS Documentation)
What you get
Natural-language cost questions
Cost anomaly investigation
Optimization summaries
Report generation
Task/automation workflows
Optional Jira/Slack integration
High-level steps
Open AWS FinOps Agent
→ Create an agent
→ Configure IAM role/permissions
→ Connect data sources/integrations
→ Optionally connect Jira/Slack
→ Ask cost questions or configure automations
AWS notes that the agent acts only on the data sources and integrations you connect during setup. (AWS Documentation)
Practical use
Use it as an assistant, not the source of truth. Your source-of-truth stack should still be:
Bills
Cost Explorer
Budgets
Cost Anomaly Detection
Data Exports / CUR 2.0
Cost Optimization Hub
6. Billing and Payments
This section is for invoice, payment, credit, and procurement management.
6.1 Bills
What is it?
Bills is where you view current charges, previous month bills, invoice details, service-level charges, account-level charges, taxes, credits, refunds, and invoice downloads.
AWS Billing documentation describes the Bills page as the place to download invoices and view detailed monthly billing data to understand how charges were calculated. (Amazon Web Services Documentation)
Why use it?
Use Bills when asking:
What did AWS charge us this month?
What was the final invoice last month?
Which AWS account caused the charge?
Which service caused the charge?
What credits/refunds/taxes were applied?
Can I download the invoice?
What you get
Current month estimated charges
Final historical bills
Invoice PDFs
CSV exports
Charges by service
Charges by account
Credits, discounts, taxes, refunds
High-level steps
Billing and Cost Management
→ Bills
→ Select billing period
→ Review total
→ Expand by service/account
→ Download invoice or CSV
Important note
Bills are best for invoice truth. For trend analysis, use Cost Explorer. For raw line-item analytics, use Data Exports.
6.2 Payments
What is it?
Payments shows outstanding balances, past payments, unapplied funds, and payment history. AWS’s billing documentation describes Payments as the place to understand outstanding or past-due balances and payment history. (Amazon Web Services Documentation)
Why use it?
Use Payments when finance asks:
Have we paid AWS?
Is anything overdue?
What is the payment history?
Which invoice is unpaid?
Which payment method was charged?
What you get
Outstanding balance
Past-due balance
Payment history
Unapplied funds
Receipts / payment records
High-level steps
Billing and Cost Management
→ Payments
→ Review payments due
→ Review payment history
→ Download records if needed
Practical use
DevOps usually only needs read-only access here. Finance owns this area.
6.3 Credits
What is it?
Credits shows AWS credits, remaining balance, expiration, and how credits are applied. AWS documents that credit sharing can be managed in Billing Preferences and describes how credits are applied across single and multiple accounts. (AWS Documentation)
Why use it?
Use Credits for:
AWS startup credits
Migration credits
Promotional credits
Partner credits
Enterprise credits
Training/lab credits
What you get
Credit balance
Credit expiration date
Credit application history
Eligible services
Credit sharing behavior
Remaining credit estimate
High-level steps
Billing and Cost Management
→ Credits
→ Review available credits
→ Check expiry date
→ Check where credits were applied
→ Adjust credit sharing if required
Practical warning
Credits can hide the real AWS run rate. Always track:
Gross cost before credits
Net cost after credits
Credit burn-down rate
Credit expiry risk
6.4 Purchase Orders
What is it?
Purchase Orders lets you configure PO numbers and line items so AWS invoices match your procurement process. AWS says you can manage purchase orders and configure how they reflect on invoices, including multiple purchase orders with multiple line items. (Amazon Web Services Documentation)
Why use it?
Use Purchase Orders when your company needs:
PO number on AWS invoice
Separate PO for AWS Marketplace
Separate PO for support or subscriptions
Separate PO by department/entity
Procurement tracking
What you get
PO number mapping
Line items
PO balance/period
Invoice association
Procurement compliance
High-level steps
Billing and Cost Management
→ Purchase Orders
→ Add purchase order
→ Add line items
→ Define billing period and amount
→ Save
→ Verify on invoice
7. Cost and Usage Analysis
This is where engineering and FinOps spend most of their time.
7.1 Cost Explorer
What is it?
Cost Explorer is AWS’s main interactive tool for analyzing cost and usage. AWS says Cost Explorer helps you visualize, understand, and manage AWS costs and usage over time; it supports historical data, current month data, and forecasting. (AWS Documentation)
AWS also documents that Cost Explorer can show historical data, current month data, and forecasts, and refreshes billing data at least once every 24 hours depending on upstream billing data. (AWS Documentation)
Why use it?
Use Cost Explorer to answer:
Why did AWS cost increase?
Which service is expensive?
Which account is expensive?
Which region is expensive?
What is the current month forecast?
What did NAT Gateway cost?
What did EKS-related compute cost?
How much did CloudWatch Logs cost?
What you get
Cost by service
Cost by account
Cost by region
Cost by usage type
Cost by tag
Cost by cost category
Daily/monthly trends
Forecast
CSV export
High-level steps
Billing and Cost Management
→ Cost Explorer
→ Choose date range
→ Choose granularity: daily/monthly
→ Group by service/account/region/tag/category
→ Apply filters
→ Save report if useful
Practical reports for you
Monthly cost by linked account
Monthly cost by service
Daily cost by service
Cost by region: ap-northeast-1 / Tokyo
Cost by Environment tag
NAT Gateway cost trend
CloudWatch Logs cost trend
RDS/Aurora cost trend
EC2/EKS compute cost trend
Data transfer cost trend
7.2 Cost Explorer Saved Reports
What is it?
Saved Reports are reusable Cost Explorer views. Instead of rebuilding the same filter/grouping every week, you save the report.
Why use it?
Use Saved Reports for recurring analysis:
EKS monthly cost
Prod account daily cost
Tokyo region cost
NAT Gateway by account
CloudWatch Logs by account
RDS cost by environment
What you get
Reusable Cost Explorer views
Standardized reports
Faster monthly review
Consistent FinOps reporting
High-level steps
Cost Explorer
→ Build report
→ Apply date range, filters, group-by
→ Save as report
→ Open later from Saved Reports
Recommended naming
CE - Monthly Cost by Account
CE - Monthly Cost by Service
CE - Tokyo Region Cost
CE - NAT Gateway Daily Trend
CE - CloudWatch Logs Trend
CE - EKS Compute by Environment
7.3 Cost Anomaly Detection
What is it?
Cost Anomaly Detection detects unusual spending patterns using cost monitors and alert subscriptions. AWS says you configure cost monitors and alert subscriptions, and monitor types can include AWS services, linked accounts, cost allocation tags, and cost categories. (AWS Documentation)
Why use it?
Budgets answer:
Did we cross a planned limit?
Cost Anomaly Detection answers:
Is today’s spend abnormal compared to usual behavior?
Use it for:
Unexpected NAT Gateway spike
CloudWatch log ingestion explosion
RDS backup/storage growth
EC2/EKS runaway workload
Data transfer spike
New expensive AWS service usage
What you get
Anomaly dashboard
Root-cause dimensions
Impact estimate
Account/service/region clues
Email/SNS/User Notification alerts
High-level steps
Billing and Cost Management
→ Cost Anomaly Detection
→ Create cost monitor
→ Choose monitor type
→ Create alert subscription
→ Set threshold and recipients
→ Review anomalies regularly
Recommended monitors
1. AWS services monitor
2. Linked account monitor
3. Environment tag monitor
4. Product/team cost category monitor
5. High-risk services: NAT Gateway, CloudWatch, EC2, RDS, Data Transfer
7.4 Free Tier
What is it?
Free Tier tracks usage against AWS Free Tier limits. AWS Free Tier is mainly relevant for new, sandbox, training, or personal accounts.
Why use it?
Use it for:
Training accounts
Student labs
New AWS accounts
Sandbox experiments
What you get
Free Tier usage
Usage warnings
Service-level free-tier consumption
Credit/free-plan status depending on account type
High-level steps
Billing and Cost Management
→ Free Tier
→ Review usage
→ Enable Free Tier alerts if relevant
→ Create zero-spend budget for extra protection
Practical use
For serious company workloads, Free Tier is not enough. Use Budgets and Cost Anomaly Detection.
7.5 Data Exports
What is it?
Data Exports is the modern AWS export system for cost and billing datasets. AWS says Data Exports lets you create exports of billing and cost management data, including cost and usage and cost optimization recommendations. (AWS Documentation)
AWS also says Data Exports can create three types of exports: standard exports, cost and usage dashboard exports, and legacy exports. (AWS Documentation)
Why use it?
Use Data Exports when you need durable historical cost data:
Long-term FinOps warehouse
Athena SQL analysis
QuickSight dashboards
Datadog Cloud Cost Management
Chargeback/showback
Cost by team/product/environment
Kubernetes/EKS cost analysis
Detailed historical reporting
What you get
CUR 2.0 / cost and usage data
FOCUS-style datasets where available
Cost optimization recommendation exports
Carbon emissions exports
S3 delivery
Athena/BI integration
AWS describes Data Exports as a way to create recurring exports to S3 and customize columns/rows/schema using SQL-like selections. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Data Exports
→ Create export
→ Choose export type
→ Select columns/filter
→ Choose S3 bucket
→ Configure delivery
→ Query with Athena or ingest into BI/Datadog
Practical architecture
Management account
→ Data Exports / CUR 2.0
→ S3 billing bucket
→ Athena table
→ QuickSight / Datadog Cloud Cost Management / custom reports
Important
This is your best historical source of truth. Cost Explorer is great for interactive analysis, but Data Exports is better for long-term reporting and automation.
7.6 Carbon emissions
What is it?
Carbon emissions shows AWS carbon footprint estimates for sustainability reporting. AWS’s Customer Carbon Footprint Tool reports estimated AWS emissions and supports service/region breakdowns and exports. (AWS Documentation)
Why use it?
Use it for:
ESG reporting
Sustainability reporting
Carbon-aware architecture discussions
Region/service footprint analysis
What you get
Estimated emissions
Emissions by region
Emissions by service
Historical carbon trend
CSV/export options
High-level steps
Billing and Cost Management
→ Carbon emissions
→ Review summary
→ Filter by time/service/region
→ Export data if needed
8. Cost Organization
This section is about ownership: who should be accountable for which cost?
8.1 Cost Categories
What is it?
Cost Categories lets you map AWS costs to your internal business structure using rules. AWS says Cost Categories help map AWS costs to your unique internal business structures by grouping costs into meaningful categories. (AWS Documentation)
Why use it?
Use Cost Categories when accounts and tags are not enough.
Examples:
Account 111 + Account 222 = Platform
Tag Product=Analytics = Analytics product
Service=NATGateway + account=shared = Shared Network
Untagged shared infra = Platform Shared
What you get
Business-unit cost views
Team/product/environment grouping
Shared-cost allocation
Cost Explorer grouping/filtering
Budget scopes
CUR/Data Export dimensions
Anomaly monitor scopes
High-level steps
Billing and Cost Management
→ Cost Categories
→ Create category
→ Define category values
→ Add rules using accounts, services, tags, charge types, etc.
→ Add split-charge rules if needed
→ Use in Cost Explorer/Budgets/Data Exports
Recommended categories for your environment
Environment = dev / stage / uat / prod / shared
Product = backend / analytics / design / platform
Owner = team name
CostCenter = finance code
Criticality = production / non-production
8.2 Cost Allocation Tags
What is it?
Cost Allocation Tags are AWS resource tags that you activate for billing. AWS says after tags are applied to resources and activated in Billing and Cost Management, AWS can generate cost allocation reports grouped by active tags. (AWS Documentation)
Why use it?
Use tags to answer:
How much does prod cost?
How much does each product cost?
Which team owns this resource?
How much is untagged?
Which app caused the bill?
What you get
Cost Explorer group/filter by tag
Budgets by tag
Data Export/CUR tag columns
Cost allocation reports
Untagged cost governance
High-level steps
Tag resources
→ Billing and Cost Management
→ Cost Allocation Tags
→ Activate tag keys
→ Wait for billing data processing
→ Use tags in Cost Explorer, Budgets, Data Exports
Recommended mandatory tags
Environment
Product
Service
Team
Owner
CostCenter
ManagedBy
Repository
Application
Practical warning
Tags must be activated for cost allocation. Merely tagging resources is not enough for billing reports.
8.3 Billing Conductor
What is it?
AWS Billing Conductor creates a separate pro forma billing view for internal chargeback/showback. AWS says Billing Conductor configurations do not affect actual AWS invoices or existing billing configuration; they let you model costs for customer agreements or internal accounting practices. (AWS Documentation)
Why use it?
Use Billing Conductor for advanced cases:
Internal chargeback
Partner/reseller billing
Custom internal rates
Custom pricing rules
Shared-service allocation
Multiple customer/business-unit billing
What you get
Billing groups
Pricing plans
Pricing rules
Custom line items
Pro forma cost and usage data
Internal bill-like views
High-level steps
Billing Conductor
→ Create billing group
→ Add accounts
→ Create pricing plan
→ Add pricing rules/custom line items
→ Assign pricing plan
→ Review pro forma billing data
Practical use
Most platform teams do not need this initially. Start with Cost Allocation Tags and Cost Categories. Add Billing Conductor only when finance needs formal internal billing views.
9. Budgets and Planning
This is where your billing-alert requirement belongs.
9.1 Budgets — New
What is it?
AWS Budgets tracks cost, usage, RI utilization/coverage, and Savings Plans utilization/coverage. AWS says Budgets can track and take action on AWS costs and usage, and can also monitor Reserved Instance and Savings Plans utilization and coverage metrics. (AWS Documentation)
Why use it?
Use Budgets for planned financial limits:
Actual cost > 80%
Actual cost > 100%
Forecasted cost > 100%
Dev account exceeds budget
Prod forecast exceeds budget
NAT Gateway monthly spend exceeds threshold
CloudWatch Logs spend exceeds threshold
Savings Plan utilization drops below target
What you get
Cost budgets
Usage budgets
RI utilization budgets
RI coverage budgets
Savings Plans utilization budgets
Savings Plans coverage budgets
Actual alerts
Forecasted alerts
Email/SNS notifications
Budget actions where configured
High-level steps
Billing and Cost Management
→ Budgets
→ Create budget
→ Choose cost budget
→ Set monthly amount
→ Scope by account/service/tag/category if needed
→ Add actual and forecast thresholds
→ Add email/SNS recipients
→ Save
Your example
Budget name: monthly-aws-total-cost-2000
Budget amount: USD 2,000
Period: Monthly
Alert 1: Actual > 80% = USD 1,600
Alert 2: Actual > 100% = USD 2,000
Alert 3: Forecasted > 100% = projected monthly cost > USD 2,000
Practical recommendation
For you:
Create the main budget in the management/payer account.
Use AWS Budgets as the official alerting source.
Route notifications to SNS + email.
Optionally forward SNS to Slack/Datadog later.
AWS Budgets also supports billing views, allowing budgets to be created from filtered cost and usage data across multiple accounts without giving everyone direct management-account access. (AWS Documentation)
9.2 Budgets Reports
What is it?
Budgets Reports send scheduled budget status reports. They are useful for weekly/monthly governance.
Why use it?
Use Budgets Reports for:
Weekly FinOps email
Monthly engineering budget review
Leadership budget summary
Environment budget health report
What you get
Scheduled reports
Budget actual vs planned
Forecast vs budget
Email distribution
High-level steps
Billing and Cost Management
→ Budgets Reports
→ Create report
→ Select budgets
→ Choose frequency
→ Add recipients
→ Save
Recommended report
Name: Weekly AWS Budget Health
Frequency: Weekly
Recipients: DevOps, FinOps, Engineering leads
Budgets: Global + per-environment + high-risk service budgets
9.3 Pricing Calculator — New
What is it?
Pricing Calculator estimates future AWS cost. AWS’s in-console Pricing Calculator can estimate planned cloud costs using actual AWS pricing context, discounts, and commitments where applicable. (AWS Documentation)
Why use it?
Use it before deploying or changing architecture:
New EKS cluster
More NAT Gateways
New RDS/Aurora database
More CloudWatch ingestion
New OpenSearch cluster
Cross-region replication
PrivateLink design
Savings Plan purchase planning
What you get
Workload estimate
Bill estimate
Monthly projected cost
Resource-level cost model
Commitment impact analysis
High-level steps
Billing and Cost Management
→ Pricing Calculator
→ Create estimate
→ Add AWS services/resources
→ Configure region/usage
→ Include commitments/discounts if available
→ Save/export estimate
Practical use
Before approving architecture, require a calculator estimate for anything likely to add recurring cost:
NAT Gateway
EKS node capacity
RDS/Aurora
OpenSearch
CloudWatch Logs
Data transfer
10. Savings and Commitments
This section is for optimization and commitment management.
10.1 Cost Optimization Hub — New
What is it?
Cost Optimization Hub consolidates AWS savings recommendations across accounts and regions. AWS says it helps identify, filter, and aggregate recommendations for rightsizing, idle resource deletion, Savings Plans, and Reserved Instances from a single dashboard. (AWS Documentation)
AWS also notes that viewing opportunities in other accounts requires management-account access and opting in member accounts. (AWS Documentation)
Why use it?
Use it to find savings:
Idle resources
Underutilized resources
Rightsizing opportunities
Savings Plans opportunities
Reserved Instance opportunities
Resource cleanup opportunities
What you get
Estimated monthly savings
Recommendations by account
Recommendations by region
Recommendations by resource type
Deduplicated savings opportunities
Prioritized optimization backlog
High-level steps
Billing and Cost Management
→ Cost Optimization Hub
→ Opt in
→ Include member accounts if using AWS Organizations
→ Review dashboard
→ Filter by account/region/resource type
→ Assign owners
→ Track implementation
Weekly practice
Every Monday:
Review top 10 savings opportunities
Validate risk
Assign owner
Implement safe actions
Track realized savings
11. Savings Plans
Savings Plans are commitment-based discounts for eligible compute usage. They are generally more flexible than classic EC2 Reserved Instances for many compute workloads.
11.1 Savings Plans — Overview
What is it?
The landing page for your Savings Plans posture.
Why use it?
Use it to answer:
Do we own Savings Plans?
Are they saving money?
Are they expiring?
Are we using our commitment fully?
Do we need more coverage?
What you get
Savings summary
Utilization summary
Coverage summary
Inventory entry point
Recommendations entry point
High-level steps
Billing and Cost Management
→ Savings Plans
→ Overview
→ Review utilization, coverage, and savings
11.2 Savings Plans — Inventory
What is it?
Inventory shows active and queued Savings Plans. AWS says the Inventory page gives a detailed overview of Savings Plans you own or have queued, and management accounts can view account or organization inventory. (AWS Documentation)
Why use it?
Use it for:
Active plan tracking
Queued plan tracking
Expiration review
Commitment amount review
Plan ownership
What you get
Plan type
Commitment amount
Start/end date
Payment option
Status
Owning account
High-level steps
Savings Plans
→ Inventory
→ Choose account or organization view
→ Review active and queued plans
→ Export if needed
11.3 Savings Plans — Recommendations
What is it?
Recommendations suggest Savings Plans purchases based on eligible historical usage.
Why use it?
Use it when compute spend is stable and predictable.
What you get
Recommended hourly commitment
Estimated savings
Coverage impact
Utilization impact
Lookback-based analysis
High-level steps
Savings Plans
→ Recommendations
→ Choose lookback period
→ Review recommended commitment
→ Validate roadmap
→ Analyze with Purchase Analyzer
Practical warning
Do not blindly buy recommendations. Check:
Are workloads stable?
Will migration reduce usage?
Will instance families or compute types change?
Are we moving from EC2 to Fargate/serverless?
Is production baseline predictable?
11.4 Savings Plans — Purchase Analyzer — New
What is it?
Purchase Analyzer models potential Savings Plans purchases. AWS says it lets you model purchases using a recommended amount, target coverage percentage, or custom amount, and compare impact on savings, coverage, and utilization. (AWS Documentation)
Why use it?
Use it before committing money.
What you get
Estimated monthly savings
Coverage projection
Utilization projection
Scenario comparison
Risk visibility
High-level steps
Savings Plans
→ Purchase Analyzer
→ Select recommended / target coverage / custom amount
→ Adjust lookback
→ Compare scenarios
→ Prepare approval
11.5 Savings Plans — Utilization Report
What is it?
Utilization shows whether you are actually consuming the Savings Plans commitment you bought.
Why use it?
Use it to detect wasted commitment.
What you get
Utilization percentage
Unused commitment
Net savings
On-Demand equivalent spend
Account/service breakdown
High-level steps
Savings Plans
→ Utilization Report
→ Select time range
→ Review utilization %
→ Investigate unused commitment
Interpretation
High utilization = you are using what you bought
Low utilization = you overcommitted or usage moved/dropped
11.6 Savings Plans — Coverage Report
What is it?
Coverage shows how much eligible usage is covered by Savings Plans.
Why use it?
Use it to find On-Demand compute spend that could be discounted.
What you get
Coverage %
Covered spend
Uncovered eligible spend
Service/account/region breakdown
High-level steps
Savings Plans
→ Coverage Report
→ Select period
→ Group by service/account/region
→ Identify uncovered eligible spend
→ Review recommendations
Interpretation
High utilization + low coverage = existing plans are used well, but you may need more.
Low utilization + high coverage = you may be overcommitted.
11.7 Purchase Savings Plans
What is it?
This is where Savings Plans are purchased.
Why use it?
Use it only after recommendation review, Purchase Analyzer modeling, and approval.
What you get
Plan type
Commitment amount
Term
Payment option
Start date
Cart checkout
High-level steps
Savings Plans
→ Purchase Savings Plans
→ Choose plan
→ Add to cart
→ Review
→ Purchase
11.8 Cart
What is it?
The cart holds pending Savings Plans purchases. If it shows 0, there are no pending purchases.
Why use it?
Use it as final review before commitment.
What you get
Pending purchase summary
Commitment details
Term/payment review
Final purchase confirmation
Practical governance
Treat this as a financial approval point. Savings Plans are not casual engineering changes.
12. Reservations
Reservations are another type of commitment discount, often used for services such as RDS, Redshift, ElastiCache, OpenSearch, and sometimes EC2. Cost Explorer supports reservation overview, utilization, coverage, and recommendations. (AWS Documentation)
12.1 Reservations — Overview
What is it?
A summary of reservation ownership, savings, utilization, and expirations.
Why use it?
Use it to answer:
Which reservations do we own?
Are they saving money?
Are any expiring?
Are they being used?
What you get
Reservation inventory summary
Savings summary
Expiration alerts
Utilization/coverage entry points
High-level steps
Billing and Cost Management
→ Reservations
→ Overview
→ Review owned reservations
→ Check savings and expiration
12.2 Reservations — Recommendations — New
What is it?
Reservation recommendations suggest RI purchases based on historical usage. AWS says RI recommendations are based on historical On-Demand usage, such as 7, 30, or 60 day lookback periods, and are refreshed regularly. (AWS Documentation)
Why use it?
Use it for stable services like:
RDS
Redshift
ElastiCache
OpenSearch
Stable EC2 workloads
What you get
Recommended reservation purchases
Estimated monthly savings
Lookback-based model
Term/payment options
High-level steps
Reservations
→ Recommendations
→ Choose service
→ Choose lookback/term/payment
→ Review savings
→ Validate workload stability
→ Purchase via service-specific path
12.3 Reservations — Utilization Report
What is it?
Shows how much of your purchased reserved capacity is being used.
Why use it?
Use it to detect wasted reservations.
What you get
Utilization %
Unused reserved hours/capacity
Savings impact
Account/service/region breakdown
High-level steps
Reservations
→ Utilization Report
→ Select time range
→ Review low-utilization items
→ Investigate workload movement or overcommitment
12.4 Reservations — Coverage Report
What is it?
Shows how much eligible usage is covered by reservations.
Why use it?
Use it to identify stable On-Demand usage that could be discounted.
What you get
Coverage %
Uncovered usage
Covered usage
Potential reservation opportunity
High-level steps
Reservations
→ Coverage Report
→ Select period
→ Group by account/service/region
→ Identify uncovered stable workloads
→ Review recommendations
13. Preferences and Settings
This section controls billing behavior, payment methods, visibility, tax, invoice configuration, and billing transfer.
13.1 Payment Preferences
What is it?
Payment Preferences manages payment methods, default payment method, payment currency, payment profiles, and billing contacts. AWS billing documentation describes payment profiles as a way to set up multiple payment methods for different AWS service providers or parts of your organization. (Amazon Web Services Documentation)
Why use it?
Use it for:
Credit card / bank payment method
Default payment method
Payment currency
Billing contacts
Payment profiles
Seller-of-record handling
What you get
Payment method configuration
Default payment method
Payment profiles
Billing contact setup
High-level steps
Billing and Cost Management
→ Payment Preferences
→ Add/update payment method
→ Set default method
→ Configure payment profile if needed
13.2 Billing Preferences
What is it?
Billing Preferences controls invoice delivery, alerts, credit sharing, RI/Savings Plans discount sharing, and legacy detailed billing reports. AWS says some sections can only be updated by the payer account. (AWS Documentation)
Why use it?
Use it for:
PDF invoice email delivery
CloudWatch billing alerts
Free Tier alerts
Credit sharing across accounts
RI/Savings Plans discount sharing
Legacy detailed billing settings
What you get
Invoice delivery settings
Alert preferences
Credit sharing settings
Discount sharing settings
Legacy report options
High-level steps
Billing and Cost Management
→ Billing Preferences
→ Configure invoice delivery
→ Configure alert preferences
→ Configure credit sharing
→ Configure RI/SP discount sharing
Practical note
This is where CloudWatch billing alerts may need to be enabled, but for your real cost alerts, AWS Budgets is still better.
13.3 Cost Management Preferences — New
What is it?
Cost Management Preferences controls cost-management data visibility and optimization preferences. This is especially relevant in AWS Organizations.
Why use it?
Use it for:
Member account Cost Explorer visibility
Cost Optimization Hub opt-in
Cost data sharing preferences
Granularity/preferences for cost management features
What you get
Linked account access behavior
Optimization visibility
Cost-management feature preferences
High-level steps
Management account
→ Billing and Cost Management
→ Cost Management Preferences
→ Configure member-account access
→ Configure optimization preferences
→ Save
Practical use
For engineering ownership, allow teams to see their own cost. Hidden cost creates poor accountability.
13.4 Tax Settings
What is it?
Tax Settings manages tax registration, tax inheritance, and exemptions.
Why use it?
Use it for:
VAT/GST/JCT registration
Tax exemption
Legal entity compliance
Tax inheritance across AWS Organizations
What you get
Tax registration numbers
Tax exemption status
Organization tax inheritance
Country/region-specific tax setup
High-level steps
Billing and Cost Management
→ Tax Settings
→ Add tax registration
→ Configure inheritance if needed
→ Upload exemption documents if applicable
Practical use
Finance/accounting owns this. DevOps should not casually modify it.
13.5 Invoice Configuration
What is it?
Invoice Configuration lets you customize invoice units and invoice preferences. AWS documents invoice configuration as a way to customize invoice preferences, including billing transfer use cases where different tax settings and seller-of-record mappings may be needed. (AWS Documentation)
Why use it?
Use it for:
Separate invoices by business unit
Separate invoice receivers
Different legal/tax handling
PO alignment
Billing transfer invoice customization
What you get
Invoice units
Invoice receiver mapping
Account grouping for invoices
Tax/SOR handling for transferred billing
High-level steps
Billing and Cost Management
→ Invoice Configuration
→ Create invoice unit
→ Add accounts or billing scope
→ Configure invoice receiver/settings
→ Save
Practical use
Not required for simple AWS setups. Very useful for large enterprises or billing-transfer models.
13.6 Billing Transfer — New
What is it?
Billing Transfer lets one AWS account centrally manage and pay bills across multiple AWS Organizations while the source organizations keep their own security and governance autonomy. AWS’s announcement describes Billing Transfer as a way to centrally manage and pay bills across multiple AWS organizations. (Amazon Web Services, Inc.)
AWS documentation says billing transfer starts when a bill-transfer account sends an invitation to a management account, and the bill-transfer account then manages and pays the bill-source account’s consolidated bill from the selected effective date. (AWS Documentation)
Why use it?
Use it for:
Central billing across multiple AWS Organizations
Partner/reseller billing
Enterprise central finance model
Separating security governance from billing ownership
What you get
Centralized billing responsibility
Transferred invoices
Billing views
Integration with Billing Conductor for chargeback/showback
High-level steps
Bill-transfer account
→ Send billing transfer invitation
→ Bill-source management account accepts
→ Effective date starts billing transfer
→ Configure billing views/invoice configuration if needed
Practical warning
This is advanced enterprise billing. Do not use it unless finance/legal/procurement specifically needs centralized billing across multiple AWS Organizations.
14. Correct setup for your AWS billing alerts
For your immediate requirement:
Actual cost > 80% of USD 2,000
Actual cost > 100% of USD 2,000
Forecast cost > 100% of USD 2,000
Use:
Primary: AWS Budgets
Notification routing: SNS + email
Visibility: Cost Explorer / Dashboards / Datadog if integrated
Historical source: Data Exports / CUR 2.0 in S3
Optional backup: CloudWatch billing alarm
Do not make CloudWatch the main solution. CloudWatch billing metrics are basic estimated-charge metrics. AWS Budgets is the correct tool because it supports actual and forecasted budget notifications. (AWS Documentation)
Recommended design:
AWS Management / Payer Account
│
├── Budget: monthly-aws-total-cost-2000
│ ├── Actual > 80%
│ ├── Actual > 100%
│ └── Forecasted > 100%
│
├── SNS Topic: aws-budget-alerts
│ ├── Email distribution list
│ ├── Slack integration, optional
│ └── Datadog event integration, optional
│
├── Cost Explorer Saved Reports
│ ├── Monthly cost by account
│ ├── Monthly cost by service
│ └── Tokyo region cost
│
└── Data Exports / CUR 2.0
└── S3 bucket → Athena / BI / Datadog Cloud Cost Management
15. Best-practice implementation order
Phase 1 — Billing foundation
1. Confirm management/payer account.
2. Enable IAM access to Billing if required.
3. Create FinOps/Billing IAM roles.
4. Configure Payment Preferences.
5. Configure Billing Preferences.
6. Configure Tax Settings.
Phase 2 — Visibility
7. Enable/use Cost Explorer.
8. Create Cost Explorer Saved Reports.
9. Create Dashboards.
10. Enable Data Exports / CUR 2.0 to S3.
11. Query with Athena or integrate with Datadog Cloud Cost Management.
Phase 3 — Allocation
12. Define mandatory tags.
13. Activate Cost Allocation Tags.
14. Create Cost Categories.
15. Build dashboards by environment/product/team.
Phase 4 — Governance
16. Create monthly global AWS Budget.
17. Create environment-specific budgets.
18. Create high-risk service budgets.
19. Enable Cost Anomaly Detection.
20. Route alerts through SNS/email/Slack.
21. Create Budgets Reports.
Phase 5 — Optimization
22. Enable Cost Optimization Hub.
23. Review savings weekly.
24. Review Savings Plans utilization and coverage.
25. Review Reservations utilization and coverage.
26. Use Pricing Calculator before major changes.
16. Practical AWS FinOps operating model
Daily
Check Home
Check Cost Anomaly Detection
Check budget alerts
Check unexpected service/account spikes
Weekly
Review Cost Explorer trends
Review top cost drivers
Review Cost Optimization Hub
Review untagged cost
Send Budget Report
Monthly
Review Bills
Compare actual vs budget
Review credits
Review Savings Plans utilization/coverage
Review Reservations utilization/coverage
Review Data Export/Athena reports
Quarterly
Review commitment strategy
Review tagging compliance
Review Cost Categories
Review showback/chargeback process
Review forecast accuracy
Review large architecture cost drivers
17. Final cheat sheet
| Console option | Best used for |
|---|---|
| Home | Fast cost health overview |
| Getting Started | Initial billing/cost setup |
| Dashboards | Custom cost and budget dashboards |
| FinOps Agent | AI-assisted FinOps investigation, preview only |
| Bills | Invoice and final billing details |
| Payments | Payment status and history |
| Credits | Credit balance, expiry, application |
| Purchase Orders | PO mapping to invoices |
| Cost Explorer | Interactive cost investigation |
| Cost Explorer Saved Reports | Reusable cost reports |
| Cost Anomaly Detection | Unusual spend detection |
| Free Tier | Free-tier tracking for new/sandbox accounts |
| Data Exports | Long-term historical cost data in S3 |
| Carbon emissions | Sustainability/carbon reporting |
| Cost Categories | Business-level cost grouping |
| Cost Allocation Tags | Resource/team/product/environment cost allocation |
| Billing Conductor | Pro forma billing, chargeback/showback |
| Budgets | Budget alerts and cost guardrails |
| Budgets Reports | Scheduled budget status emails |
| Pricing Calculator | Forecasting planned workload cost |
| Cost Optimization Hub | Savings opportunities |
| Savings Plans Overview | Commitment health summary |
| Savings Plans Inventory | Active/queued Savings Plans |
| Savings Plans Recommendations | Suggested commitment purchases |
| Purchase Analyzer | Model Savings Plans purchase scenarios |
| SP Utilization Report | Are we using what we bought? |
| SP Coverage Report | How much eligible usage is covered? |
| Purchase Savings Plans | Buy Savings Plans |
| Cart | Review pending Savings Plans purchases |
| Reservations Overview | RI ownership and health |
| Reservations Recommendations | Suggested RI purchases |
| RI Utilization Report | Are reservations being used? |
| RI Coverage Report | How much eligible usage is reserved? |
| Payment Preferences | Payment methods and payment profiles |
| Billing Preferences | Invoice delivery, alerts, credit/discount sharing |
| Cost Management Preferences | Cost visibility and optimization preferences |
| Tax Settings | Tax registrations and exemptions |
| Invoice Configuration | Invoice unit customization |
| Billing Transfer | Central billing across multiple AWS Organizations |
For your immediate next step, I would start with Budgets, Cost Explorer Saved Reports, and Data Exports. Those three give you alerting, investigation, and historical truth.