Below is a master guide to AWS Billing and Cost Management, written like a complete FinOps tutorial. I’ll map every menu item you listed and explain:
What is it?
Why use it?
What do you get from it?
High-level steps to use it?
Where it fits in a real FinOps workflow?
Master Guide: AWS Billing and Cost Management
AWS Billing and Cost Management is the financial control center for AWS. It helps you pay bills, view invoices, analyze cost, organize spend, create budgets, detect anomalies, plan future workloads, and optimize commitments. AWS groups the console into major areas: billing and payments, cost analysis, cost organization, budgeting and planning, savings and commitments, and preferences/settings. (AWS Documentation)
For a multi-account company setup, the most important concept is this:
AWS member accounts generate usage
↓
AWS billing system calculates cost
↓
Management / payer account receives consolidated billing
↓
Cost Explorer, Bills, Budgets, Data Exports, Cost Categories, Tags, and Optimization tools analyze that data
If you use AWS Organizations, the management account pays the charges of member accounts and can consolidate billing across them. That is usually where company-level FinOps controls should be configured. (AWS Documentation)
1. Mental model: how AWS cost data flows
AWS Services
EC2, EKS, RDS, NAT Gateway, S3, CloudWatch, ALB, Route 53, etc.
↓
AWS usage and billing pipeline
↓
Billing and Cost Management data layer
↓
Bills / Payments / Credits
Cost Explorer
Budgets
Cost Anomaly Detection
Data Exports / CUR 2.0
Cost Categories / Tags
Cost Optimization Hub
Savings Plans / Reservations
↓
Finance, DevOps, FinOps, Engineering, Leadership dashboards
There are three practical layers:
| Layer | Purpose | Main AWS tools |
|---|---|---|
| Billing truth | What AWS invoices you for | Bills, Payments, Credits, Purchase Orders |
| Cost analysis | Why cost changed and who caused it | Cost Explorer, Data Exports, Dashboards, Cost Anomaly Detection |
| Cost control and optimization | Prevent overspend and reduce waste | Budgets, Cost Optimization Hub, Savings Plans, Reservations |
A very important detail: Billing page data and Cost Explorer data can differ. AWS says the Billing and Cost Management home page uses Cost Explorer data, refreshes at least every 24 hours when available, and may differ from invoices/Bills because of grouping, credits, refunds, taxes, timing, and rounding. (AWS Documentation)
So for investigation:
Invoice/payment issue → Bills / Payments
Trend or service analysis → Cost Explorer
Long-term detailed history → Data Exports / CUR 2.0 in S3
Alerting → AWS Budgets + Cost Anomaly Detection
Savings → Cost Optimization Hub + Savings Plans + Reservations
2. Home
What is it?
Home is the landing page of Billing and Cost Management. It gives a high-level view of your AWS financial position: current cost, forecasted cost, trends, anomalies, recommended actions, cost allocation coverage, and savings opportunities. AWS says the home page is designed to help you understand high-level cost trends, drivers, anomalies, budget overruns, recommended actions, allocation coverage, and savings opportunities. (AWS Documentation)
Why use it?
Use it when you want a quick answer to:
Are we spending more than usual?
Which services are driving cost?
Are we forecasted to exceed budget?
Do we have unallocated cost?
Are there saving opportunities?
What you get
| Widget / area | What it gives you |
|---|---|
| Cost summary | Month-to-date cost, last month comparison, forecasted monthly cost |
| Cost monitor | Anomalies, budget overruns, high-priority cost issues |
| Cost breakdown | Cost by service, account, region, or other useful views |
| Recommended actions | Budget, tax, payment, optimization, anomaly, and IAM-related action items |
| Cost allocation coverage | How much cost is properly mapped to tags/categories |
| Savings opportunities | Savings recommendations |
| Top trends | Services/accounts/regions trending up or down |
High-level steps
Billing and Cost Management
→ Home
→ Review cost summary
→ Review cost monitor
→ Check recommended actions
→ Click into Cost Explorer / Budgets / Cost Optimization Hub for details
FinOps advice
For your AWS environments, Home is good for a daily 2-minute check, but it is not enough for governance. Use it as the executive overview, not the source of detailed historical truth.
3. Getting Started
What is it?
Getting Started is the onboarding area that helps you set up Billing and Cost Management properly. AWS’s setup guidance includes signing up for AWS, setting up IAM users/roles, reviewing bills, enabling billing access, configuring tax/payment/billing preferences, and learning cost-management features. (AWS Documentation)
Why use it?
Use it when setting up a new AWS account, new AWS Organization, or new FinOps process.
What you get
| Area | Why it matters |
|---|---|
| IAM billing access | Lets IAM roles/users access billing console |
| Bills review | Lets you verify monthly AWS charges |
| Payment setup | Ensures AWS invoices can be paid |
| Tax setup | Keeps tax registration/exemption data correct |
| Cost Management setup | Enables budgets, forecasts, reports, and cost visibility |
By default, AWS says IAM roles/users cannot access the Billing and Cost Management console unless the root user activates IAM access. (AWS Documentation)
High-level steps
Root / authorized admin
→ Account page
→ Activate IAM access to Billing
→ Assign billing/cost IAM permissions
→ Open Billing and Cost Management
→ Review Bills
→ Review Payments
→ Enable Cost Explorer
→ Configure budgets and reports
FinOps advice
Do not give broad billing access to everyone. Create IAM roles such as:
BillingAdmin
FinOpsAdmin
FinOpsReadOnly
EngineeringCostViewer
BudgetManager
4. Dashboards
What is it?
Dashboards are custom cost and usage pages made from widgets. AWS says Billing and Cost Management Dashboards let you create and share customized views of cost and usage data in one page, combining Cost Explorer data with Savings Plans, RI coverage/utilization metrics, and Budgets. (AWS Documentation)
Why use it?
Use Dashboards when different stakeholders need different views:
Leadership → total monthly cost, forecast, trend
Platform team → EKS, EC2, NAT Gateway, RDS, CloudWatch
Finance → monthly cost by account and service
Engineering managers → cost by product/team/environment
What you get
| Dashboard capability | Value |
|---|---|
| Custom widgets | Build views by service, account, region, tag, budget |
| Budget widgets | Compare actual/forecast spend against budget |
| RI/Savings Plan widgets | Track commitment utilization and coverage |
| Sharing | Share securely inside/outside organization |
| PDF export | Offline reporting |
| Scheduled email delivery | Daily/weekly/monthly reporting |
AWS documents that dashboards can be exported as PDF and scheduled for email delivery. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Dashboards
→ Create dashboard
→ Add widgets
→ Select Cost Explorer / Budgets / RI / Savings Plans data
→ Save
→ Share or schedule email report
FinOps advice
Create at least these dashboards:
Executive AWS Cost Dashboard
Environment Cost Dashboard
EKS Cost Dashboard
Top Cost Drivers Dashboard
Commitment Utilization Dashboard
Budget Health Dashboard
5. FinOps Agent — Preview
What is it?
AWS FinOps Agent is a preview AWS feature that helps users investigate costs, monitor anomalies, generate financial reports, and surface optimization opportunities using natural-language workflows. AWS explicitly says the FinOps Agent is in preview and subject to change. (AWS Documentation)
Why use it?
Use it when you want AI-assisted FinOps workflows:
Why did cost increase yesterday?
Which account caused the anomaly?
Create a monthly AWS cost report.
Generate a PPT for leadership.
Summarize cost by service/account/region/tag.
Create Jira tickets for cost anomalies.
Post investigation summaries to Slack.
AWS says the agent can create HTML, PDF, and PPT reports with cost summaries, service/account/region/tag breakdowns, trend analysis, month-over-month comparisons, and forecast projections. (AWS Documentation)
What you get
| Feature | Output |
|---|---|
| Natural-language cost inquiry | Answers based on Cost Explorer/anomaly data |
| Cost reports | HTML, PDF, PPT |
| Anomaly investigation | Consolidated investigation summaries |
| Jira/Slack integration | Tickets and notifications |
| Context upload | Account-owner mapping and org rules |
High-level steps
Switch to us-east-1
→ Open AWS FinOps Agent console
→ Create agent
→ Let wizard create IAM roles/policies
→ Optionally connect Slack/Jira
→ Upload account-owner mapping and org context
→ Ask cost questions or create scheduled tasks
FinOps advice
Because it is preview, use it as an assistant, not the only control system. Keep AWS Budgets, Cost Anomaly Detection, Data Exports, and dashboards as your official governance layer.
6. Billing and Payments
This section answers:
What did AWS charge us?
Have we paid?
Do we have credits?
Which PO appears on the invoice?
6.1 Bills
What is it?
Bills is the invoice and charge detail page. It shows estimated current-month charges and final charges for previous months. AWS says you receive monthly invoices for usage charges and recurring fees, and you can view estimated current charges and final charges for previous months. (AWS Documentation)
Why use it?
Use Bills when finance or engineering asks:
What did AWS invoice us?
Which service caused the charge?
Which account generated the charge?
What is the tax/credit/discount/refund amount?
Can I download the invoice?
What you get
| View | What it means |
|---|---|
| Monthly summary | Total charge for selected billing period |
| Charges by service | EC2, RDS, S3, CloudWatch, etc. |
| Charges by account | Useful for AWS Organizations |
| Invoices | PDF invoices |
| Savings tab | Credits, discounts, refunds, tax, savings |
| CSV download | Finance-friendly export |
If consolidated billing is used, AWS says the Bills page lists totals for all accounts on the Charges by account tab. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Bills
→ Select billing period
→ Review summary
→ Expand service/account details
→ Download invoice PDF or CSV
FinOps advice
Use Bills for invoice truth, not daily cost analysis. For daily/monthly cost trends, use Cost Explorer or Data Exports.
6.2 Payments
What is it?
Payments shows what you owe AWS, payment status, unapplied funds, payment history, and invoices due. AWS describes the Payments page as a consolidated view of financial status, including what you owe and funds available to use. (AWS Documentation)
Why use it?
Use it when finance asks:
Is there any outstanding balance?
Which invoices are unpaid?
Did AWS charge our card/bank?
Do we have unapplied funds?
Can we download payment history?
What you get
| Item | Meaning |
|---|---|
| Total outstanding balance | Amount currently owed, including past due invoices |
| Total unapplied funds | Unused funds, credit memos, or Advance Pay balance |
| Payments due | Open invoices |
| Payment history | Previous payments |
| CSV download | Payment records for finance |
High-level steps
Billing and Cost Management
→ Payments
→ Payments due
→ Payment history
→ Unapplied funds
→ Download CSV if needed
FinOps advice
Payments is mainly for finance/accounting. DevOps usually needs read-only access only.
6.3 Credits
What is it?
Credits shows AWS credits, remaining balance, estimated current-month remaining balance, expiration date, applicable products, and allocation history. AWS says the Credits page shows credit balance under Amount remaining, and the credit details page includes metadata and application history. (AWS Documentation)
Why use it?
Use it when you have:
AWS promotional credits
Startup credits
Migration credits
Enterprise credits
Partner/reseller credits
Training/event credits
What you get
| Credit detail | Why it matters |
|---|---|
| Amount remaining | How much credit is left |
| Estimated amount remaining | Current-month estimate |
| Expiration date | Prevent losing unused credits |
| Applicable products | Which services can consume credit |
| Application history | Which account/service consumed credit |
| Sharing preference | Whether credits are shared across accounts |
High-level steps
Billing and Cost Management
→ Credits
→ Select credit
→ Review status, expiry, remaining amount
→ Review application history
→ Adjust sharing preference if allowed
FinOps advice
Credits can hide true cost. Always report both:
Net cost after credits
Gross cost before credits
This avoids surprise when credits expire.
6.4 Purchase Orders
What is it?
Purchase Orders lets you manage PO numbers and line items so they appear correctly on AWS invoices. AWS says you can add multiple purchase orders with multiple line items, and AWS selects the PO that best matches the invoice based on configuration. (AWS Documentation)
Why use it?
Use it when your procurement process requires:
PO number on invoices
Separate PO for AWS Marketplace
Separate PO for monthly usage
Separate PO for subscriptions or RI upfront charges
PO balance tracking
What you get
| Feature | Use |
|---|---|
| Multiple POs | Different departments or legal entities |
| Line items | Match monthly usage, subscriptions, Marketplace, training |
| Invoice association | Correct PO appears on invoice |
| Notifications | PO expiration or balance alerts |
AWS allows up to 100 active purchase orders with up to 100 line items for each regular account or AWS Organizations management account. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Purchase Orders
→ Add purchase order
→ Add line items
→ Define bill-from entity, period, amount, line item type
→ Save
→ Confirm association on invoices
FinOps advice
For enterprise AWS usage, map POs to:
AWS monthly usage
AWS Marketplace
Support
Reserved Instances / Savings Plans upfront
Professional services
7. Cost and Usage Analysis
This section answers:
Why did cost increase?
Which service/account/region/team caused it?
What is the trend?
What will we spend by month end?
Where is detailed historical data stored?
7.1 Cost Explorer
What is it?
Cost Explorer is AWS’s interactive cost and usage analysis tool. AWS says it lets you view and analyze cost and usage using graphs, cost and usage reports, and RI reports. It can show historical data, forecast future spend, and provide RI recommendations. (AWS Documentation)
Why use it?
Use it when investigating:
Monthly AWS cost trend
Cost by service
Cost by linked account
Cost by region
Cost by tag
Cost by usage type
Forecasted cost
EC2/RDS/NAT Gateway/CloudWatch cost changes
What you get
| Feature | Output |
|---|---|
| Filters | Account, service, region, tag, usage type |
| Group by | Service, account, region, tag, cost category |
| Granularity | Daily, monthly, sometimes hourly depending setup/data |
| Forecast | Future cost projection |
| CSV download | Export data behind graph |
| RI/SP recommendations | Commitment insights |
| Amazon Q integration | Natural-language cost questions |
AWS says Cost Explorer can display up to 13 months of historical data by default, the current month, and forecasted costs for the next 18 months after setup; Cost Explorer refreshes data at least once every 24 hours, depending on upstream billing data. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Cost Explorer
→ Select date range
→ Choose granularity
→ Filter by service/account/region/tag
→ Group by useful dimension
→ Save report or download CSV
FinOps advice
For your AWS environment, create standard Cost Explorer views:
Monthly cost by linked account
Monthly cost by service
Daily cost by environment tag
EKS-related costs
NAT Gateway cost
CloudWatch cost
RDS/Aurora cost
Data transfer cost
7.2 Cost Explorer Saved Reports
What is it?
Cost Explorer Saved Reports are saved Cost Explorer configurations. AWS says Cost Explorer provides default reports and lets you change filters/constraints, save reports, bookmark configurations, and download the CSV data behind graphs. (AWS Documentation)
Why use it?
Use saved reports when you repeatedly need the same analysis.
Examples:
EKS monthly cost
Prod account service breakdown
Tokyo region cost
NAT Gateway daily trend
CloudWatch logs ingestion cost
Cost by product tag
What you get
| Output | Value |
|---|---|
| Saved report | Reusable analysis |
| Default reports | Quick start |
| CSV download | Offline analysis |
| Bookmarks/favorites | Faster access |
High-level steps
Cost Explorer
→ Build your filter/grouping
→ Save to report library
→ Name the report
→ Reopen from Saved Reports
FinOps advice
Create a naming standard:
CE - Monthly Cost by Account
CE - Monthly Cost by Service
CE - EKS Cost by Env
CE - NAT Gateway Daily Trend
CE - Data Transfer by Region
7.3 Cost Anomaly Detection
What is it?
Cost Anomaly Detection uses AWS cost monitors and alert subscriptions to detect unusual spend patterns. AWS says it can configure cost monitors and alert subscriptions that adapt to your growing AWS environment, including AWS-managed monitors that track accounts, teams, or business units automatically. (AWS Documentation)
Why use it?
Budgets answer:
Are we over a planned limit?
Cost Anomaly Detection answers:
Is today’s cost unusual compared to normal behavior?
Use it for:
Unexpected NAT Gateway spike
CloudWatch logs ingestion jump
RDS backup/storage growth
EC2/EKS runaway workload
Data transfer anomaly
New service unexpectedly used
What you get
| Item | Meaning |
|---|---|
| Cost monitor | Scope being watched |
| Alert subscription | Who receives anomaly alerts |
| Root cause hints | Service/account/region dimensions |
| Anomaly dashboard | Detected anomalies, even below alert threshold |
| AWS managed monitor | Auto-expanding monitor scope |
AWS says creating a monitor requires at least one cost monitor and alert subscription, and monitor types include AWS services, linked account, cost allocation tag, and cost category. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Cost Anomaly Detection
→ Cost monitors
→ Create monitor
→ Choose AWS managed or customer managed
→ Select dimension: service/account/tag/category
→ Configure alert subscription
→ Choose email/SNS/User Notifications
FinOps advice
Recommended monitors:
All AWS services monitor
Linked account monitor
Environment tag monitor
Product/team cost category monitor
High-risk services monitor: NAT Gateway, CloudWatch, EC2, RDS, Data Transfer
7.4 Free Tier
What is it?
Free Tier tracks usage against AWS Free Tier offers and alerts when usage approaches or exceeds limits. AWS documents different behavior for accounts created before and after July 15, 2025, and says the Free Tier page can track actual usage against short-term trials and always-free usage limits. (AWS Documentation)
Why use it?
Use it for:
Training accounts
Sandbox accounts
Personal experiments
Student labs
New AWS accounts
What you get
| Item | Meaning |
|---|---|
| Free Tier usage | How much of free allowance has been used |
| Alerts | Email when approaching/exceeding usage limits |
| Credit balance | For free account plan / paid plan scenarios |
| Expiration information | Avoid surprise charges after trial/free period |
For older accounts, AWS says Free Tier usage alerts notify by email when usage exceeds 85% of the Free Tier limit, and you can use Budgets to track 100% of the Free Tier limit with a zero spend budget. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Free Tier
→ Review service usage
→ Enable Free Tier alerts in Billing preferences
→ Optionally create zero-spend budget
FinOps advice
For company AWS environments, Free Tier is less important than Budgets. For training/lab/student accounts, it is very useful.
7.5 Data Exports
What is it?
Data Exports is the modern way to export billing and cost-management datasets, including CUR 2.0, cost optimization recommendations, FOCUS data, and carbon emissions. AWS says Data Exports lets you create billing/cost and carbon emissions exports using SQL, customize columns/rows/schema, and store recurring exports in S3. (AWS Documentation)
Why use it?
Use it when you need serious historical cost analytics:
Long-term cost warehouse
Athena queries
QuickSight dashboards
Datadog Cloud Cost Management
Chargeback/showback
Cost by Kubernetes namespace
Cost by product/team/environment
Historical trend beyond console screenshots
What you get
| Export type | Use |
|---|---|
| CUR 2.0 | Detailed AWS cost and usage line items |
| Cost optimization recommendations | Savings opportunity dataset |
| FOCUS 1.0/1.2 with AWS columns | Open cost data standard |
| Carbon emissions | Sustainability reporting |
| Cost and usage dashboard | QuickSight integration |
| Legacy CUR | Older CUR format |
AWS says CUR 2.0 is the new and recommended way to receive detailed AWS cost and usage data. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Data Exports
→ Create export
→ Choose CUR 2.0 / FOCUS / recommendations / carbon emissions
→ Select columns and filters
→ Choose S3 bucket
→ Configure refresh/export schedule
→ Query with Athena or integrate with BI/Datadog
FinOps advice
For your AWS environments, this is the historical source of truth. Use:
Management account
→ Data Exports / CUR 2.0
→ S3 billing bucket
→ Athena
→ QuickSight or Datadog Cloud Cost Management
7.6 Carbon emissions
What is it?
Carbon emissions shows estimated AWS carbon footprint data. AWS’s Customer Carbon Footprint Tool uses MTCO2e and provides historical emissions data, service/region breakdowns, and CSV export. AWS says carbon emissions data is available for the previous 38 months, and new data is usually published between the 15th and 21st of the month after usage occurs. (AWS Documentation)
Why use it?
Use it for:
ESG reporting
Sustainability reporting
Regional footprint analysis
Executive reporting
Carbon-aware architecture discussions
What you get
| View | Meaning |
|---|---|
| Emissions summary | Estimated AWS emissions and savings |
| Emissions by region | Which AWS regions contribute most |
| Emissions by service | EC2, S3, CloudFront, other |
| CSV export | Historical reporting |
| Data Export | More granular export to S3 |
High-level steps
Billing and Cost Management
→ Carbon emissions
→ Review summary
→ Filter by calculation method
→ Review region/service trend
→ Download CSV or create data export
FinOps advice
Do not mix carbon reporting with financial chargeback unless your organization explicitly wants “green cost allocation.” Keep it as a separate sustainability reporting stream.
8. Cost Organization
This section answers:
Who owns the cost?
Which team/product/environment should pay?
How do we map AWS billing to business structure?
8.1 Cost Categories
What is it?
Cost Categories maps AWS cost into your internal business structure using rules. AWS says Cost Categories is a cost allocation service that helps map AWS costs to unique internal business structures, using rules to group costs into meaningful categories. (AWS Documentation)
Why use it?
Use Cost Categories when tags/accounts alone are not enough.
Examples:
Account 1 + Account 2 = Platform Team
Service EC2 + RDS + NAT Gateway = Shared Infrastructure
Tag product=analytics = Analytics BU
Untagged shared services split across teams
What you get
| Feature | Use |
|---|---|
| Rule-based grouping | Map costs to team/product/env |
| Hierarchies | BusinessUnit → Team → Product |
| Split charge rules | Allocate shared costs |
| Cost Explorer integration | Filter/group by category |
| Budgets integration | Budget by category |
| CUR/Data Export integration | Category appears in exported cost data |
| Anomaly Detection integration | Detect anomalies by category |
AWS says Cost Categories can be used across Cost Explorer, Budgets, CUR, and Cost Anomaly Detection. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Cost Categories
→ Create category
→ Define category values
→ Add rules based on account, service, tag, charge type, etc.
→ Add split charge rules if needed
→ Activate and use in Cost Explorer/Budgets/CUR
FinOps advice
For your setup, good categories would be:
Environment: dev, stage, uat, prod, shared
Product: analytics, backend, design, platform
Owner: team / manager / cost center
Criticality: production, non-production
8.2 Cost Allocation Tags
What is it?
Cost Allocation Tags are resource tags activated for billing analysis. AWS says a tag is a key/value label assigned to a resource, and after activation, AWS uses cost allocation tags to organize resource costs in cost allocation reports, Cost Explorer, and related billing views. (AWS Documentation)
Why use it?
Use tags when cost needs to follow resources.
Examples:
Environment=prod
Product=telematics
Team=platform
CostCenter=engineering
Owner=rajesh
Application=vehicle-service
What you get
| Output | Value |
|---|---|
| Cost by tag | Showback/chargeback |
| Tag filter in Cost Explorer | Analyze product/team/env cost |
| Tag columns in CUR | Data warehouse reporting |
| Budget by tag | Team/product budget |
| Untagged cost visibility | Governance improvement |
AWS says AWS-generated and user-defined cost allocation tags must be activated separately before they appear in Cost Explorer or cost allocation reports. (AWS Documentation)
High-level steps
Tag AWS resources
→ Billing and Cost Management
→ Cost Allocation Tags
→ Activate required tag keys
→ Wait for tags to appear
→ Use in Cost Explorer, Budgets, Data Exports
AWS notes that tags can take up to 24 hours to appear in the Billing and Cost Management console. (AWS Documentation)
FinOps advice
Mandatory AWS tags should be enforced by Terraform/module policy:
Environment
Product
Service
Team
Owner
CostCenter
ManagedBy
Repository
Avoid sensitive data in tags; AWS explicitly recommends not including sensitive information in tags. (AWS Documentation)
8.3 Billing Conductor
What is it?
AWS Billing Conductor creates an alternate/custom billing view for showback and chargeback. AWS says Billing Conductor supports showback/chargeback workflows and lets you customize a second, alternative version of monthly billing data without changing how AWS bills you. (AWS Documentation)
Why use it?
Use it when you need:
Custom internal rates
Partner/reseller billing
Chargeback to business units
Pro forma billing
Separate billing groups
Custom pricing rules
What you get
| Feature | Use |
|---|---|
| Billing groups | Group accounts/customers |
| Pricing plans | Custom rates |
| Pro forma bills | Internal/custom view |
| Custom CUR per billing group | Downstream reporting |
| Margin/showback analysis | Compare AWS actual vs internal rates |
High-level steps
Billing Conductor
→ Create billing group
→ Add linked accounts
→ Create pricing plan/rules
→ Assign pricing plan to billing group
→ Generate pro forma billing data
→ Export/report to teams/customers
FinOps advice
Most normal engineering teams do not need Billing Conductor. Use it if you are doing advanced chargeback, partner resale, or separate internal billing views.
9. Budgets and Planning
This section answers:
How do we prevent surprise bills?
How do we alert before overspend?
How do we estimate future workloads?
9.1 Budgets
What is it?
AWS Budgets lets you create cost, usage, RI, and Savings Plans budgets with actual and forecasted alerts. AWS says Budgets can track cost and usage, and examples include monthly cost budgets with actual and forecasted notifications, usage budgets, RI/Savings Plans utilization or coverage budgets, and custom period budgets. (AWS Documentation)
Why use it?
Use Budgets for proactive alerts:
Actual cost > 80%
Actual cost > 100%
Forecasted cost > 100%
Service-specific budget exceeded
Environment budget exceeded
Team budget exceeded
Savings Plan utilization below target
RI coverage below target
What you get
| Budget type | Use |
|---|---|
| Cost budget | Dollar spend |
| Usage budget | Units such as hours, GB, requests |
| RI utilization budget | Are purchased RIs being used? |
| RI coverage budget | How much eligible usage is covered by RIs? |
| Savings Plans utilization budget | Is committed spend being consumed? |
| Savings Plans coverage budget | How much eligible usage is covered by SP? |
AWS says Budgets information is updated up to three times per day, typically 8–12 hours after the previous update, and Budgets can track blended, unblended, net unblended, amortized, and net amortized costs. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Budgets
→ Create budget
→ Choose cost/usage/RI/SP type
→ Set amount and period
→ Scope by account/service/tag/category if needed
→ Add actual and forecast thresholds
→ Add email/SNS subscribers
→ Save
Your billing alert example
Budget: Monthly AWS Cost Budget
Amount: USD 2,000
Alert 1: Actual > 80% = USD 1,600
Alert 2: Actual > 100% = USD 2,000
Alert 3: Forecasted > 100% = forecast exceeds USD 2,000
FinOps advice
For your AWS environment:
Create global budget in management/payer account.
Create per-environment budgets for dev/stage/uat/prod.
Create high-risk service budgets for NAT Gateway, CloudWatch, EC2, RDS.
Route alerts through SNS/email/Slack.
9.2 Budget Actions
What is it?
Budget Actions allow AWS Budgets to take an action when a threshold is exceeded. AWS says Budgets can run an action automatically or after manual approval, such as applying an IAM policy or Service Control Policy. (AWS Documentation)
Why use it?
Use it when you want cost guardrails, not just alerts.
Examples:
Block new EC2 instance launches in sandbox
Restrict expensive services after budget breach
Apply SCP to non-production account
Require approval before continuing
What you get
| Action type | Use |
|---|---|
| IAM policy action | Restrict a role/user/group |
| SCP action | Restrict an AWS Organizations account/OU |
| Manual approval | Human-controlled enforcement |
| Automatic action | Strong guardrail |
High-level steps
Create budget
→ Add threshold
→ Configure action
→ Choose IAM/SCP action
→ Choose automatic or manual approval
→ Confirm required permissions
FinOps advice
Use Budget Actions carefully. For production, avoid automatic deny policies unless tested. For sandbox/dev, they are very useful.
9.3 Budgets Reports
What is it?
Budgets Reports send scheduled budget performance reports. AWS says Budgets Reports can monitor existing budgets on a daily, weekly, or monthly cadence and deliver the report to up to 50 email addresses. (AWS Documentation)
Why use it?
Use it for recurring reporting:
Weekly FinOps update
Monthly engineering budget status
Daily budget report during migration
Budget health report for leadership
What you get
| Feature | Value |
|---|---|
| Daily/weekly/monthly schedule | Automated reporting |
| Up to 50 recipients | Finance/team distribution |
| Up to 50 reports | Multiple stakeholder groups |
| Budget performance summary | Actual/forecast vs target |
AWS says each budget report costs $0.01 per report delivered, regardless of recipients. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Budgets Reports
→ Create report
→ Select budgets
→ Choose cadence
→ Add recipients
→ Save
FinOps advice
For your team, create one weekly report:
AWS Weekly Budget Report
Recipients: DevOps + Finance + Engineering leads
Cadence: Weekly Monday morning
Budgets: Global + env budgets + high-risk service budgets
9.4 Pricing Calculator
What is it?
AWS has two calculator experiences: public Pricing Calculator and in-console Pricing Calculator. The in-console AWS Pricing Calculator estimates planned cloud costs using your discounts and purchase commitments. AWS says it can assess migration impact, growth plans, and commitment purchases. (AWS Documentation)
Why use it?
Use it before deploying:
New EKS cluster
New Aurora database
More NAT Gateways
New CloudWatch ingestion
New multi-AZ architecture
New Savings Plan purchase
Migration from GCP to AWS
What you get
| Estimate type | Meaning |
|---|---|
| Workload estimate | Cost of a specific workload/application/change |
| Bill estimate | Cost impact across entire consolidated bill |
| Before-discount rates | Public On-Demand estimate |
| After-discount rates | More realistic based on your pricing |
| Commitment modeling | RI/SP impact analysis |
AWS says bill estimates include last month’s consolidated billing usage and existing commitments such as Savings Plans and Reserved Instances, and they allow modeling changes without affecting the actual bill. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Pricing Calculator
→ Choose workload estimate or bill estimate
→ Import existing usage if needed
→ Add/change resources
→ Model commitments
→ Save/export estimate
FinOps advice
Use Pricing Calculator before architecture approval. For example, before moving from one NAT Gateway to three NAT Gateways, estimate the monthly baseline and data processing impact.
10. Savings and Commitments
This section answers:
Where can we save money?
Are our commitments healthy?
Should we buy Savings Plans or Reserved Instances?
Are we wasting commitments?
10.1 Cost Optimization Hub
What is it?
Cost Optimization Hub consolidates and prioritizes savings recommendations across AWS accounts and Regions. AWS says it helps identify, filter, and aggregate recommendations such as resource rightsizing, idle resource deletion, Savings Plans, and Reserved Instances from a single dashboard. (AWS Documentation)
Why use it?
Use it to find:
Idle EC2
Underutilized EC2
Idle EBS
Rightsizing opportunities
Unused NAT Gateway-like waste patterns
Lambda optimization
RDS rightsizing
Savings Plans opportunities
Reserved Instance opportunities
What you get
| Feature | Value |
|---|---|
| Consolidated recommendations | One place instead of many consoles |
| Estimated monthly savings | Prioritize by impact |
| Deduplication | Avoid double-counting savings |
| Filters/grouping | Account, region, resource type, recommendation |
| API access | Automation/reporting |
| Organization view | Multi-account optimization |
AWS says Cost Optimization Hub supports many resource types including EC2, Auto Scaling groups, EBS, Lambda, ECS Fargate, Savings Plans, RIs, RDS, OpenSearch, Redshift, ElastiCache, DynamoDB reserved capacity, Aurora storage, and NAT Gateway. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Cost Optimization Hub
→ Opt in
→ Choose standalone/account/org scope
→ Review opportunities
→ Filter by account/region/resource/recommendation
→ Assign owners
→ Implement and track savings
FinOps advice
Create a weekly habit:
Every Monday:
Review top 10 savings opportunities
Assign owner
Validate risk
Implement safe changes
Track realized savings
11. Savings Plans
Savings Plans reduce eligible compute costs in exchange for a committed spend amount over one or three years. In Billing and Cost Management, the Savings Plans menu helps you manage inventory, recommendations, purchase analysis, utilization, coverage, purchases, and cart. AWS describes Savings Plans as flexible pricing models to reduce bills and manage inventory, recommendations, purchase analyses, utilization, and coverage. (AWS Documentation)
11.1 Savings Plans — Overview
What is it?
Overview is 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 underusing commitments?
Do we need to buy more?
What you get
Summary of owned plans
Utilization health
Coverage health
Savings trend
Recommendations entry point
High-level steps
Billing and Cost Management
→ Savings Plans
→ Overview
→ Review utilization, coverage, savings, upcoming expirations
11.2 Savings Plans — Inventory
What is it?
Inventory shows Savings Plans you own or have queued. AWS says the Inventory page shows a detailed overview of Savings Plans that you own or have queued, and management accounts can view account or organization inventory. (AWS Documentation)
Why use it?
Use it to track:
Plan type
Commitment amount
Start/end date
Payment option
Status
Owning account
Queued future purchases
What you get
Active Savings Plans
Queued Savings Plans
Expiring commitments
CSV download
Account vs Organization inventory
High-level steps
Savings Plans
→ Inventory
→ Choose Account inventory or Organization inventory
→ Review active/queued plans
→ Download CSV if needed
11.3 Savings Plans — Recommendations
What is it?
Recommendations suggest Savings Plans purchases based on historical On-Demand usage and existing commitments.
Why use it?
Use it when you have stable compute usage and want commitment discounts.
What you get
Recommended hourly commitment
Estimated monthly savings
Coverage impact
Utilization impact
Lookback-based recommendation parameters
High-level steps
Savings Plans
→ Recommendations
→ Choose lookback period
→ Review estimated savings
→ Open recommendation details
→ Validate with Purchase Analyzer
FinOps advice
Do not blindly buy recommendations. Validate:
Will workloads remain steady?
Are migrations/scale-downs coming?
Are services moving from EC2 to Fargate/serverless?
Is production stable enough for commitment?
11.4 Savings Plans — Purchase Analyzer
What is it?
Purchase Analyzer models the impact of potential Savings Plan purchases. AWS says it lets you model and evaluate purchases using a recommended amount, target coverage percentage, or custom amount, then view impact on savings, coverage, and utilization. (AWS Documentation)
Why use it?
Use it before buying Savings Plans.
What you get
| Metric | Meaning |
|---|---|
| Estimated monthly savings | Expected monthly reduction |
| Coverage percentage | How much eligible usage will be covered |
| Utilization | How much commitment will be consumed |
| Risk comparison | Compare commitment scenarios |
High-level steps
Savings Plans
→ Purchase Analyzer
→ Choose recommendation / target coverage / custom amount
→ Adjust lookback period
→ Exclude expiring plans if needed
→ Compare scenarios
→ Decide purchase amount
11.5 Savings Plans — Utilization Report
What is it?
Utilization tells you how much of your purchased Savings Plans commitment you are actually using. AWS says Savings Plans utilization shows the percentage of your commitment used across On-Demand usage. (AWS Documentation)
Why use it?
Use it to detect wasted commitments.
What you get
Utilization percentage
Unused commitment
Net savings
On-Demand equivalent spend
Filter by account, region, plan type, family
High-level steps
Savings Plans
→ Utilization Report
→ Select time range
→ Filter by account/region/type
→ Review utilization %
→ Investigate unused commitment
FinOps advice
Healthy target:
95–100% utilization for mature stable workloads
Lower utilization may be acceptable if intentionally keeping room for growth
11.6 Savings Plans — Coverage Report
What is it?
Coverage tells you how much eligible usage is covered by Savings Plans. AWS says the coverage report shows what percentage of applicable AWS usage costs are covered by Savings Plans during the selected period. (AWS Documentation)
Why use it?
Use it to find On-Demand spend that could be covered by commitments.
What you get
Coverage percentage
Eligible On-Demand spend
Covered spend
Uncovered spend
Service/account/region breakdown
High-level steps
Savings Plans
→ Coverage Report
→ Select period
→ Group/filter by account/service/region
→ Identify uncovered eligible spend
→ Review recommendations/Purchase Analyzer
FinOps advice
Coverage and utilization are different:
Utilization = Are we using what we bought?
Coverage = How much eligible usage is protected by what we bought?
High utilization with low coverage means you are using commitments well, but may need more.
11.7 Purchase Savings Plans
What is it?
This is where you buy custom Savings Plans or finalize recommended purchases. AWS says you can add selections to the Savings Plans cart from Recommendations or Purchase Savings Plans, and AWS recommends using Recommendations and Purchase Analyzer before purchasing. (AWS Documentation)
Why use it?
Use it only after analysis and approval.
What you get
Plan type selection
Commitment amount
Term
Payment option
Start date / queue option
Cart review
Purchase confirmation
High-level steps
Savings Plans
→ Recommendations or Purchase Analyzer
→ Choose plan
→ Add to cart
→ Review cart
→ Final approval
→ Purchase
FinOps advice
Require approval before buying commitments:
Requester: Platform/FinOps
Reviewer: Finance
Approver: Engineering/Infra owner
Evidence: utilization, coverage, forecast, migration roadmap
11.8 Cart
What is it?
The Cart is the checkout area for pending Savings Plans purchases. The “0” you see in the console usually means there are zero items currently in the cart.
Why use it?
Use it to review before committing money.
What you get
Pending purchase list
Term/payment/commitment summary
Final estimated cost
Purchase confirmation
High-level steps
Savings Plans
→ Cart
→ Review selected plans
→ Confirm details
→ Purchase or remove items
FinOps advice
Never leave major commitment purchases to one person. Treat the cart like a financial approval checkpoint.
12. Reservations
Reservations are commitment-based discounts/capacity constructs for services such as EC2, RDS, Redshift, ElastiCache, OpenSearch, DynamoDB reserved capacity, and others. AWS says Cost Explorer gives an overview of reservations, shows utilization and coverage, and calculates reservation recommendations that could save money. (AWS Documentation)
12.1 Reservations — Overview
What is it?
Reservations Overview shows current reservations, savings, and expiring reservations.
Why use it?
Use it to understand:
How many RIs do we own?
How much are they saving?
Are any expiring soon?
Are we using them efficiently?
AWS says the Reservations Overview page shows how many reservations you have, savings compared to On-Demand, and reservations expiring this month. (AWS Documentation)
High-level steps
Billing and Cost Management
→ Reservations
→ Overview
→ Review savings and expiration
→ Configure expiration alerts
AWS supports reservation expiration alerts 7, 30, or 60 days in advance and on the expiration day, for EC2, RDS, Redshift, ElastiCache, and OpenSearch reservations. (AWS Documentation)
12.2 Reservations — Recommendations
What is it?
Reservation Recommendations suggests RI purchases based on past On-Demand usage. AWS says Cost Explorer recommendations are based on the past 7, 30, or 60 days of single-account or organization usage and are updated at least once every 24 hours. (AWS Documentation)
Why use it?
Use it when workloads are predictable and stable.
What you get
Recommended reservation purchases
Estimated monthly savings
Estimated savings vs On-Demand
Lookback parameters
All-account and individual-account recommendations
High-level steps
Reservations
→ Recommendations
→ Choose service
→ Choose term/offering/payment/lookback
→ Review estimated savings
→ Validate workload stability
→ Purchase from service-specific reservation workflow
FinOps advice
For EKS worker compute, Savings Plans are often more flexible than EC2 RIs. For RDS/Aurora or Redshift, reservations may be more relevant.
12.3 Reservations — Utilization Report
What is it?
RI utilization measures how much of purchased reservation capacity you actually used.
Why use it?
Use it to find wasted reservations.
What you get
Utilization %
Unused reservation hours/capacity
Savings
Breakdown by service/account/region/instance family
High-level steps
Reservations
→ Utilization Report
→ Select time period
→ Filter service/account/region
→ Identify low utilization
→ Decide whether to modify/sell/avoid renewal where applicable
FinOps advice
Low utilization usually means:
Workload moved
Instance family changed
Region changed
Reservation purchased incorrectly
Demand dropped
12.4 Reservations — Coverage Report
What is it?
RI coverage measures how much eligible usage is covered by reservations versus On-Demand.
Why use it?
Use it to find eligible workloads still running On-Demand.
What you get
Coverage %
Uncovered On-Demand usage
Potential commitment opportunity
Breakdown by service/account/region
High-level steps
Reservations
→ Coverage Report
→ Select period
→ Filter service/account/region
→ Identify uncovered stable usage
→ Review recommendations
FinOps advice
For production databases, aim for strong coverage if usage is stable. For highly dynamic compute, be more careful.
13. Preferences and Settings
This section controls billing behavior, permissions, invoice setup, tax, payment methods, and multi-organization billing relationships.
13.1 Payment Preferences
What is it?
Payment Preferences manages AWS payment methods, default payment method, payment currency, payment profiles, and billing contact emails. AWS says the Payment preferences page is used to manage payment methods, and payment profiles can assign unique payment methods for different AWS service providers/sellers of record. (AWS Documentation)
Why use it?
Use it for:
Credit card / bank payment method
Default payment method
Payment currency
Billing contact emails
Different seller-of-record payment profiles
What you get
Payment method list
Default payment method
Payment profiles
Billing contact email
Currency setting
High-level steps
Billing and Cost Management
→ Payment Preferences
→ Add/update payment method
→ Set default
→ Configure billing contacts
→ Configure payment profiles if needed
13.2 Billing Preferences
What is it?
Billing Preferences controls invoice email delivery, alerts, credit sharing, RI/Savings Plans discount sharing, and legacy detailed billing settings. AWS says Billing Preferences can manage invoice delivery, alerts, credit sharing, RI/SP discount sharing, and detailed billing reports; some sections can only be updated by payer accounts. (Amazon Web Services Docs)
Why use it?
Use it to configure:
Receive PDF invoice by email
Free Tier alerts
CloudWatch billing alerts
Credit sharing across accounts
RI/Savings Plans discount sharing
Legacy report behavior
What you get
Invoice delivery settings
Alert preferences
Credit sharing settings
Discount sharing settings
High-level steps
Billing and Cost Management
→ Billing Preferences
→ Edit invoice delivery preferences
→ Edit alert preferences
→ Edit credit sharing / discount sharing settings
FinOps advice
For your budget-alert use case, Billing Preferences is separate from AWS Budgets, but it is where some billing alert preferences, including CloudWatch billing alerts and Free Tier alerts, may be enabled.
13.3 Cost Management Preferences
What is it?
Cost Management Preferences controls how cost data is shared or viewed, including member account visibility, data granularity, and optimization preferences. AWS describes Cost Management preferences as the place to manage what member accounts can view, account data granularity, and cost optimization preferences. (AWS Documentation)
Why use it?
Use it when operating a multi-account organization:
Allow/deny member accounts to see Cost Explorer data
Configure detailed cost data settings
Manage cost optimization preferences
Control organizational cost visibility
What you get
Member account cost visibility controls
Granularity options
Cost optimization settings
Linked account access behavior
High-level steps
Management account
→ Billing and Cost Management
→ Cost Management Preferences
→ Configure linked account access
→ Configure data granularity/options
→ Save
FinOps advice
For engineering teams, allow visibility to their own cost data. Hidden cost creates poor ownership.
13.4 Tax Settings
What is it?
Tax Settings manages tax registration numbers, tax inheritance across AWS Organizations accounts, and tax exemptions. AWS says Tax settings lets you manage tax registration numbers, turn on tax setting inheritance across Organizations accounts, and manage tax exemptions. (AWS Documentation)
Why use it?
Use it for:
Tax registration number
VAT/GST/JCT setup
Tax exemption management
Organization-wide tax inheritance
Legal entity compliance
What you get
Tax registration profile
Tax inheritance settings
Tax exemption status
Country/region-specific tax settings
High-level steps
Billing and Cost Management
→ Tax Settings
→ Add tax registration
→ Enable inheritance if needed
→ Upload/manage exemptions if applicable
→ Save
FinOps advice
Finance/accounting should own this. Platform/DevOps usually only needs awareness.
13.5 Invoice Configuration
What is it?
Invoice Configuration lets you create invoice units and customize invoice preferences across accounts. AWS says invoice units can be created within a single payer account or organization, new accounts are not automatically added, and payer/invoice receiver accounts can download invoices from the Bills page. (AWS Documentation)
Why use it?
Use it when you need:
Separate invoices for business units
Different invoice receivers
Procurement mapping
PO association to invoice units
Separate tax/payment handling
What you get
Invoice units
Invoice receivers
Account grouping for invoicing
PO association
Invoice-level configuration
High-level steps
Billing and Cost Management
→ Invoice Configuration
→ Create invoice unit
→ Add accounts
→ Configure invoice receiver
→ Associate PO if required
→ Review invoices on Bills page
FinOps advice
Useful for large organizations. Not required for simple Dev/Stage/UAT/Prod unless finance needs separate invoices.
13.6 Billing Transfer
What is it?
Billing Transfer lets one external account manage and pay the consolidated bill of another AWS Organization while the source organization keeps security/governance management. AWS says billing transfer starts when an external bill-transfer account sends an invitation to a management account; if accepted, it manages and pays the bill-source account’s consolidated bill from the specified date. (AWS Documentation)
Why use it?
Use it for:
AWS partners/resellers
Multiple AWS Organizations
Centralized billing operations
Commercial terms managed outside workload organization
Separating financial management from security governance
What you get
External bill-transfer account
Transferred consolidated invoices
Billing views
Showback/chargeback view with Billing Conductor
Centralized payment management
High-level steps
Bill-transfer account
→ Send billing transfer invitation
→ Bill-source management account accepts
→ Effective date starts billing transfer
→ Configure Billing Conductor pricing/view if needed
→ Access invoices/payments from transfer account
FinOps advice
Do not use Billing Transfer unless there is a clear enterprise/partner billing reason. It changes who receives invoices and controls cost data visibility.
14. How all tools fit together in a real company FinOps architecture
For your AWS environments, I would organize it like this:
AWS Organizations Management / Payer Account
│
├── Billing and Payments
│ ├── Bills
│ ├── Payments
│ ├── Credits
│ └── Purchase Orders
│
├── Cost Visibility
│ ├── Home
│ ├── Dashboards
│ ├── Cost Explorer
│ └── Saved Reports
│
├── Cost Allocation
│ ├── Cost Allocation Tags
│ ├── Cost Categories
│ └── Billing Conductor only if showback/chargeback is advanced
│
├── Cost Governance
│ ├── Budgets
│ ├── Budget Reports
│ └── Cost Anomaly Detection
│
├── Historical Data
│ ├── Data Exports / CUR 2.0
│ ├── S3
│ ├── Athena
│ └── QuickSight / Datadog Cloud Cost Management
│
├── Optimization
│ ├── Cost Optimization Hub
│ ├── Savings Plans
│ └── Reservations
│
└── Settings
├── Payment Preferences
├── Billing Preferences
├── Cost Management Preferences
├── Tax Settings
├── Invoice Configuration
└── Billing Transfer
15. Recommended setup order for your AWS environments
Do this in order:
Phase 1 — Foundation
1. Confirm AWS Organizations management/payer account.
2. Activate IAM billing access.
3. Create IAM roles for FinOps/Admin/ReadOnly.
4. Configure Billing Preferences.
5. Configure Payment 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 — Control
16. Create global monthly AWS budget.
17. Create per-environment budgets.
18. Create high-risk service budgets.
19. Enable Cost Anomaly Detection.
20. Configure SNS/email/Slack routing.
21. Create Budget Reports.
Phase 5 — Optimization
22. Enable Cost Optimization Hub.
23. Review top recommendations weekly.
24. Review Savings Plans coverage/utilization.
25. Review Reservation coverage/utilization.
26. Use Pricing Calculator before major architecture changes.
16. For your immediate billing-alert requirement
For your specific requirement:
Actual cost > 80% of USD 2000
Actual cost > 100% of USD 2000
Forecast cost > 100% of USD 2000
Use this:
Primary tool: AWS Budgets
Scope: Management / payer account
Budget type: Cost budget
Period: Monthly
Amount: USD 2,000
Notifications:
- Actual > 80%
- Actual > 100%
- Forecasted > 100%
Delivery:
- Email
- SNS topic
- Optional Slack/Datadog integration
Do not use CloudWatch as the main solution. CloudWatch billing alarms are only basic estimated-charge alarms. Use CloudWatch only as an optional backup. Use Datadog for visibility and dashboards if the AWS billing/CUR integration is enabled.
17. Best-practice operating cadence
Daily
Check Home
Check Cost Anomaly Detection
Check major cost spikes
Weekly
Review Cost Explorer trends
Review budget status
Review Cost Optimization Hub
Review untagged cost
Send budget report
Monthly
Review Bills and invoices
Review actual vs budget
Review credits
Review Savings Plans utilization/coverage
Review RI utilization/coverage
Review top services and top accounts
Review CUR/Datadog/QuickSight reports
Quarterly
Review commitment strategy
Review account/tag/category model
Review showback/chargeback
Review forecast vs actual accuracy
Review architecture cost changes
18. Final cheat sheet
| Need | Use this AWS feature |
|---|---|
| See invoice | Bills |
| See payment status | Payments |
| See credits | Credits |
| Put PO on invoice | Purchase Orders |
| Quick financial overview | Home |
| Custom visual reports | Dashboards |
| Investigate cost | Cost Explorer |
| Save repeated analysis | Cost Explorer Saved Reports |
| Detect unusual spikes | Cost Anomaly Detection |
| Track Free Tier | Free Tier |
| Store detailed historical cost | Data Exports / CUR 2.0 |
| ESG/carbon reporting | Carbon emissions |
| Map cost to business units | Cost Categories |
| Map cost to resources/teams/env | Cost Allocation Tags |
| Custom internal billing | Billing Conductor |
| Alert on budget thresholds | Budgets |
| Email budget performance | Budgets Reports |
| Estimate future workloads | Pricing Calculator |
| Find savings opportunities | Cost Optimization Hub |
| Manage compute commitments | Savings Plans |
| Manage service reservations | Reservations |
| Manage payment methods | Payment Preferences |
| Manage invoice/alerts/credit sharing | Billing Preferences |
| Control member account cost visibility | Cost Management Preferences |
| Manage tax IDs/exemptions | Tax Settings |
| Separate invoices by unit | Invoice Configuration |
| Centralize billing across organizations | Billing Transfer |
For your case, the most important first three are:
1. AWS Budgets
2. Cost Explorer
3. Data Exports / CUR 2.0
Then add:
4. Cost Allocation Tags
5. Cost Categories
6. Cost Anomaly Detection
7. Cost Optimization Hub
8. Dashboards / Datadog
