{"id":1033,"date":"2026-07-02T01:29:14","date_gmt":"2026-07-02T01:29:14","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/?p=1033"},"modified":"2026-07-02T01:29:15","modified_gmt":"2026-07-02T01:29:15","slug":"master-guide-aws-billing-and-cost-management","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/master-guide-aws-billing-and-cost-management\/","title":{"rendered":"Master Guide: AWS Billing and Cost Management"},"content":{"rendered":"\n

Below is a master guide to AWS Billing and Cost Management<\/strong>, written like a complete FinOps tutorial. I\u2019ll map every menu item you listed and explain:<\/p>\n\n\n\n

What is it?\nWhy use it?\nWhat do you get from it?\nHigh-level steps to use it?\nWhere it fits in a real FinOps workflow?\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Master Guide: AWS Billing and Cost Management<\/h1>\n\n\n\n
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<\/strong>. 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<\/a>)<\/p>\n\n\n\n
For a multi-account company setup, the most important concept is this:<\/p>\n\n\n\n
AWS member accounts generate usage\n        \u2193\nAWS billing system calculates cost\n        \u2193\nManagement \/ payer account receives consolidated billing\n        \u2193\nCost Explorer, Bills, Budgets, Data Exports, Cost Categories, Tags, and Optimization tools analyze that data\n<\/code><\/pre>\n\n\n\n
If you use AWS Organizations, the management account<\/strong> 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<\/a>)<\/p>\n\n\n\n
\n\n\n\n
1. Mental model: how AWS cost data flows<\/h1>\n\n\n\n
AWS Services\nEC2, EKS, RDS, NAT Gateway, S3, CloudWatch, ALB, Route 53, etc.\n        \u2193\nAWS usage and billing pipeline\n        \u2193\nBilling and Cost Management data layer\n        \u2193\nBills \/ Payments \/ Credits\nCost Explorer\nBudgets\nCost Anomaly Detection\nData Exports \/ CUR 2.0\nCost Categories \/ Tags\nCost Optimization Hub\nSavings Plans \/ Reservations\n        \u2193\nFinance, DevOps, FinOps, Engineering, Leadership dashboards\n<\/code><\/pre>\n\n\n\n
There are three practical layers:<\/p>\n\n\n\n
Layer<\/th>Purpose<\/th>Main AWS tools<\/th><\/tr><\/thead>
Billing truth<\/strong><\/td>What AWS invoices you for<\/td>Bills, Payments, Credits, Purchase Orders<\/td><\/tr>
Cost analysis<\/strong><\/td>Why cost changed and who caused it<\/td>Cost Explorer, Data Exports, Dashboards, Cost Anomaly Detection<\/td><\/tr>
Cost control and optimization<\/strong><\/td>Prevent overspend and reduce waste<\/td>Budgets, Cost Optimization Hub, Savings Plans, Reservations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
A very important detail: Billing page data and Cost Explorer data can differ<\/strong>. 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<\/a>)<\/p>\n\n\n\n
So for investigation:<\/p>\n\n\n\n
Invoice\/payment issue \u2192 Bills \/ Payments\nTrend or service analysis \u2192 Cost Explorer\nLong-term detailed history \u2192 Data Exports \/ CUR 2.0 in S3\nAlerting \u2192 AWS Budgets + Cost Anomaly Detection\nSavings \u2192 Cost Optimization Hub + Savings Plans + Reservations\n<\/code><\/pre>\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you want a quick answer to:<\/p>\n\n\n\n
Are we spending more than usual?\nWhich services are driving cost?\nAre we forecasted to exceed budget?\nDo we have unallocated cost?\nAre there saving opportunities?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Widget \/ area<\/th>What it gives you<\/th><\/tr><\/thead>
Cost summary<\/td>Month-to-date cost, last month comparison, forecasted monthly cost<\/td><\/tr>
Cost monitor<\/td>Anomalies, budget overruns, high-priority cost issues<\/td><\/tr>
Cost breakdown<\/td>Cost by service, account, region, or other useful views<\/td><\/tr>
Recommended actions<\/td>Budget, tax, payment, optimization, anomaly, and IAM-related action items<\/td><\/tr>
Cost allocation coverage<\/td>How much cost is properly mapped to tags\/categories<\/td><\/tr>
Savings opportunities<\/td>Savings recommendations<\/td><\/tr>
Top trends<\/td>Services\/accounts\/regions trending up or down<\/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 cost summary\n\u2192 Review cost monitor\n\u2192 Check recommended actions\n\u2192 Click into Cost Explorer \/ Budgets \/ Cost Optimization Hub for details\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
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<\/strong>, not the source of detailed historical truth.<\/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 that helps you set up Billing and Cost Management properly. AWS\u2019s 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when setting up a new AWS account, new AWS Organization, or new FinOps process.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Area<\/th>Why it matters<\/th><\/tr><\/thead>
IAM billing access<\/td>Lets IAM roles\/users access billing console<\/td><\/tr>
Bills review<\/td>Lets you verify monthly AWS charges<\/td><\/tr>
Payment setup<\/td>Ensures AWS invoices can be paid<\/td><\/tr>
Tax setup<\/td>Keeps tax registration\/exemption data correct<\/td><\/tr>
Cost Management setup<\/td>Enables budgets, forecasts, reports, and cost visibility<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
By default, AWS says IAM roles\/users cannot access the Billing and Cost Management console unless the root user activates IAM access. (AWS Documentation<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Root \/ authorized admin\n\u2192 Account page\n\u2192 Activate IAM access to Billing\n\u2192 Assign billing\/cost IAM permissions\n\u2192 Open Billing and Cost Management\n\u2192 Review Bills\n\u2192 Review Payments\n\u2192 Enable Cost Explorer\n\u2192 Configure budgets and reports\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Do not give broad billing access to everyone. Create IAM roles such as:<\/p>\n\n\n\n
BillingAdmin\nFinOpsAdmin\nFinOpsReadOnly\nEngineeringCostViewer\nBudgetManager\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
4. Dashboards<\/h1>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Dashboards<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Dashboards when different stakeholders need different views:<\/p>\n\n\n\n
Leadership \u2192 total monthly cost, forecast, trend\nPlatform team \u2192 EKS, EC2, NAT Gateway, RDS, CloudWatch\nFinance \u2192 monthly cost by account and service\nEngineering managers \u2192 cost by product\/team\/environment\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Dashboard capability<\/th>Value<\/th><\/tr><\/thead>
Custom widgets<\/td>Build views by service, account, region, tag, budget<\/td><\/tr>
Budget widgets<\/td>Compare actual\/forecast spend against budget<\/td><\/tr>
RI\/Savings Plan widgets<\/td>Track commitment utilization and coverage<\/td><\/tr>
Sharing<\/td>Share securely inside\/outside organization<\/td><\/tr>
PDF export<\/td>Offline reporting<\/td><\/tr>
Scheduled email delivery<\/td>Daily\/weekly\/monthly reporting<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
AWS documents that dashboards can be exported as PDF and scheduled for email delivery. (AWS Documentation<\/a>)<\/p>\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 \/ Budgets \/ RI \/ Savings Plans data\n\u2192 Save\n\u2192 Share or schedule email report\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Create at least these dashboards:<\/p>\n\n\n\n
Executive AWS Cost Dashboard\nEnvironment Cost Dashboard\nEKS Cost Dashboard\nTop Cost Drivers Dashboard\nCommitment Utilization Dashboard\nBudget Health 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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you want AI-assisted FinOps workflows:<\/p>\n\n\n\n
Why did cost increase yesterday?\nWhich account caused the anomaly?\nCreate a monthly AWS cost report.\nGenerate a PPT for leadership.\nSummarize cost by service\/account\/region\/tag.\nCreate Jira tickets for cost anomalies.\nPost investigation summaries to Slack.\n<\/code><\/pre>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Output<\/th><\/tr><\/thead>
Natural-language cost inquiry<\/td>Answers based on Cost Explorer\/anomaly data<\/td><\/tr>
Cost reports<\/td>HTML, PDF, PPT<\/td><\/tr>
Anomaly investigation<\/td>Consolidated investigation summaries<\/td><\/tr>
Jira\/Slack integration<\/td>Tickets and notifications<\/td><\/tr>
Context upload<\/td>Account-owner mapping and org rules<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Switch to us-east-1\n\u2192 Open AWS FinOps Agent console\n\u2192 Create agent\n\u2192 Let wizard create IAM roles\/policies\n\u2192 Optionally connect Slack\/Jira\n\u2192 Upload account-owner mapping and org context\n\u2192 Ask cost questions or create scheduled tasks\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
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.<\/p>\n\n\n\n
\n\n\n\n
6. Billing and Payments<\/h1>\n\n\n\n
This section answers:<\/p>\n\n\n\n
What did AWS charge us?\nHave we paid?\nDo we have credits?\nWhich PO appears on the invoice?\n<\/code><\/pre>\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Bills when finance or engineering asks:<\/p>\n\n\n\n
What did AWS invoice us?\nWhich service caused the charge?\nWhich account generated the charge?\nWhat is the tax\/credit\/discount\/refund amount?\nCan I download the invoice?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
View<\/th>What it means<\/th><\/tr><\/thead>
Monthly summary<\/td>Total charge for selected billing period<\/td><\/tr>
Charges by service<\/td>EC2, RDS, S3, CloudWatch, etc.<\/td><\/tr>
Charges by account<\/td>Useful for AWS Organizations<\/td><\/tr>
Invoices<\/td>PDF invoices<\/td><\/tr>
Savings tab<\/td>Credits, discounts, refunds, tax, savings<\/td><\/tr>
CSV download<\/td>Finance-friendly export<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
If consolidated billing is used, AWS says the Bills page lists totals for all accounts on the Charges by account tab. (AWS Documentation<\/a>)<\/p>\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 summary\n\u2192 Expand service\/account details\n\u2192 Download invoice PDF or CSV\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Use Bills for invoice truth<\/strong>, not daily cost analysis. For daily\/monthly cost trends, use Cost Explorer or 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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when finance asks:<\/p>\n\n\n\n
Is there any outstanding balance?\nWhich invoices are unpaid?\nDid AWS charge our card\/bank?\nDo we have unapplied funds?\nCan we download payment history?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Item<\/th>Meaning<\/th><\/tr><\/thead>
Total outstanding balance<\/td>Amount currently owed, including past due invoices<\/td><\/tr>
Total unapplied funds<\/td>Unused funds, credit memos, or Advance Pay balance<\/td><\/tr>
Payments due<\/td>Open invoices<\/td><\/tr>
Payment history<\/td>Previous payments<\/td><\/tr>
CSV download<\/td>Payment records for finance<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Payments\n\u2192 Payments due\n\u2192 Payment history\n\u2192 Unapplied funds\n\u2192 Download CSV if needed\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Payments is mainly for finance\/accounting. DevOps usually needs read-only access only.<\/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, 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you have:<\/p>\n\n\n\n
AWS promotional credits\nStartup credits\nMigration credits\nEnterprise credits\nPartner\/reseller credits\nTraining\/event credits\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Credit detail<\/th>Why it matters<\/th><\/tr><\/thead>
Amount remaining<\/td>How much credit is left<\/td><\/tr>
Estimated amount remaining<\/td>Current-month estimate<\/td><\/tr>
Expiration date<\/td>Prevent losing unused credits<\/td><\/tr>
Applicable products<\/td>Which services can consume credit<\/td><\/tr>
Application history<\/td>Which account\/service consumed credit<\/td><\/tr>
Sharing preference<\/td>Whether credits are shared across accounts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Credits\n\u2192 Select credit\n\u2192 Review status, expiry, remaining amount\n\u2192 Review application history\n\u2192 Adjust sharing preference if allowed\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Credits can hide true cost. Always report both:<\/p>\n\n\n\n
Net cost after credits\nGross cost before credits\n<\/code><\/pre>\n\n\n\n
This avoids surprise when credits expire.<\/p>\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when your procurement process requires:<\/p>\n\n\n\n
PO number on invoices\nSeparate PO for AWS Marketplace\nSeparate PO for monthly usage\nSeparate PO for subscriptions or RI upfront charges\nPO balance tracking\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Use<\/th><\/tr><\/thead>
Multiple POs<\/td>Different departments or legal entities<\/td><\/tr>
Line items<\/td>Match monthly usage, subscriptions, Marketplace, training<\/td><\/tr>
Invoice association<\/td>Correct PO appears on invoice<\/td><\/tr>
Notifications<\/td>PO expiration or balance alerts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\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 bill-from entity, period, amount, line item type\n\u2192 Save\n\u2192 Confirm association on invoices\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For enterprise AWS usage, map POs to:<\/p>\n\n\n\n
AWS monthly usage\nAWS Marketplace\nSupport\nReserved Instances \/ Savings Plans upfront\nProfessional services\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7. Cost and Usage Analysis<\/h1>\n\n\n\n
This section answers:<\/p>\n\n\n\n
Why did cost increase?\nWhich service\/account\/region\/team caused it?\nWhat is the trend?\nWhat will we spend by month end?\nWhere is detailed historical data stored?\n<\/code><\/pre>\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when investigating:<\/p>\n\n\n\n
Monthly AWS cost trend\nCost by service\nCost by linked account\nCost by region\nCost by tag\nCost by usage type\nForecasted cost\nEC2\/RDS\/NAT Gateway\/CloudWatch cost changes\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Output<\/th><\/tr><\/thead>
Filters<\/td>Account, service, region, tag, usage type<\/td><\/tr>
Group by<\/td>Service, account, region, tag, cost category<\/td><\/tr>
Granularity<\/td>Daily, monthly, sometimes hourly depending setup\/data<\/td><\/tr>
Forecast<\/td>Future cost projection<\/td><\/tr>
CSV download<\/td>Export data behind graph<\/td><\/tr>
RI\/SP recommendations<\/td>Commitment insights<\/td><\/tr>
Amazon Q integration<\/td>Natural-language cost questions<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Cost Explorer\n\u2192 Select date range\n\u2192 Choose granularity\n\u2192 Filter by service\/account\/region\/tag\n\u2192 Group by useful dimension\n\u2192 Save report or download CSV\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For your AWS environment, create standard Cost Explorer views:<\/p>\n\n\n\n
Monthly cost by linked account\nMonthly cost by service\nDaily cost by environment tag\nEKS-related costs\nNAT Gateway cost\nCloudWatch cost\nRDS\/Aurora cost\nData transfer cost\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
Cost Explorer Saved Reports<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use saved reports when you repeatedly need the same analysis.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
EKS monthly cost\nProd account service breakdown\nTokyo region cost\nNAT Gateway daily trend\nCloudWatch logs ingestion cost\nCost by product tag\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Output<\/th>Value<\/th><\/tr><\/thead>
Saved report<\/td>Reusable analysis<\/td><\/tr>
Default reports<\/td>Quick start<\/td><\/tr>
CSV download<\/td>Offline analysis<\/td><\/tr>
Bookmarks\/favorites<\/td>Faster access<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Cost Explorer\n\u2192 Build your filter\/grouping\n\u2192 Save to report library\n\u2192 Name the report\n\u2192 Reopen from Saved Reports\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Create a naming standard:<\/p>\n\n\n\n
CE - Monthly Cost by Account\nCE - Monthly Cost by Service\nCE - EKS Cost by Env\nCE - NAT Gateway Daily Trend\nCE - Data Transfer by Region\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> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Budgets answer:<\/p>\n\n\n\n
Are we over a planned limit?\n<\/code><\/pre>\n\n\n\n
Cost Anomaly Detection answers:<\/p>\n\n\n\n
Is today\u2019s cost unusual compared to normal behavior?\n<\/code><\/pre>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Unexpected NAT Gateway spike\nCloudWatch logs ingestion jump\nRDS backup\/storage growth\nEC2\/EKS runaway workload\nData transfer anomaly\nNew service unexpectedly used\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Item<\/th>Meaning<\/th><\/tr><\/thead>
Cost monitor<\/td>Scope being watched<\/td><\/tr>
Alert subscription<\/td>Who receives anomaly alerts<\/td><\/tr>
Root cause hints<\/td>Service\/account\/region dimensions<\/td><\/tr>
Anomaly dashboard<\/td>Detected anomalies, even below alert threshold<\/td><\/tr>
AWS managed monitor<\/td>Auto-expanding monitor scope<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Cost Anomaly Detection\n\u2192 Cost monitors\n\u2192 Create monitor\n\u2192 Choose AWS managed or customer managed\n\u2192 Select dimension: service\/account\/tag\/category\n\u2192 Configure alert subscription\n\u2192 Choose email\/SNS\/User Notifications\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Recommended monitors:<\/p>\n\n\n\n
All AWS services monitor\nLinked account monitor\nEnvironment tag monitor\nProduct\/team cost category monitor\nHigh-risk services monitor: 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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Training accounts\nSandbox accounts\nPersonal experiments\nStudent labs\nNew AWS accounts\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Item<\/th>Meaning<\/th><\/tr><\/thead>
Free Tier usage<\/td>How much of free allowance has been used<\/td><\/tr>
Alerts<\/td>Email when approaching\/exceeding usage limits<\/td><\/tr>
Credit balance<\/td>For free account plan \/ paid plan scenarios<\/td><\/tr>
Expiration information<\/td>Avoid surprise charges after trial\/free period<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Free Tier\n\u2192 Review service usage\n\u2192 Enable Free Tier alerts in Billing preferences\n\u2192 Optionally create zero-spend budget\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For company AWS environments, Free Tier is less important than Budgets. For training\/lab\/student accounts, it is very useful.<\/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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you need serious historical cost analytics:<\/p>\n\n\n\n
Long-term cost warehouse\nAthena queries\nQuickSight dashboards\nDatadog Cloud Cost Management\nChargeback\/showback\nCost by Kubernetes namespace\nCost by product\/team\/environment\nHistorical trend beyond console screenshots\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Export type<\/th>Use<\/th><\/tr><\/thead>
CUR 2.0<\/td>Detailed AWS cost and usage line items<\/td><\/tr>
Cost optimization recommendations<\/td>Savings opportunity dataset<\/td><\/tr>
FOCUS 1.0\/1.2 with AWS columns<\/td>Open cost data standard<\/td><\/tr>
Carbon emissions<\/td>Sustainability reporting<\/td><\/tr>
Cost and usage dashboard<\/td>QuickSight integration<\/td><\/tr>
Legacy CUR<\/td>Older CUR format<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
AWS says CUR 2.0 is the new and recommended way to receive detailed AWS cost and usage data. (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 CUR 2.0 \/ FOCUS \/ recommendations \/ carbon emissions\n\u2192 Select columns and filters\n\u2192 Choose S3 bucket\n\u2192 Configure refresh\/export schedule\n\u2192 Query with Athena or integrate with BI\/Datadog\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For your AWS environments, this is the historical source of truth. Use:<\/p>\n\n\n\n
Management account\n\u2192 Data Exports \/ CUR 2.0\n\u2192 S3 billing bucket\n\u2192 Athena\n\u2192 QuickSight or Datadog Cloud Cost Management\n<\/code><\/pre>\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 estimated AWS carbon footprint data. AWS\u2019s 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<\/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\nRegional footprint analysis\nExecutive reporting\nCarbon-aware architecture discussions\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
View<\/th>Meaning<\/th><\/tr><\/thead>
Emissions summary<\/td>Estimated AWS emissions and savings<\/td><\/tr>
Emissions by region<\/td>Which AWS regions contribute most<\/td><\/tr>
Emissions by service<\/td>EC2, S3, CloudFront, other<\/td><\/tr>
CSV export<\/td>Historical reporting<\/td><\/tr>
Data Export<\/td>More granular export to S3<\/td><\/tr><\/tbody><\/table><\/figure>\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 calculation method\n\u2192 Review region\/service trend\n\u2192 Download CSV or create data export\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Do not mix carbon reporting with financial chargeback unless your organization explicitly wants \u201cgreen cost allocation.\u201d Keep it as a separate sustainability reporting stream.<\/p>\n\n\n\n
\n\n\n\n
8. Cost Organization<\/h1>\n\n\n\n
This section answers:<\/p>\n\n\n\n
Who owns the cost?\nWhich team\/product\/environment should pay?\nHow do we map AWS billing to business structure?\n<\/code><\/pre>\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> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Cost Categories when tags\/accounts alone are not enough.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
Account 1 + Account 2 = Platform Team\nService EC2 + RDS + NAT Gateway = Shared Infrastructure\nTag product=analytics = Analytics BU\nUntagged shared services split across teams\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Use<\/th><\/tr><\/thead>
Rule-based grouping<\/td>Map costs to team\/product\/env<\/td><\/tr>
Hierarchies<\/td>BusinessUnit \u2192 Team \u2192 Product<\/td><\/tr>
Split charge rules<\/td>Allocate shared costs<\/td><\/tr>
Cost Explorer integration<\/td>Filter\/group by category<\/td><\/tr>
Budgets integration<\/td>Budget by category<\/td><\/tr>
CUR\/Data Export integration<\/td>Category appears in exported cost data<\/td><\/tr>
Anomaly Detection integration<\/td>Detect anomalies by category<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
AWS says Cost Categories can be used across Cost Explorer, Budgets, CUR, and Cost Anomaly Detection. (AWS Documentation<\/a>)<\/p>\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 based on account, service, tag, charge type, etc.\n\u2192 Add split charge rules if needed\n\u2192 Activate and use in Cost Explorer\/Budgets\/CUR\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For your setup, good categories would be:<\/p>\n\n\n\n
Environment: dev, stage, uat, prod, shared\nProduct: analytics, backend, design, platform\nOwner: team \/ manager \/ cost center\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use tags when cost needs to follow resources.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
Environment=prod\nProduct=telematics\nTeam=platform\nCostCenter=engineering\nOwner=rajesh\nApplication=vehicle-service\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Output<\/th>Value<\/th><\/tr><\/thead>
Cost by tag<\/td>Showback\/chargeback<\/td><\/tr>
Tag filter in Cost Explorer<\/td>Analyze product\/team\/env cost<\/td><\/tr>
Tag columns in CUR<\/td>Data warehouse reporting<\/td><\/tr>
Budget by tag<\/td>Team\/product budget<\/td><\/tr>
Untagged cost visibility<\/td>Governance improvement<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Tag AWS resources\n\u2192 Billing and Cost Management\n\u2192 Cost Allocation Tags\n\u2192 Activate required tag keys\n\u2192 Wait for tags to appear\n\u2192 Use in Cost Explorer, Budgets, Data Exports\n<\/code><\/pre>\n\n\n\n
AWS notes that tags can take up to 24 hours to appear in the Billing and Cost Management console. (AWS Documentation<\/a>)<\/p>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Mandatory AWS tags should be enforced by Terraform\/module policy:<\/p>\n\n\n\n
Environment\nProduct\nService\nTeam\nOwner\nCostCenter\nManagedBy\nRepository\n<\/code><\/pre>\n\n\n\n
Avoid sensitive data in tags; AWS explicitly recommends not including sensitive information in tags. (AWS Documentation<\/a>)<\/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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you need:<\/p>\n\n\n\n
Custom internal rates\nPartner\/reseller billing\nChargeback to business units\nPro forma billing\nSeparate billing groups\nCustom pricing rules\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Use<\/th><\/tr><\/thead>
Billing groups<\/td>Group accounts\/customers<\/td><\/tr>
Pricing plans<\/td>Custom rates<\/td><\/tr>
Pro forma bills<\/td>Internal\/custom view<\/td><\/tr>
Custom CUR per billing group<\/td>Downstream reporting<\/td><\/tr>
Margin\/showback analysis<\/td>Compare AWS actual vs internal rates<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing Conductor\n\u2192 Create billing group\n\u2192 Add linked accounts\n\u2192 Create pricing plan\/rules\n\u2192 Assign pricing plan to billing group\n\u2192 Generate pro forma billing data\n\u2192 Export\/report to teams\/customers\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Most normal engineering teams do not need Billing Conductor. Use it if you are doing advanced chargeback, partner resale, or separate internal billing views.<\/p>\n\n\n\n
\n\n\n\n
9. Budgets and Planning<\/h1>\n\n\n\n
This section answers:<\/p>\n\n\n\n
How do we prevent surprise bills?\nHow do we alert before overspend?\nHow do we estimate future workloads?\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
9.1 Budgets<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
AWS Budgets<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use Budgets for proactive alerts:<\/p>\n\n\n\n
Actual cost > 80%\nActual cost > 100%\nForecasted cost > 100%\nService-specific budget exceeded\nEnvironment budget exceeded\nTeam budget exceeded\nSavings Plan utilization below target\nRI coverage below target\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Budget type<\/th>Use<\/th><\/tr><\/thead>
Cost budget<\/td>Dollar spend<\/td><\/tr>
Usage budget<\/td>Units such as hours, GB, requests<\/td><\/tr>
RI utilization budget<\/td>Are purchased RIs being used?<\/td><\/tr>
RI coverage budget<\/td>How much eligible usage is covered by RIs?<\/td><\/tr>
Savings Plans utilization budget<\/td>Is committed spend being consumed?<\/td><\/tr>
Savings Plans coverage budget<\/td>How much eligible usage is covered by SP?<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
AWS says Budgets information is updated up to three times per day, typically 8\u201312 hours after the previous update, and Budgets can track blended, unblended, net unblended, amortized, and net amortized costs. (AWS Documentation<\/a>)<\/p>\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\/usage\/RI\/SP type\n\u2192 Set amount and period\n\u2192 Scope by account\/service\/tag\/category if needed\n\u2192 Add actual and forecast thresholds\n\u2192 Add email\/SNS subscribers\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
Your billing alert example<\/h2>\n\n\n\n
Budget: Monthly AWS Cost Budget\nAmount: USD 2,000\n\nAlert 1: Actual > 80% = USD 1,600\nAlert 2: Actual > 100% = USD 2,000\nAlert 3: Forecasted > 100% = forecast exceeds USD 2,000\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For your AWS environment:<\/p>\n\n\n\n
Create global budget in management\/payer account.\nCreate per-environment budgets for dev\/stage\/uat\/prod.\nCreate high-risk service budgets for NAT Gateway, CloudWatch, EC2, RDS.\nRoute alerts through SNS\/email\/Slack.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
9.2 Budget Actions<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you want cost guardrails, not just alerts.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
Block new EC2 instance launches in sandbox\nRestrict expensive services after budget breach\nApply SCP to non-production account\nRequire approval before continuing\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Action type<\/th>Use<\/th><\/tr><\/thead>
IAM policy action<\/td>Restrict a role\/user\/group<\/td><\/tr>
SCP action<\/td>Restrict an AWS Organizations account\/OU<\/td><\/tr>
Manual approval<\/td>Human-controlled enforcement<\/td><\/tr>
Automatic action<\/td>Strong guardrail<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Create budget\n\u2192 Add threshold\n\u2192 Configure action\n\u2192 Choose IAM\/SCP action\n\u2192 Choose automatic or manual approval\n\u2192 Confirm required permissions\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Use Budget Actions carefully. For production, avoid automatic deny policies unless tested. For sandbox\/dev, they are very useful.<\/p>\n\n\n\n
\n\n\n\n
9.3 Budgets Reports<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Budgets Reports<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for recurring reporting:<\/p>\n\n\n\n
Weekly FinOps update\nMonthly engineering budget status\nDaily budget report during migration\nBudget health report for leadership\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Value<\/th><\/tr><\/thead>
Daily\/weekly\/monthly schedule<\/td>Automated reporting<\/td><\/tr>
Up to 50 recipients<\/td>Finance\/team distribution<\/td><\/tr>
Up to 50 reports<\/td>Multiple stakeholder groups<\/td><\/tr>
Budget performance summary<\/td>Actual\/forecast vs target<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
AWS says each budget report costs $0.01 per report delivered, regardless of recipients. (AWS Documentation<\/a>)<\/p>\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 cadence\n\u2192 Add recipients\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For your team, create one weekly report:<\/p>\n\n\n\n
AWS Weekly Budget Report\nRecipients: DevOps + Finance + Engineering leads\nCadence: Weekly Monday morning\nBudgets: Global + env budgets + high-risk service budgets\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
9.4 Pricing Calculator<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it before deploying:<\/p>\n\n\n\n
New EKS cluster\nNew Aurora database\nMore NAT Gateways\nNew CloudWatch ingestion\nNew multi-AZ architecture\nNew Savings Plan purchase\nMigration from GCP to AWS\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Estimate type<\/th>Meaning<\/th><\/tr><\/thead>
Workload estimate<\/td>Cost of a specific workload\/application\/change<\/td><\/tr>
Bill estimate<\/td>Cost impact across entire consolidated bill<\/td><\/tr>
Before-discount rates<\/td>Public On-Demand estimate<\/td><\/tr>
After-discount rates<\/td>More realistic based on your pricing<\/td><\/tr>
Commitment modeling<\/td>RI\/SP impact analysis<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
AWS says bill estimates include last month\u2019s 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<\/a>)<\/p>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Billing and Cost Management\n\u2192 Pricing Calculator\n\u2192 Choose workload estimate or bill estimate\n\u2192 Import existing usage if needed\n\u2192 Add\/change resources\n\u2192 Model commitments\n\u2192 Save\/export estimate\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
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.<\/p>\n\n\n\n
\n\n\n\n
10. Savings and Commitments<\/h1>\n\n\n\n
This section answers:<\/p>\n\n\n\n
Where can we save money?\nAre our commitments healthy?\nShould we buy Savings Plans or Reserved Instances?\nAre we wasting commitments?\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
10.1 Cost Optimization Hub<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Optimization Hub<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to find:<\/p>\n\n\n\n
Idle EC2\nUnderutilized EC2\nIdle EBS\nRightsizing opportunities\nUnused NAT Gateway-like waste patterns\nLambda optimization\nRDS rightsizing\nSavings Plans opportunities\nReserved Instance opportunities\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Feature<\/th>Value<\/th><\/tr><\/thead>
Consolidated recommendations<\/td>One place instead of many consoles<\/td><\/tr>
Estimated monthly savings<\/td>Prioritize by impact<\/td><\/tr>
Deduplication<\/td>Avoid double-counting savings<\/td><\/tr>
Filters\/grouping<\/td>Account, region, resource type, recommendation<\/td><\/tr>
API access<\/td>Automation\/reporting<\/td><\/tr>
Organization view<\/td>Multi-account optimization<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
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<\/a>)<\/p>\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 Choose standalone\/account\/org scope\n\u2192 Review opportunities\n\u2192 Filter by account\/region\/resource\/recommendation\n\u2192 Assign owners\n\u2192 Implement and track savings\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Create a weekly habit:<\/p>\n\n\n\n
Every Monday:\nReview top 10 savings opportunities\nAssign owner\nValidate risk\nImplement safe changes\nTrack realized savings\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11. Savings Plans<\/h1>\n\n\n\n
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<\/a>)<\/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
Overview is 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 underusing commitments?\nDo we need to buy more?\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Summary of owned plans\nUtilization health\nCoverage health\nSavings trend\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, savings, upcoming expirations\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to track:<\/p>\n\n\n\n
Plan type\nCommitment amount\nStart\/end date\nPayment option\nStatus\nOwning account\nQueued future purchases\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Active Savings Plans\nQueued Savings Plans\nExpiring commitments\nCSV download\nAccount vs Organization inventory\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Inventory\n\u2192 Choose Account inventory or Organization inventory\n\u2192 Review active\/queued plans\n\u2192 Download CSV 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 historical On-Demand usage and existing commitments.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you have stable compute usage and want commitment discounts.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Recommended hourly commitment\nEstimated monthly savings\nCoverage impact\nUtilization impact\nLookback-based recommendation parameters\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 estimated savings\n\u2192 Open recommendation details\n\u2192 Validate with Purchase Analyzer\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Do not blindly buy recommendations. Validate:<\/p>\n\n\n\n
Will workloads remain steady?\nAre migrations\/scale-downs coming?\nAre services moving from EC2 to Fargate\/serverless?\nIs production stable enough for commitment?\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
11.4 Savings Plans \u2014 Purchase Analyzer<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it before buying Savings Plans.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Metric<\/th>Meaning<\/th><\/tr><\/thead>
Estimated monthly savings<\/td>Expected monthly reduction<\/td><\/tr>
Coverage percentage<\/td>How much eligible usage will be covered<\/td><\/tr>
Utilization<\/td>How much commitment will be consumed<\/td><\/tr>
Risk comparison<\/td>Compare commitment scenarios<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Purchase Analyzer\n\u2192 Choose recommendation \/ target coverage \/ custom amount\n\u2192 Adjust lookback period\n\u2192 Exclude expiring plans if needed\n\u2192 Compare scenarios\n\u2192 Decide purchase amount\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to detect wasted commitments.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Utilization percentage\nUnused commitment\nNet savings\nOn-Demand equivalent spend\nFilter by account, region, plan type, family\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 Filter by account\/region\/type\n\u2192 Review utilization %\n\u2192 Investigate unused commitment\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Healthy target:<\/p>\n\n\n\n
95\u2013100% utilization for mature stable workloads\nLower utilization may be acceptable if intentionally keeping room for growth\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to find On-Demand spend that could be covered by commitments.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Coverage percentage\nEligible On-Demand spend\nCovered spend\nUncovered 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\/filter by account\/service\/region\n\u2192 Identify uncovered eligible spend\n\u2192 Review recommendations\/Purchase Analyzer\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Coverage and utilization are different:<\/p>\n\n\n\n
Utilization = Are we using what we bought?\nCoverage = How much eligible usage is protected by what we bought?\n<\/code><\/pre>\n\n\n\n
High utilization with low coverage means you are using commitments well, but may need more.<\/p>\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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it only after analysis and approval.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Plan type selection\nCommitment amount\nTerm\nPayment option\nStart date \/ queue option\nCart review\nPurchase confirmation\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Recommendations or Purchase Analyzer\n\u2192 Choose plan\n\u2192 Add to cart\n\u2192 Review cart\n\u2192 Final approval\n\u2192 Purchase\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Require approval before buying commitments:<\/p>\n\n\n\n
Requester: Platform\/FinOps\nReviewer: Finance\nApprover: Engineering\/Infra owner\nEvidence: utilization, coverage, forecast, migration roadmap\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<\/strong> is the checkout area for pending Savings Plans purchases. The \u201c0\u201d you see in the console usually means there are zero items currently in the cart.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to review before committing money.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Pending purchase list\nTerm\/payment\/commitment summary\nFinal estimated cost\nPurchase confirmation\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Savings Plans\n\u2192 Cart\n\u2192 Review selected plans\n\u2192 Confirm details\n\u2192 Purchase or remove items\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Never leave major commitment purchases to one person. Treat the cart like a financial approval checkpoint.<\/p>\n\n\n\n
\n\n\n\n
12. Reservations<\/h1>\n\n\n\n
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<\/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
Reservations Overview shows current reservations, savings, and expiring reservations.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to understand:<\/p>\n\n\n\n
How many RIs do we own?\nHow much are they saving?\nAre any expiring soon?\nAre we using them efficiently?\n<\/code><\/pre>\n\n\n\n
AWS says the Reservations Overview page shows how many reservations you have, savings compared to On-Demand, and reservations expiring this month. (AWS Documentation<\/a>)<\/p>\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 savings and expiration\n\u2192 Configure expiration alerts\n<\/code><\/pre>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
\n\n\n\n
12.2 Reservations \u2014 Recommendations<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when workloads are predictable and stable.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Recommended reservation purchases\nEstimated monthly savings\nEstimated savings vs On-Demand\nLookback parameters\nAll-account and individual-account recommendations\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 term\/offering\/payment\/lookback\n\u2192 Review estimated savings\n\u2192 Validate workload stability\n\u2192 Purchase from service-specific reservation workflow\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For EKS worker compute, Savings Plans are often more flexible than EC2 RIs. For RDS\/Aurora or Redshift, reservations may be more relevant.<\/p>\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
RI utilization measures how much of purchased reservation capacity you actually used.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to find wasted reservations.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Utilization %\nUnused reservation hours\/capacity\nSavings\nBreakdown by service\/account\/region\/instance family\n<\/code><\/pre>\n\n\n\n
High-level steps<\/h2>\n\n\n\n
Reservations\n\u2192 Utilization Report\n\u2192 Select time period\n\u2192 Filter service\/account\/region\n\u2192 Identify low utilization\n\u2192 Decide whether to modify\/sell\/avoid renewal where applicable\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Low utilization usually means:<\/p>\n\n\n\n
Workload moved\nInstance family changed\nRegion changed\nReservation purchased incorrectly\nDemand dropped\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
RI coverage measures how much eligible usage is covered by reservations versus On-Demand.<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to find eligible workloads still running On-Demand.<\/p>\n\n\n\n
What you get<\/h2>\n\n\n\n
Coverage %\nUncovered On-Demand usage\nPotential commitment opportunity\nBreakdown by service\/account\/region\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 Filter service\/account\/region\n\u2192 Identify uncovered stable usage\n\u2192 Review recommendations\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For production databases, aim for strong coverage if usage is stable. For highly dynamic compute, be more careful.<\/p>\n\n\n\n
\n\n\n\n
13. Preferences and Settings<\/h1>\n\n\n\n
This section controls billing behavior, permissions, invoice setup, tax, payment methods, and multi-organization billing relationships.<\/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 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<\/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 contact emails\nDifferent seller-of-record payment profiles\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Payment method list\nDefault payment method\nPayment profiles\nBilling contact email\nCurrency setting\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\n\u2192 Configure billing contacts\n\u2192 Configure payment profiles 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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it to configure:<\/p>\n\n\n\n
Receive PDF invoice by email\nFree Tier alerts\nCloudWatch billing alerts\nCredit sharing across accounts\nRI\/Savings Plans discount sharing\nLegacy report behavior\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\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 Edit invoice delivery preferences\n\u2192 Edit alert preferences\n\u2192 Edit credit sharing \/ discount sharing settings\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
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.<\/p>\n\n\n\n
\n\n\n\n
13.3 Cost Management Preferences<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Cost Management Preferences<\/strong> 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when operating a multi-account organization:<\/p>\n\n\n\n
Allow\/deny member accounts to see Cost Explorer data\nConfigure detailed cost data settings\nManage cost optimization preferences\nControl organizational cost visibility\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Member account cost visibility controls\nGranularity options\nCost optimization settings\nLinked account access behavior\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 linked account access\n\u2192 Configure data granularity\/options\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
For engineering teams, allow visibility to their own cost data. Hidden cost creates poor ownership.<\/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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it for:<\/p>\n\n\n\n
Tax registration number\nVAT\/GST\/JCT setup\nTax exemption management\nOrganization-wide tax inheritance\nLegal entity compliance\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Tax registration profile\nTax inheritance settings\nTax exemption status\nCountry\/region-specific tax settings\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 Enable inheritance if needed\n\u2192 Upload\/manage exemptions if applicable\n\u2192 Save\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Finance\/accounting should own this. Platform\/DevOps usually only needs awareness.<\/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 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<\/a>)<\/p>\n\n\n\n
Why use it?<\/h2>\n\n\n\n
Use it when you need:<\/p>\n\n\n\n
Separate invoices for business units\nDifferent invoice receivers\nProcurement mapping\nPO association to invoice units\nSeparate tax\/payment handling\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
Invoice units\nInvoice receivers\nAccount grouping for invoicing\nPO association\nInvoice-level configuration\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\n\u2192 Configure invoice receiver\n\u2192 Associate PO if required\n\u2192 Review invoices on Bills page\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Useful for large organizations. Not required for simple Dev\/Stage\/UAT\/Prod unless finance needs separate invoices.<\/p>\n\n\n\n
\n\n\n\n
13.6 Billing Transfer<\/h2>\n\n\n\n
What is it?<\/h2>\n\n\n\n
Billing Transfer<\/strong> 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\u2019s consolidated bill from the specified 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
AWS partners\/resellers\nMultiple AWS Organizations\nCentralized billing operations\nCommercial terms managed outside workload organization\nSeparating financial management from security governance\n<\/code><\/pre>\n\n\n\n
What you get<\/h2>\n\n\n\n
External bill-transfer account\nTransferred consolidated invoices\nBilling views\nShowback\/chargeback view with Billing Conductor\nCentralized payment management\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 Conductor pricing\/view if needed\n\u2192 Access invoices\/payments from transfer account\n<\/code><\/pre>\n\n\n\n
FinOps advice<\/h2>\n\n\n\n
Do not use Billing Transfer unless there is a clear enterprise\/partner billing reason. It changes who receives invoices and controls cost data visibility.<\/p>\n\n\n\n
\n\n\n\n
14. How all tools fit together in a real company FinOps architecture<\/h1>\n\n\n\n
For your AWS environments, I would organize it like this:<\/p>\n\n\n\n
AWS Organizations Management \/ Payer Account\n\u2502\n\u251c\u2500\u2500 Billing and Payments\n\u2502   \u251c\u2500\u2500 Bills\n\u2502   \u251c\u2500\u2500 Payments\n\u2502   \u251c\u2500\u2500 Credits\n\u2502   \u2514\u2500\u2500 Purchase Orders\n\u2502\n\u251c\u2500\u2500 Cost Visibility\n\u2502   \u251c\u2500\u2500 Home\n\u2502   \u251c\u2500\u2500 Dashboards\n\u2502   \u251c\u2500\u2500 Cost Explorer\n\u2502   \u2514\u2500\u2500 Saved Reports\n\u2502\n\u251c\u2500\u2500 Cost Allocation\n\u2502   \u251c\u2500\u2500 Cost Allocation Tags\n\u2502   \u251c\u2500\u2500 Cost Categories\n\u2502   \u2514\u2500\u2500 Billing Conductor only if showback\/chargeback is advanced\n\u2502\n\u251c\u2500\u2500 Cost Governance\n\u2502   \u251c\u2500\u2500 Budgets\n\u2502   \u251c\u2500\u2500 Budget Reports\n\u2502   \u2514\u2500\u2500 Cost Anomaly Detection\n\u2502\n\u251c\u2500\u2500 Historical Data\n\u2502   \u251c\u2500\u2500 Data Exports \/ CUR 2.0\n\u2502   \u251c\u2500\u2500 S3\n\u2502   \u251c\u2500\u2500 Athena\n\u2502   \u2514\u2500\u2500 QuickSight \/ Datadog Cloud Cost Management\n\u2502\n\u251c\u2500\u2500 Optimization\n\u2502   \u251c\u2500\u2500 Cost Optimization Hub\n\u2502   \u251c\u2500\u2500 Savings Plans\n\u2502   \u2514\u2500\u2500 Reservations\n\u2502\n\u2514\u2500\u2500 Settings\n    \u251c\u2500\u2500 Payment Preferences\n    \u251c\u2500\u2500 Billing Preferences\n    \u251c\u2500\u2500 Cost Management Preferences\n    \u251c\u2500\u2500 Tax Settings\n    \u251c\u2500\u2500 Invoice Configuration\n    \u2514\u2500\u2500 Billing Transfer\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
15. Recommended setup order for your AWS environments<\/h1>\n\n\n\n
Do this in order:<\/p>\n\n\n\n
Phase 1 \u2014 Foundation<\/h2>\n\n\n\n
1. Confirm AWS Organizations management\/payer account.\n2. Activate IAM billing access.\n3. Create IAM roles for FinOps\/Admin\/ReadOnly.\n4. Configure Billing Preferences.\n5. Configure Payment 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 Control<\/h2>\n\n\n\n
16. Create global monthly AWS budget.\n17. Create per-environment budgets.\n18. Create high-risk service budgets.\n19. Enable Cost Anomaly Detection.\n20. Configure SNS\/email\/Slack routing.\n21. Create Budget Reports.\n<\/code><\/pre>\n\n\n\n
Phase 5 \u2014 Optimization<\/h2>\n\n\n\n
22. Enable Cost Optimization Hub.\n23. Review top recommendations weekly.\n24. Review Savings Plans coverage\/utilization.\n25. Review Reservation coverage\/utilization.\n26. Use Pricing Calculator before major architecture changes.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
16. For your immediate billing-alert requirement<\/h1>\n\n\n\n
For your specific requirement:<\/p>\n\n\n\n
Actual cost > 80% of USD 2000\nActual cost > 100% of USD 2000\nForecast cost > 100% of USD 2000\n<\/code><\/pre>\n\n\n\n
Use this:<\/p>\n\n\n\n
Primary tool: AWS Budgets\nScope: Management \/ payer account\nBudget type: Cost budget\nPeriod: Monthly\nAmount: USD 2,000\nNotifications:\n  - Actual > 80%\n  - Actual > 100%\n  - Forecasted > 100%\nDelivery:\n  - Email\n  - SNS topic\n  - Optional Slack\/Datadog integration\n<\/code><\/pre>\n\n\n\n
Do not<\/strong> 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.<\/p>\n\n\n\n
\n\n\n\n
17. Best-practice operating cadence<\/h1>\n\n\n\n
Daily<\/h2>\n\n\n\n
Check Home\nCheck Cost Anomaly Detection\nCheck major cost spikes\n<\/code><\/pre>\n\n\n\n
Weekly<\/h2>\n\n\n\n
Review Cost Explorer trends\nReview budget status\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 and invoices\nReview actual vs budget\nReview credits\nReview Savings Plans utilization\/coverage\nReview RI utilization\/coverage\nReview top services and top accounts\nReview CUR\/Datadog\/QuickSight reports\n<\/code><\/pre>\n\n\n\n
Quarterly<\/h2>\n\n\n\n
Review commitment strategy\nReview account\/tag\/category model\nReview showback\/chargeback\nReview forecast vs actual accuracy\nReview architecture cost changes\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
18. Final cheat sheet<\/h1>\n\n\n\n
Need<\/th>Use this AWS feature<\/th><\/tr><\/thead>
See invoice<\/td>Bills<\/td><\/tr>
See payment status<\/td>Payments<\/td><\/tr>
See credits<\/td>Credits<\/td><\/tr>
Put PO on invoice<\/td>Purchase Orders<\/td><\/tr>
Quick financial overview<\/td>Home<\/td><\/tr>
Custom visual reports<\/td>Dashboards<\/td><\/tr>
Investigate cost<\/td>Cost Explorer<\/td><\/tr>
Save repeated analysis<\/td>Cost Explorer Saved Reports<\/td><\/tr>
Detect unusual spikes<\/td>Cost Anomaly Detection<\/td><\/tr>
Track Free Tier<\/td>Free Tier<\/td><\/tr>
Store detailed historical cost<\/td>Data Exports \/ CUR 2.0<\/td><\/tr>
ESG\/carbon reporting<\/td>Carbon emissions<\/td><\/tr>
Map cost to business units<\/td>Cost Categories<\/td><\/tr>
Map cost to resources\/teams\/env<\/td>Cost Allocation Tags<\/td><\/tr>
Custom internal billing<\/td>Billing Conductor<\/td><\/tr>
Alert on budget thresholds<\/td>Budgets<\/td><\/tr>
Email budget performance<\/td>Budgets Reports<\/td><\/tr>
Estimate future workloads<\/td>Pricing Calculator<\/td><\/tr>
Find savings opportunities<\/td>Cost Optimization Hub<\/td><\/tr>
Manage compute commitments<\/td>Savings Plans<\/td><\/tr>
Manage service reservations<\/td>Reservations<\/td><\/tr>
Manage payment methods<\/td>Payment Preferences<\/td><\/tr>
Manage invoice\/alerts\/credit sharing<\/td>Billing Preferences<\/td><\/tr>
Control member account cost visibility<\/td>Cost Management Preferences<\/td><\/tr>
Manage tax IDs\/exemptions<\/td>Tax Settings<\/td><\/tr>
Separate invoices by unit<\/td>Invoice Configuration<\/td><\/tr>
Centralize billing across organizations<\/td>Billing Transfer<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
For your case, the most important first three are:<\/p>\n\n\n\n
1. AWS Budgets\n2. Cost Explorer\n3. Data Exports \/ CUR 2.0\n<\/code><\/pre>\n\n\n\n
Then add:<\/p>\n\n\n\n
4. Cost Allocation Tags\n5. Cost Categories\n6. Cost Anomaly Detection\n7. Cost Optimization Hub\n8. Dashboards \/ Datadog\n<\/code><\/pre>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Below is a master guide to AWS Billing and Cost Management, written like a complete FinOps tutorial. I\u2019ll map every menu item you listed and explain: Master… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1033","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/1033","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=1033"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/1033\/revisions"}],"predecessor-version":[{"id":1034,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/1033\/revisions\/1034"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=1033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=1033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=1033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}