{"id":2602,"date":"2026-07-02T01:34:24","date_gmt":"2026-07-02T01:34:24","guid":{"rendered":"https:\/\/finopsschool.com\/blog\/?p=2602"},"modified":"2026-07-02T01:36:09","modified_gmt":"2026-07-02T01:36:09","slug":"aws-billing-and-cost-management-master-guide","status":"publish","type":"post","link":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/","title":{"rendered":"AWS Billing and Cost Management \u2014 Master Guide"},"content":{"rendered":"\n

AWS Billing and Cost Management is not one service. It is a financial management console<\/strong> made of several tools that help you do five major things:<\/p>\n\n\n\n

1. Pay and manage invoices\n2. Understand what AWS is costing\n3. Organize cost by account, team, product, environment, or tag\n4. Alert and plan against budget\n5. Optimize spend using commitments and savings recommendations\n<\/code><\/pre>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
For your AWS multi-environment setup, think of it like this:<\/p>\n\n\n\n
AWS Accounts\nDev \/ Stage \/ UAT \/ Prod \/ Shared\n        \u2193\nAWS Organizations Management or Payer Account\n        \u2193\nBilling and Cost Management\n        \u2193\nBills, Cost Explorer, Budgets, Data Exports, Cost Categories, Tags,\nCost Anomaly Detection, Cost Optimization Hub, Savings Plans, Reservations\n<\/code><\/pre>\n\n\n\n
The management\/payer account<\/strong> is usually the right place to manage organization-wide billing, budgets, Cost Explorer, Data Exports, cost allocation tags, cost categories, and savings visibility.<\/p>\n\n\n\n
\n\n\n\n
1. The correct mental model<\/h1>\n\n\n\n
AWS cost data flows like this:<\/p>\n\n\n\n
AWS services create usage\nEC2, EKS, RDS, NAT Gateway, S3, CloudWatch, ALB, Route 53, etc.\n        \u2193\nAWS billing pipeline calculates charges\n        \u2193\nBilling and Cost Management\n        \u2193\nCost Explorer \/ Bills \/ Budgets \/ Data Exports \/ Cost Categories \/ Tags\n        \u2193\nDashboards, reports, alerts, chargeback, optimization\n<\/code><\/pre>\n\n\n\n
Important distinction:<\/p>\n\n\n\n
Need<\/th>Correct AWS feature<\/th><\/tr><\/thead>
Final invoice and payment record<\/td>Bills \/ Payments<\/strong><\/td><\/tr>
Daily\/monthly spend investigation<\/td>Cost Explorer<\/strong><\/td><\/tr>
Budget alerting<\/td>AWS Budgets<\/strong><\/td><\/tr>
Unexpected spike detection<\/td>Cost Anomaly Detection<\/strong><\/td><\/tr>
Long-term historical raw billing data<\/td>Data Exports \/ CUR 2.0 to S3<\/strong><\/td><\/tr>
Cost by team\/product\/environment<\/td>Cost Allocation Tags + Cost Categories<\/strong><\/td><\/tr>
Savings recommendations<\/td>Cost Optimization Hub<\/strong><\/td><\/tr>
Commitment discount management<\/td>Savings Plans \/ Reservations<\/strong><\/td><\/tr>
Internal pro-forma billing<\/td>Billing Conductor<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
\n\n\n\n
2. Home<\/h1>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Home<\/strong> 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<\/strong>, Cost monitor<\/strong>, Cost breakdown<\/strong>, Recommended actions<\/strong>, Savings opportunities<\/strong>, and Top trends<\/strong>. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for a quick daily overview:<\/p>\n\n\n\n
Are we spending more than last month?\nAre we forecasted to exceed normal spend?\nWhich services or accounts are trending up?\nAre there savings opportunities?\nAre there budget or anomaly issues?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Area<\/th>What it gives<\/th><\/tr><\/thead>
Cost summary<\/td>Current month cost trend and forecast<\/td><\/tr>
Cost monitor<\/td>Budget\/anomaly-style financial health<\/td><\/tr>
Cost breakdown<\/td>Spend by important dimensions<\/td><\/tr>
Recommended actions<\/td>Suggested billing\/cost tasks<\/td><\/tr>
Savings opportunities<\/td>Optimization opportunities from Cost Optimization Hub<\/td><\/tr>
Top trends<\/td>Biggest positive\/negative cost movements<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Home\n\u2192 Review current month cost\n\u2192 Check forecast\n\u2192 Check cost monitor\n\u2192 Open Cost Explorer \/ Budgets \/ Cost Optimization Hub for details\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
For your setup, Home is good for a daily visual check<\/strong>, but not enough for real FinOps control. Use it as the top page, then investigate in Cost Explorer, Budgets, or Data Exports.<\/p>\n\n\n\n
\n\n\n\n
3. Getting Started<\/h1>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Getting Started<\/strong> 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\u2019s getting-started guidance covers account setup, IAM users\/roles, reviewing bills, and accessing billing features. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you are setting up a new AWS account or AWS Organization.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Billing setup checklist\nIAM billing-access guidance\nLinks to Bills, Payments, Cost Explorer, Budgets, Data Exports\nRecommended setup actions\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Root\/admin user\n\u2192 Enable IAM access to Billing if required\n\u2192 Create IAM roles for billing\/cost access\n\u2192 Configure payment and tax settings\n\u2192 Enable Cost Explorer\n\u2192 Create first budget\n\u2192 Enable Data Exports if needed\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
In real companies, do not let engineers use the root account for billing. Create IAM roles like:<\/p>\n\n\n\n
FinOpsAdmin\nBillingAdmin\nBillingReadOnly\nEngineeringCostViewer\nBudgetManager\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
4. Dashboards \u2014 New<\/h1>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Dashboards<\/strong> 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<\/a>)<\/p>\n\n\n\n
AWS also says dashboards can contain widgets that show costs, usage, Savings Plans\/RI coverage and utilization, and budget data. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Dashboards when different audiences need different cost views:<\/p>\n\n\n\n
Audience<\/th>Dashboard example<\/th><\/tr><\/thead>
Leadership<\/td>Total AWS cost, forecast, budget health<\/td><\/tr>
Platform\/DevOps<\/td>EKS, EC2, NAT Gateway, CloudWatch, RDS cost<\/td><\/tr>
Engineering managers<\/td>Cost by product\/team\/environment<\/td><\/tr>
Finance<\/td>Account\/service\/monthly trend<\/td><\/tr>
FinOps<\/td>Unallocated cost, anomalies, savings, commitments<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
What you get<\/h2>\n\n\n\n
Custom cost widgets\nBudget widgets\nService\/account\/region\/tag breakdowns\nSavings Plans and RI coverage\/utilization widgets\nShareable dashboards\nScheduled reports, depending on configuration\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Dashboards\n\u2192 Create dashboard\n\u2192 Add widgets\n\u2192 Select Cost Explorer \/ Budget \/ Savings \/ RI data\n\u2192 Save\n\u2192 Share or schedule\n<\/code><\/pre>\n\n\n\n
Recommended dashboards for your AWS estate<\/h2>\n\n\n\n
1. Executive AWS Monthly Cost Dashboard\n2. Environment Cost Dashboard: Dev \/ Stage \/ UAT \/ Prod\n3. EKS Cost Dashboard\n4. NAT Gateway and Data Transfer Dashboard\n5. RDS\/Aurora Cost Dashboard\n6. CloudWatch Logs and Metrics Cost Dashboard\n7. Budget Health Dashboard\n8. Savings and Commitments Dashboard\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
5. FinOps Agent \u2014 Preview<\/h1>\n\n\n\n
What is it?<\/h2>\n\n\n\n
AWS FinOps Agent<\/strong> 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<\/strong>, which means behavior and availability can change. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you want natural-language FinOps help:<\/p>\n\n\n\n
Why did AWS cost increase this week?\nWhich account caused the anomaly?\nCreate a cost report for leadership.\nFind optimization opportunities.\nSummarize cost by service, account, region, or tag.\nInvestigate anomalies and create follow-up tasks.\n<\/code><\/pre>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Natural-language cost questions\nCost anomaly investigation\nOptimization summaries\nReport generation\nTask\/automation workflows\nOptional Jira\/Slack integration\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Open AWS FinOps Agent\n\u2192 Create an agent\n\u2192 Configure IAM role\/permissions\n\u2192 Connect data sources\/integrations\n\u2192 Optionally connect Jira\/Slack\n\u2192 Ask cost questions or configure automations\n<\/code><\/pre>\n\n\n\n
AWS notes that the agent acts only on the data sources and integrations you connect during setup. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Practical use<\/h2>\n\n\n\n
Use it as an assistant, not the source of truth. Your source-of-truth stack should still be:<\/p>\n\n\n\n
Bills\nCost Explorer\nBudgets\nCost Anomaly Detection\nData Exports \/ CUR 2.0\nCost Optimization Hub\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
6. Billing and Payments<\/h1>\n\n\n\n
This section is for invoice, payment, credit, and procurement management<\/strong>.<\/p>\n\n\n\n
\n\n\n\n
6.1 Bills<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Bills<\/strong> is where you view current charges, previous month bills, invoice details, service-level charges, account-level charges, taxes, credits, refunds, and invoice downloads.<\/p>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Bills when asking:<\/p>\n\n\n\n
What did AWS charge us this month?\nWhat was the final invoice last month?\nWhich AWS account caused the charge?\nWhich service caused the charge?\nWhat credits\/refunds\/taxes were applied?\nCan I download the invoice?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Current month estimated charges\nFinal historical bills\nInvoice PDFs\nCSV exports\nCharges by service\nCharges by account\nCredits, discounts, taxes, refunds\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Bills\n\u2192 Select billing period\n\u2192 Review total\n\u2192 Expand by service\/account\n\u2192 Download invoice or CSV\n<\/code><\/pre>\n\n\n\n
Important note<\/h2>\n\n\n\n
Bills are best for invoice truth<\/strong>. For trend analysis, use Cost Explorer. For raw line-item analytics, use Data Exports.<\/p>\n\n\n\n
\n\n\n\n
6.2 Payments<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Payments<\/strong> shows outstanding balances, past payments, unapplied funds, and payment history. AWS\u2019s billing documentation describes Payments as the place to understand outstanding or past-due balances and payment history. (Amazon Web Services Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Payments when finance asks:<\/p>\n\n\n\n
Have we paid AWS?\nIs anything overdue?\nWhat is the payment history?\nWhich invoice is unpaid?\nWhich payment method was charged?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Outstanding balance\nPast-due balance\nPayment history\nUnapplied funds\nReceipts \/ payment records\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Payments\n\u2192 Review payments due\n\u2192 Review payment history\n\u2192 Download records if needed\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
DevOps usually only needs read-only access here. Finance owns this area.<\/p>\n\n\n\n
\n\n\n\n
6.3 Credits<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Credits<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Credits for:<\/p>\n\n\n\n
AWS startup credits\nMigration credits\nPromotional credits\nPartner credits\nEnterprise credits\nTraining\/lab credits\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Credit balance\nCredit expiration date\nCredit application history\nEligible services\nCredit sharing behavior\nRemaining credit estimate\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Credits\n\u2192 Review available credits\n\u2192 Check expiry date\n\u2192 Check where credits were applied\n\u2192 Adjust credit sharing if required\n<\/code><\/pre>\n\n\n\n
Practical warning<\/h2>\n\n\n\n
Credits can hide the real AWS run rate. Always track:<\/p>\n\n\n\n
Gross cost before credits\nNet cost after credits\nCredit burn-down rate\nCredit expiry risk\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
6.4 Purchase Orders<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Purchase Orders<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Purchase Orders when your company needs:<\/p>\n\n\n\n
PO number on AWS invoice\nSeparate PO for AWS Marketplace\nSeparate PO for support or subscriptions\nSeparate PO by department\/entity\nProcurement tracking\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
PO number mapping\nLine items\nPO balance\/period\nInvoice association\nProcurement compliance\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Purchase Orders\n\u2192 Add purchase order\n\u2192 Add line items\n\u2192 Define billing period and amount\n\u2192 Save\n\u2192 Verify on invoice\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7. Cost and Usage Analysis<\/h1>\n\n\n\n
This is where engineering and FinOps spend most of their time.<\/p>\n\n\n\n
\n\n\n\n
7.1 Cost Explorer<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Explorer<\/strong> is AWS\u2019s 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<\/a>)<\/p>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Cost Explorer to answer:<\/p>\n\n\n\n
Why did AWS cost increase?\nWhich service is expensive?\nWhich account is expensive?\nWhich region is expensive?\nWhat is the current month forecast?\nWhat did NAT Gateway cost?\nWhat did EKS-related compute cost?\nHow much did CloudWatch Logs cost?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Cost by service\nCost by account\nCost by region\nCost by usage type\nCost by tag\nCost by cost category\nDaily\/monthly trends\nForecast\nCSV export\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Cost Explorer\n\u2192 Choose date range\n\u2192 Choose granularity: daily\/monthly\n\u2192 Group by service\/account\/region\/tag\/category\n\u2192 Apply filters\n\u2192 Save report if useful\n<\/code><\/pre>\n\n\n\n
Practical reports for you<\/h2>\n\n\n\n
Monthly cost by linked account\nMonthly cost by service\nDaily cost by service\nCost by region: ap-northeast-1 \/ Tokyo\nCost by Environment tag\nNAT Gateway cost trend\nCloudWatch Logs cost trend\nRDS\/Aurora cost trend\nEC2\/EKS compute cost trend\nData transfer cost trend\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7.2 Cost Explorer Saved Reports<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Saved Reports<\/strong> are reusable Cost Explorer views. Instead of rebuilding the same filter\/grouping every week, you save the report.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Saved Reports for recurring analysis:<\/p>\n\n\n\n
EKS monthly cost\nProd account daily cost\nTokyo region cost\nNAT Gateway by account\nCloudWatch Logs by account\nRDS cost by environment\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Reusable Cost Explorer views\nStandardized reports\nFaster monthly review\nConsistent FinOps reporting\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Cost Explorer\n\u2192 Build report\n\u2192 Apply date range, filters, group-by\n\u2192 Save as report\n\u2192 Open later from Saved Reports\n<\/code><\/pre>\n\n\n\n
Recommended naming<\/h2>\n\n\n\n
CE - Monthly Cost by Account\nCE - Monthly Cost by Service\nCE - Tokyo Region Cost\nCE - NAT Gateway Daily Trend\nCE - CloudWatch Logs Trend\nCE - EKS Compute by Environment\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7.3 Cost Anomaly Detection<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Anomaly Detection<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Budgets answer:<\/p>\n\n\n\n
Did we cross a planned limit?\n<\/code><\/pre>\n\n\n\n
Cost Anomaly Detection answers:<\/p>\n\n\n\n
Is today\u2019s spend abnormal compared to usual behavior?\n<\/code><\/pre>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Unexpected NAT Gateway spike\nCloudWatch log ingestion explosion\nRDS backup\/storage growth\nEC2\/EKS runaway workload\nData transfer spike\nNew expensive AWS service usage\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Anomaly dashboard\nRoot-cause dimensions\nImpact estimate\nAccount\/service\/region clues\nEmail\/SNS\/User Notification alerts\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Cost Anomaly Detection\n\u2192 Create cost monitor\n\u2192 Choose monitor type\n\u2192 Create alert subscription\n\u2192 Set threshold and recipients\n\u2192 Review anomalies regularly\n<\/code><\/pre>\n\n\n\n
Recommended monitors<\/h2>\n\n\n\n
1. AWS services monitor\n2. Linked account monitor\n3. Environment tag monitor\n4. Product\/team cost category monitor\n5. High-risk services: NAT Gateway, CloudWatch, EC2, RDS, Data Transfer\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7.4 Free Tier<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Free Tier<\/strong> tracks usage against AWS Free Tier limits. AWS Free Tier is mainly relevant for new, sandbox, training, or personal accounts.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Training accounts\nStudent labs\nNew AWS accounts\nSandbox experiments\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Free Tier usage\nUsage warnings\nService-level free-tier consumption\nCredit\/free-plan status depending on account type\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Free Tier\n\u2192 Review usage\n\u2192 Enable Free Tier alerts if relevant\n\u2192 Create zero-spend budget for extra protection\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
For serious company workloads, Free Tier is not enough. Use Budgets and Cost Anomaly Detection.<\/p>\n\n\n\n
\n\n\n\n
7.5 Data Exports<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Data Exports<\/strong> 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<\/a>)<\/p>\n\n\n\n
AWS also says Data Exports can create three types of exports: standard exports<\/strong>, cost and usage dashboard exports<\/strong>, and legacy exports<\/strong>. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Data Exports when you need durable historical cost data:<\/p>\n\n\n\n
Long-term FinOps warehouse\nAthena SQL analysis\nQuickSight dashboards\nDatadog Cloud Cost Management\nChargeback\/showback\nCost by team\/product\/environment\nKubernetes\/EKS cost analysis\nDetailed historical reporting\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
CUR 2.0 \/ cost and usage data\nFOCUS-style datasets where available\nCost optimization recommendation exports\nCarbon emissions exports\nS3 delivery\nAthena\/BI integration\n<\/code><\/pre>\n\n\n\n
AWS describes Data Exports as a way to create recurring exports to S3 and customize columns\/rows\/schema using SQL-like selections. (AWS Documentation<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Data Exports\n\u2192 Create export\n\u2192 Choose export type\n\u2192 Select columns\/filter\n\u2192 Choose S3 bucket\n\u2192 Configure delivery\n\u2192 Query with Athena or ingest into BI\/Datadog\n<\/code><\/pre>\n\n\n\n
Practical architecture<\/h2>\n\n\n\n
Management account\n\u2192 Data Exports \/ CUR 2.0\n\u2192 S3 billing bucket\n\u2192 Athena table\n\u2192 QuickSight \/ Datadog Cloud Cost Management \/ custom reports\n<\/code><\/pre>\n\n\n\n
Important<\/h2>\n\n\n\n
This is your best historical source of truth<\/strong>. Cost Explorer is great for interactive analysis, but Data Exports is better for long-term reporting and automation.<\/p>\n\n\n\n
\n\n\n\n
7.6 Carbon emissions<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Carbon emissions<\/strong> shows AWS carbon footprint estimates for sustainability reporting. AWS\u2019s Customer Carbon Footprint Tool reports estimated AWS emissions and supports service\/region breakdowns and exports. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
ESG reporting\nSustainability reporting\nCarbon-aware architecture discussions\nRegion\/service footprint analysis\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Estimated emissions\nEmissions by region\nEmissions by service\nHistorical carbon trend\nCSV\/export options\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Carbon emissions\n\u2192 Review summary\n\u2192 Filter by time\/service\/region\n\u2192 Export data if needed\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
8. Cost Organization<\/h1>\n\n\n\n
This section is about ownership: who should be accountable for which cost?<\/strong><\/p>\n\n\n\n
\n\n\n\n
8.1 Cost Categories<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Categories<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Cost Categories when accounts and tags are not enough.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
Account 111 + Account 222 = Platform\nTag Product=Analytics = Analytics product\nService=NATGateway + account=shared = Shared Network\nUntagged shared infra = Platform Shared\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Business-unit cost views\nTeam\/product\/environment grouping\nShared-cost allocation\nCost Explorer grouping\/filtering\nBudget scopes\nCUR\/Data Export dimensions\nAnomaly monitor scopes\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Cost Categories\n\u2192 Create category\n\u2192 Define category values\n\u2192 Add rules using accounts, services, tags, charge types, etc.\n\u2192 Add split-charge rules if needed\n\u2192 Use in Cost Explorer\/Budgets\/Data Exports\n<\/code><\/pre>\n\n\n\n
Recommended categories for your environment<\/h2>\n\n\n\n
Environment = dev \/ stage \/ uat \/ prod \/ shared\nProduct = backend \/ analytics \/ design \/ platform\nOwner = team name\nCostCenter = finance code\nCriticality = production \/ non-production\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
8.2 Cost Allocation Tags<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Allocation Tags<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use tags to answer:<\/p>\n\n\n\n
How much does prod cost?\nHow much does each product cost?\nWhich team owns this resource?\nHow much is untagged?\nWhich app caused the bill?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Cost Explorer group\/filter by tag\nBudgets by tag\nData Export\/CUR tag columns\nCost allocation reports\nUntagged cost governance\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Tag resources\n\u2192 Billing and Cost Management\n\u2192 Cost Allocation Tags\n\u2192 Activate tag keys\n\u2192 Wait for billing data processing\n\u2192 Use tags in Cost Explorer, Budgets, Data Exports\n<\/code><\/pre>\n\n\n\n
Recommended mandatory tags<\/h2>\n\n\n\n
Environment\nProduct\nService\nTeam\nOwner\nCostCenter\nManagedBy\nRepository\nApplication\n<\/code><\/pre>\n\n\n\n
Practical warning<\/h2>\n\n\n\n
Tags must be activated for cost allocation<\/strong>. Merely tagging resources is not enough for billing reports.<\/p>\n\n\n\n
\n\n\n\n
8.3 Billing Conductor<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
AWS Billing Conductor<\/strong> creates a separate pro forma billing view<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Billing Conductor for advanced cases:<\/p>\n\n\n\n
Internal chargeback\nPartner\/reseller billing\nCustom internal rates\nCustom pricing rules\nShared-service allocation\nMultiple customer\/business-unit billing\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Billing groups\nPricing plans\nPricing rules\nCustom line items\nPro forma cost and usage data\nInternal bill-like views\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing Conductor\n\u2192 Create billing group\n\u2192 Add accounts\n\u2192 Create pricing plan\n\u2192 Add pricing rules\/custom line items\n\u2192 Assign pricing plan\n\u2192 Review pro forma billing data\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
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.<\/p>\n\n\n\n
\n\n\n\n
9. Budgets and Planning<\/h1>\n\n\n\n
This is where your billing-alert requirement belongs.<\/p>\n\n\n\n
\n\n\n\n
9.1 Budgets \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
AWS Budgets<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Budgets for planned financial limits:<\/p>\n\n\n\n
Actual cost > 80%\nActual cost > 100%\nForecasted cost > 100%\nDev account exceeds budget\nProd forecast exceeds budget\nNAT Gateway monthly spend exceeds threshold\nCloudWatch Logs spend exceeds threshold\nSavings Plan utilization drops below target\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Cost budgets\nUsage budgets\nRI utilization budgets\nRI coverage budgets\nSavings Plans utilization budgets\nSavings Plans coverage budgets\nActual alerts\nForecasted alerts\nEmail\/SNS notifications\nBudget actions where configured\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Budgets\n\u2192 Create budget\n\u2192 Choose cost budget\n\u2192 Set monthly amount\n\u2192 Scope by account\/service\/tag\/category if needed\n\u2192 Add actual and forecast thresholds\n\u2192 Add email\/SNS recipients\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
Your example<\/h2>\n\n\n\n
Budget name: monthly-aws-total-cost-2000\nBudget amount: USD 2,000\nPeriod: Monthly\n\nAlert 1: Actual > 80%  = USD 1,600\nAlert 2: Actual > 100% = USD 2,000\nAlert 3: Forecasted > 100% = projected monthly cost > USD 2,000\n<\/code><\/pre>\n\n\n\n
Practical recommendation<\/h2>\n\n\n\n
For you:<\/p>\n\n\n\n
Create the main budget in the management\/payer account.\nUse AWS Budgets as the official alerting source.\nRoute notifications to SNS + email.\nOptionally forward SNS to Slack\/Datadog later.\n<\/code><\/pre>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
\n\n\n\n
9.2 Budgets Reports<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Budgets Reports<\/strong> send scheduled budget status reports. They are useful for weekly\/monthly governance.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Budgets Reports for:<\/p>\n\n\n\n
Weekly FinOps email\nMonthly engineering budget review\nLeadership budget summary\nEnvironment budget health report\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Scheduled reports\nBudget actual vs planned\nForecast vs budget\nEmail distribution\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Budgets Reports\n\u2192 Create report\n\u2192 Select budgets\n\u2192 Choose frequency\n\u2192 Add recipients\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
Recommended report<\/h2>\n\n\n\n
Name: Weekly AWS Budget Health\nFrequency: Weekly\nRecipients: DevOps, FinOps, Engineering leads\nBudgets: Global + per-environment + high-risk service budgets\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
9.3 Pricing Calculator \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Pricing Calculator<\/strong> estimates future AWS cost. AWS\u2019s in-console Pricing Calculator can estimate planned cloud costs using actual AWS pricing context, discounts, and commitments where applicable. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it before deploying or changing architecture:<\/p>\n\n\n\n
New EKS cluster\nMore NAT Gateways\nNew RDS\/Aurora database\nMore CloudWatch ingestion\nNew OpenSearch cluster\nCross-region replication\nPrivateLink design\nSavings Plan purchase planning\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Workload estimate\nBill estimate\nMonthly projected cost\nResource-level cost model\nCommitment impact analysis\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Pricing Calculator\n\u2192 Create estimate\n\u2192 Add AWS services\/resources\n\u2192 Configure region\/usage\n\u2192 Include commitments\/discounts if available\n\u2192 Save\/export estimate\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
Before approving architecture, require a calculator estimate for anything likely to add recurring cost:<\/p>\n\n\n\n
NAT Gateway\nEKS node capacity\nRDS\/Aurora\nOpenSearch\nCloudWatch Logs\nData transfer\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
10. Savings and Commitments<\/h1>\n\n\n\n
This section is for optimization and commitment management.<\/p>\n\n\n\n
\n\n\n\n
10.1 Cost Optimization Hub \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Optimization Hub<\/strong> 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<\/a>)<\/p>\n\n\n\n
AWS also notes that viewing opportunities in other accounts requires management-account access and opting in member accounts. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to find savings:<\/p>\n\n\n\n
Idle resources\nUnderutilized resources\nRightsizing opportunities\nSavings Plans opportunities\nReserved Instance opportunities\nResource cleanup opportunities\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Estimated monthly savings\nRecommendations by account\nRecommendations by region\nRecommendations by resource type\nDeduplicated savings opportunities\nPrioritized optimization backlog\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Cost Optimization Hub\n\u2192 Opt in\n\u2192 Include member accounts if using AWS Organizations\n\u2192 Review dashboard\n\u2192 Filter by account\/region\/resource type\n\u2192 Assign owners\n\u2192 Track implementation\n<\/code><\/pre>\n\n\n\n
Weekly practice<\/h2>\n\n\n\n
Every Monday:\nReview top 10 savings opportunities\nValidate risk\nAssign owner\nImplement safe actions\nTrack realized savings\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11. Savings Plans<\/h1>\n\n\n\n
Savings Plans are commitment-based discounts for eligible compute usage. They are generally more flexible than classic EC2 Reserved Instances for many compute workloads.<\/p>\n\n\n\n
\n\n\n\n
11.1 Savings Plans \u2014 Overview<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
The landing page for your Savings Plans posture.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to answer:<\/p>\n\n\n\n
Do we own Savings Plans?\nAre they saving money?\nAre they expiring?\nAre we using our commitment fully?\nDo we need more coverage?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Savings summary\nUtilization summary\nCoverage summary\nInventory entry point\nRecommendations entry point\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Savings Plans\n\u2192 Overview\n\u2192 Review utilization, coverage, and savings\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.2 Savings Plans \u2014 Inventory<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Inventory<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Active plan tracking\nQueued plan tracking\nExpiration review\nCommitment amount review\nPlan ownership\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Plan type\nCommitment amount\nStart\/end date\nPayment option\nStatus\nOwning account\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Inventory\n\u2192 Choose account or organization view\n\u2192 Review active and queued plans\n\u2192 Export if needed\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.3 Savings Plans \u2014 Recommendations<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Recommendations suggest Savings Plans purchases based on eligible historical usage.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when compute spend is stable and predictable.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Recommended hourly commitment\nEstimated savings\nCoverage impact\nUtilization impact\nLookback-based analysis\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Recommendations\n\u2192 Choose lookback period\n\u2192 Review recommended commitment\n\u2192 Validate roadmap\n\u2192 Analyze with Purchase Analyzer\n<\/code><\/pre>\n\n\n\n
Practical warning<\/h2>\n\n\n\n
Do not blindly buy recommendations. Check:<\/p>\n\n\n\n
Are workloads stable?\nWill migration reduce usage?\nWill instance families or compute types change?\nAre we moving from EC2 to Fargate\/serverless?\nIs production baseline predictable?\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.4 Savings Plans \u2014 Purchase Analyzer \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Purchase Analyzer<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it before committing money.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Estimated monthly savings\nCoverage projection\nUtilization projection\nScenario comparison\nRisk visibility\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Purchase Analyzer\n\u2192 Select recommended \/ target coverage \/ custom amount\n\u2192 Adjust lookback\n\u2192 Compare scenarios\n\u2192 Prepare approval\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.5 Savings Plans \u2014 Utilization Report<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Utilization shows whether you are actually consuming the Savings Plans commitment you bought.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to detect wasted commitment.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Utilization percentage\nUnused commitment\nNet savings\nOn-Demand equivalent spend\nAccount\/service breakdown\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Utilization Report\n\u2192 Select time range\n\u2192 Review utilization %\n\u2192 Investigate unused commitment\n<\/code><\/pre>\n\n\n\n
Interpretation<\/h2>\n\n\n\n
High utilization = you are using what you bought\nLow utilization = you overcommitted or usage moved\/dropped\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.6 Savings Plans \u2014 Coverage Report<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Coverage shows how much eligible usage is covered by Savings Plans.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to find On-Demand compute spend that could be discounted.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Coverage %\nCovered spend\nUncovered eligible spend\nService\/account\/region breakdown\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Coverage Report\n\u2192 Select period\n\u2192 Group by service\/account\/region\n\u2192 Identify uncovered eligible spend\n\u2192 Review recommendations\n<\/code><\/pre>\n\n\n\n
Interpretation<\/h2>\n\n\n\n
High utilization + low coverage = existing plans are used well, but you may need more.\nLow utilization + high coverage = you may be overcommitted.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.7 Purchase Savings Plans<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
This is where Savings Plans are purchased.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it only after recommendation review, Purchase Analyzer modeling, and approval.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Plan type\nCommitment amount\nTerm\nPayment option\nStart date\nCart checkout\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Purchase Savings Plans\n\u2192 Choose plan\n\u2192 Add to cart\n\u2192 Review\n\u2192 Purchase\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.8 Cart<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
The cart holds pending Savings Plans purchases. If it shows 0<\/code>, there are no pending purchases.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it as final review before commitment.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Pending purchase summary\nCommitment details\nTerm\/payment review\nFinal purchase confirmation\n<\/code><\/pre>\n\n\n\n
Practical governance<\/h2>\n\n\n\n
Treat this as a financial approval point. Savings Plans are not casual engineering changes.<\/p>\n\n\n\n
\n\n\n\n
12. Reservations<\/h1>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
\n\n\n\n
12.1 Reservations \u2014 Overview<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
A summary of reservation ownership, savings, utilization, and expirations.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to answer:<\/p>\n\n\n\n
Which reservations do we own?\nAre they saving money?\nAre any expiring?\nAre they being used?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Reservation inventory summary\nSavings summary\nExpiration alerts\nUtilization\/coverage entry points\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Reservations\n\u2192 Overview\n\u2192 Review owned reservations\n\u2192 Check savings and expiration\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
12.2 Reservations \u2014 Recommendations \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for stable services like:<\/p>\n\n\n\n
RDS\nRedshift\nElastiCache\nOpenSearch\nStable EC2 workloads\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Recommended reservation purchases\nEstimated monthly savings\nLookback-based model\nTerm\/payment options\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Reservations\n\u2192 Recommendations\n\u2192 Choose service\n\u2192 Choose lookback\/term\/payment\n\u2192 Review savings\n\u2192 Validate workload stability\n\u2192 Purchase via service-specific path\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
12.3 Reservations \u2014 Utilization Report<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Shows how much of your purchased reserved capacity is being used.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to detect wasted reservations.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Utilization %\nUnused reserved hours\/capacity\nSavings impact\nAccount\/service\/region breakdown\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Reservations\n\u2192 Utilization Report\n\u2192 Select time range\n\u2192 Review low-utilization items\n\u2192 Investigate workload movement or overcommitment\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
12.4 Reservations \u2014 Coverage Report<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Shows how much eligible usage is covered by reservations.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to identify stable On-Demand usage that could be discounted.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Coverage %\nUncovered usage\nCovered usage\nPotential reservation opportunity\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Reservations\n\u2192 Coverage Report\n\u2192 Select period\n\u2192 Group by account\/service\/region\n\u2192 Identify uncovered stable workloads\n\u2192 Review recommendations\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
13. Preferences and Settings<\/h1>\n\n\n\n
This section controls billing behavior, payment methods, visibility, tax, invoice configuration, and billing transfer.<\/p>\n\n\n\n
\n\n\n\n
13.1 Payment Preferences<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Payment Preferences<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Credit card \/ bank payment method\nDefault payment method\nPayment currency\nBilling contacts\nPayment profiles\nSeller-of-record handling\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Payment method configuration\nDefault payment method\nPayment profiles\nBilling contact setup\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Payment Preferences\n\u2192 Add\/update payment method\n\u2192 Set default method\n\u2192 Configure payment profile if needed\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
13.2 Billing Preferences<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Billing Preferences<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
PDF invoice email delivery\nCloudWatch billing alerts\nFree Tier alerts\nCredit sharing across accounts\nRI\/Savings Plans discount sharing\nLegacy detailed billing settings\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Invoice delivery settings\nAlert preferences\nCredit sharing settings\nDiscount sharing settings\nLegacy report options\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Billing Preferences\n\u2192 Configure invoice delivery\n\u2192 Configure alert preferences\n\u2192 Configure credit sharing\n\u2192 Configure RI\/SP discount sharing\n<\/code><\/pre>\n\n\n\n
Practical note<\/h2>\n\n\n\n
This is where CloudWatch billing alerts may need to be enabled, but for your real cost alerts, AWS Budgets is still better.<\/p>\n\n\n\n
\n\n\n\n
13.3 Cost Management Preferences \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Management Preferences<\/strong> controls cost-management data visibility and optimization preferences. This is especially relevant in AWS Organizations.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Member account Cost Explorer visibility\nCost Optimization Hub opt-in\nCost data sharing preferences\nGranularity\/preferences for cost management features\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Linked account access behavior\nOptimization visibility\nCost-management feature preferences\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Management account\n\u2192 Billing and Cost Management\n\u2192 Cost Management Preferences\n\u2192 Configure member-account access\n\u2192 Configure optimization preferences\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
For engineering ownership, allow teams to see their own cost. Hidden cost creates poor accountability.<\/p>\n\n\n\n
\n\n\n\n
13.4 Tax Settings<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Tax Settings<\/strong> manages tax registration, tax inheritance, and exemptions.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
VAT\/GST\/JCT registration\nTax exemption\nLegal entity compliance\nTax inheritance across AWS Organizations\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Tax registration numbers\nTax exemption status\nOrganization tax inheritance\nCountry\/region-specific tax setup\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Tax Settings\n\u2192 Add tax registration\n\u2192 Configure inheritance if needed\n\u2192 Upload exemption documents if applicable\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
Finance\/accounting owns this. DevOps should not casually modify it.<\/p>\n\n\n\n
\n\n\n\n
13.5 Invoice Configuration<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Invoice Configuration<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Separate invoices by business unit\nSeparate invoice receivers\nDifferent legal\/tax handling\nPO alignment\nBilling transfer invoice customization\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Invoice units\nInvoice receiver mapping\nAccount grouping for invoices\nTax\/SOR handling for transferred billing\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Invoice Configuration\n\u2192 Create invoice unit\n\u2192 Add accounts or billing scope\n\u2192 Configure invoice receiver\/settings\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
Practical use<\/h2>\n\n\n\n
Not required for simple AWS setups. Very useful for large enterprises or billing-transfer models.<\/p>\n\n\n\n
\n\n\n\n
13.6 Billing Transfer \u2014 New<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Billing Transfer<\/strong> 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\u2019s announcement describes Billing Transfer as a way to centrally manage and pay bills across multiple AWS organizations. (Amazon Web Services, Inc.<\/a>)<\/p>\n\n\n\n
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\u2019s consolidated bill from the selected effective date. (AWS Documentation<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Central billing across multiple AWS Organizations\nPartner\/reseller billing\nEnterprise central finance model\nSeparating security governance from billing ownership\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Centralized billing responsibility\nTransferred invoices\nBilling views\nIntegration with Billing Conductor for chargeback\/showback\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Bill-transfer account\n\u2192 Send billing transfer invitation\n\u2192 Bill-source management account accepts\n\u2192 Effective date starts billing transfer\n\u2192 Configure billing views\/invoice configuration if needed\n<\/code><\/pre>\n\n\n\n
Practical warning<\/h2>\n\n\n\n
This is advanced enterprise billing. Do not use it unless finance\/legal\/procurement specifically needs centralized billing across multiple AWS Organizations.<\/p>\n\n\n\n
\n\n\n\n
14. Correct setup for your AWS billing alerts<\/h1>\n\n\n\n
For your immediate requirement:<\/p>\n\n\n\n
Actual cost > 80% of USD 2,000\nActual cost > 100% of USD 2,000\nForecast cost > 100% of USD 2,000\n<\/code><\/pre>\n\n\n\n
Use:<\/p>\n\n\n\n
Primary: AWS Budgets\nNotification routing: SNS + email\nVisibility: Cost Explorer \/ Dashboards \/ Datadog if integrated\nHistorical source: Data Exports \/ CUR 2.0 in S3\nOptional backup: CloudWatch billing alarm\n<\/code><\/pre>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Recommended design:<\/p>\n\n\n\n
AWS Management \/ Payer Account\n\u2502\n\u251c\u2500\u2500 Budget: monthly-aws-total-cost-2000\n\u2502   \u251c\u2500\u2500 Actual > 80%\n\u2502   \u251c\u2500\u2500 Actual > 100%\n\u2502   \u2514\u2500\u2500 Forecasted > 100%\n\u2502\n\u251c\u2500\u2500 SNS Topic: aws-budget-alerts\n\u2502   \u251c\u2500\u2500 Email distribution list\n\u2502   \u251c\u2500\u2500 Slack integration, optional\n\u2502   \u2514\u2500\u2500 Datadog event integration, optional\n\u2502\n\u251c\u2500\u2500 Cost Explorer Saved Reports\n\u2502   \u251c\u2500\u2500 Monthly cost by account\n\u2502   \u251c\u2500\u2500 Monthly cost by service\n\u2502   \u2514\u2500\u2500 Tokyo region cost\n\u2502\n\u2514\u2500\u2500 Data Exports \/ CUR 2.0\n    \u2514\u2500\u2500 S3 bucket \u2192 Athena \/ BI \/ Datadog Cloud Cost Management\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
15. Best-practice implementation order<\/h1>\n\n\n\n
Phase 1 \u2014 Billing foundation<\/h2>\n\n\n\n
1. Confirm management\/payer account.\n2. Enable IAM access to Billing if required.\n3. Create FinOps\/Billing IAM roles.\n4. Configure Payment Preferences.\n5. Configure Billing Preferences.\n6. Configure Tax Settings.\n<\/code><\/pre>\n\n\n\n
Phase 2 \u2014 Visibility<\/h2>\n\n\n\n
7. Enable\/use Cost Explorer.\n8. Create Cost Explorer Saved Reports.\n9. Create Dashboards.\n10. Enable Data Exports \/ CUR 2.0 to S3.\n11. Query with Athena or integrate with Datadog Cloud Cost Management.\n<\/code><\/pre>\n\n\n\n
Phase 3 \u2014 Allocation<\/h2>\n\n\n\n
12. Define mandatory tags.\n13. Activate Cost Allocation Tags.\n14. Create Cost Categories.\n15. Build dashboards by environment\/product\/team.\n<\/code><\/pre>\n\n\n\n
Phase 4 \u2014 Governance<\/h2>\n\n\n\n
16. Create monthly global AWS Budget.\n17. Create environment-specific budgets.\n18. Create high-risk service budgets.\n19. Enable Cost Anomaly Detection.\n20. Route alerts through SNS\/email\/Slack.\n21. Create Budgets Reports.\n<\/code><\/pre>\n\n\n\n
Phase 5 \u2014 Optimization<\/h2>\n\n\n\n
22. Enable Cost Optimization Hub.\n23. Review savings weekly.\n24. Review Savings Plans utilization and coverage.\n25. Review Reservations utilization and coverage.\n26. Use Pricing Calculator before major changes.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
16. Practical AWS FinOps operating model<\/h1>\n\n\n\n
Daily<\/h2>\n\n\n\n
Check Home\nCheck Cost Anomaly Detection\nCheck budget alerts\nCheck unexpected service\/account spikes\n<\/code><\/pre>\n\n\n\n
Weekly<\/h2>\n\n\n\n
Review Cost Explorer trends\nReview top cost drivers\nReview Cost Optimization Hub\nReview untagged cost\nSend Budget Report\n<\/code><\/pre>\n\n\n\n
Monthly<\/h2>\n\n\n\n
Review Bills\nCompare actual vs budget\nReview credits\nReview Savings Plans utilization\/coverage\nReview Reservations utilization\/coverage\nReview Data Export\/Athena reports\n<\/code><\/pre>\n\n\n\n
Quarterly<\/h2>\n\n\n\n
Review commitment strategy\nReview tagging compliance\nReview Cost Categories\nReview showback\/chargeback process\nReview forecast accuracy\nReview large architecture cost drivers\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
17. Final cheat sheet<\/h1>\n\n\n\n
Console option<\/th>Best used for<\/th><\/tr><\/thead>
Home<\/td>Fast cost health overview<\/td><\/tr>
Getting Started<\/td>Initial billing\/cost setup<\/td><\/tr>
Dashboards<\/td>Custom cost and budget dashboards<\/td><\/tr>
FinOps Agent<\/td>AI-assisted FinOps investigation, preview only<\/td><\/tr>
Bills<\/td>Invoice and final billing details<\/td><\/tr>
Payments<\/td>Payment status and history<\/td><\/tr>
Credits<\/td>Credit balance, expiry, application<\/td><\/tr>
Purchase Orders<\/td>PO mapping to invoices<\/td><\/tr>
Cost Explorer<\/td>Interactive cost investigation<\/td><\/tr>
Cost Explorer Saved Reports<\/td>Reusable cost reports<\/td><\/tr>
Cost Anomaly Detection<\/td>Unusual spend detection<\/td><\/tr>
Free Tier<\/td>Free-tier tracking for new\/sandbox accounts<\/td><\/tr>
Data Exports<\/td>Long-term historical cost data in S3<\/td><\/tr>
Carbon emissions<\/td>Sustainability\/carbon reporting<\/td><\/tr>
Cost Categories<\/td>Business-level cost grouping<\/td><\/tr>
Cost Allocation Tags<\/td>Resource\/team\/product\/environment cost allocation<\/td><\/tr>
Billing Conductor<\/td>Pro forma billing, chargeback\/showback<\/td><\/tr>
Budgets<\/td>Budget alerts and cost guardrails<\/td><\/tr>
Budgets Reports<\/td>Scheduled budget status emails<\/td><\/tr>
Pricing Calculator<\/td>Forecasting planned workload cost<\/td><\/tr>
Cost Optimization Hub<\/td>Savings opportunities<\/td><\/tr>
Savings Plans Overview<\/td>Commitment health summary<\/td><\/tr>
Savings Plans Inventory<\/td>Active\/queued Savings Plans<\/td><\/tr>
Savings Plans Recommendations<\/td>Suggested commitment purchases<\/td><\/tr>
Purchase Analyzer<\/td>Model Savings Plans purchase scenarios<\/td><\/tr>
SP Utilization Report<\/td>Are we using what we bought?<\/td><\/tr>
SP Coverage Report<\/td>How much eligible usage is covered?<\/td><\/tr>
Purchase Savings Plans<\/td>Buy Savings Plans<\/td><\/tr>
Cart<\/td>Review pending Savings Plans purchases<\/td><\/tr>
Reservations Overview<\/td>RI ownership and health<\/td><\/tr>
Reservations Recommendations<\/td>Suggested RI purchases<\/td><\/tr>
RI Utilization Report<\/td>Are reservations being used?<\/td><\/tr>
RI Coverage Report<\/td>How much eligible usage is reserved?<\/td><\/tr>
Payment Preferences<\/td>Payment methods and payment profiles<\/td><\/tr>
Billing Preferences<\/td>Invoice delivery, alerts, credit\/discount sharing<\/td><\/tr>
Cost Management Preferences<\/td>Cost visibility and optimization preferences<\/td><\/tr>
Tax Settings<\/td>Tax registrations and exemptions<\/td><\/tr>
Invoice Configuration<\/td>Invoice unit customization<\/td><\/tr>
Billing Transfer<\/td>Central billing across multiple AWS Organizations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
For your immediate next step, I would start with Budgets<\/strong>, Cost Explorer Saved Reports<\/strong>, and Data Exports<\/strong>. Those three give you alerting, investigation, and historical truth.<\/p>\n","protected":false},"excerpt":{"rendered":"
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: 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 … Read more<\/a><\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2602","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nAWS Billing and Cost Management \u2014 Master Guide - FinOps School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AWS Billing and Cost Management \u2014 Master Guide - FinOps School\" \/>\n<meta property=\"og:description\" content=\"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: 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 ... Read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/\" \/>\n<meta property=\"og:site_name\" content=\"FinOps School\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-02T01:34:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-02T01:36:09+00:00\" \/>\n<meta name=\"author\" content=\"rajeshkumar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"rajeshkumar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/\"},\"author\":{\"name\":\"rajeshkumar\",\"@id\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/#\\\/schema\\\/person\\\/0cc0bd5373147ea66317868865cda1b8\"},\"headline\":\"AWS Billing and Cost Management \u2014 Master Guide\",\"datePublished\":\"2026-07-02T01:34:24+00:00\",\"dateModified\":\"2026-07-02T01:36:09+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/\"},\"wordCount\":3318,\"commentCount\":0,\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/\",\"url\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/\",\"name\":\"AWS Billing and Cost Management \u2014 Master Guide - FinOps School\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/#website\"},\"datePublished\":\"2026-07-02T01:34:24+00:00\",\"dateModified\":\"2026-07-02T01:36:09+00:00\",\"author\":{\"@id\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/#\\\/schema\\\/person\\\/0cc0bd5373147ea66317868865cda1b8\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/aws-billing-and-cost-management-master-guide\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AWS Billing and Cost Management \u2014 Master Guide\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/#website\",\"url\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/\",\"name\":\"FinOps School\",\"description\":\"FinOps NoOps Certifications\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"http:\\\/\\\/finopsschool.com\\\/blog\\\/#\\\/schema\\\/person\\\/0cc0bd5373147ea66317868865cda1b8\",\"name\":\"rajeshkumar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g\",\"caption\":\"rajeshkumar\"},\"url\":\"https:\\\/\\\/finopsschool.com\\\/blog\\\/author\\\/rajeshkumar\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"AWS Billing and Cost Management \u2014 Master Guide - FinOps School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/","og_locale":"en_US","og_type":"article","og_title":"AWS Billing and Cost Management \u2014 Master Guide - FinOps School","og_description":"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: 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 ... Read more","og_url":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/","og_site_name":"FinOps School","article_published_time":"2026-07-02T01:34:24+00:00","article_modified_time":"2026-07-02T01:36:09+00:00","author":"rajeshkumar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"rajeshkumar","Est. reading time":"15 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/#article","isPartOf":{"@id":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/"},"author":{"name":"rajeshkumar","@id":"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8"},"headline":"AWS Billing and Cost Management \u2014 Master Guide","datePublished":"2026-07-02T01:34:24+00:00","dateModified":"2026-07-02T01:36:09+00:00","mainEntityOfPage":{"@id":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/"},"wordCount":3318,"commentCount":0,"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/","url":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/","name":"AWS Billing and Cost Management \u2014 Master Guide - FinOps School","isPartOf":{"@id":"http:\/\/finopsschool.com\/blog\/#website"},"datePublished":"2026-07-02T01:34:24+00:00","dateModified":"2026-07-02T01:36:09+00:00","author":{"@id":"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8"},"breadcrumb":{"@id":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/finopsschool.com\/blog\/aws-billing-and-cost-management-master-guide\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/finopsschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"AWS Billing and Cost Management \u2014 Master Guide"}]},{"@type":"WebSite","@id":"http:\/\/finopsschool.com\/blog\/#website","url":"http:\/\/finopsschool.com\/blog\/","name":"FinOps School","description":"FinOps NoOps Certifications","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/finopsschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8","name":"rajeshkumar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g","caption":"rajeshkumar"},"url":"https:\/\/finopsschool.com\/blog\/author\/rajeshkumar\/"}]}},"_links":{"self":[{"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2602","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=2602"}],"version-history":[{"count":2,"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2602\/revisions"}],"predecessor-version":[{"id":2604,"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2602\/revisions\/2604"}],"wp:attachment":[{"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=2602"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=2602"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=2602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}