Arkinu
AWS service comparison

AWS Budgets vs AWS Cost Explorer: differences and when to use each

AWS Budgets
AWS Cost Explorer

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

AWS Cost Management

AWS Budgets

Service for setting cost or usage budgets and receiving alerts by email or Amazon SNS when actual or forecasted spend exceeds the threshold. It can also run actions, such as applying an IAM policy that prevents creating more resources.

Exam phrases that point here

  • «get an alert when actual or forecasted spend exceeds a defined amount»

    AWS Budgets compares cost or usage with an amount you set and notifies you by email or through an Amazon SNS topic when the threshold is crossed, both with spend that has already occurred and with the forecasted spend for the period.

    When not: If there is no fixed amount and the goal is to discover unusual spend that nobody expected, AWS Cost Anomaly Detection fits better. If you only want to watch a technical metric, such as CPU utilization, the alarm is an Amazon CloudWatch one.

  • «automatically prevent more resources from being created once the budget is exceeded»

    Budget actions let AWS Budgets, when a threshold is crossed, apply a restrictive IAM policy or an SCP on its own, without waiting for someone to react to the email.

    When not: An SCP can only be applied by the AWS Organizations management account. If the requirement is a permanent preventive control that does not depend on spend, think directly of SCPs or IAM policies, not a budget.

  • «stop development instances when spend reaches the limit»

    A budget action can target specific Amazon EC2 or Amazon RDS instances and stop them when the threshold is reached, automatically or after approval from an approver.

    When not: Billing data arrives with a delay, so spend can keep rising before the action runs: it is not a hard cap. To turn instances on and off on a fixed schedule, the pattern is a scheduler (for example, Amazon EventBridge Scheduler), not a budget.

  • «get notified when the utilization or coverage of Savings Plans or Reserved Instances drops»

    AWS Budgets has specific utilization and coverage budgets for Reserved Instances and Savings Plans, which alert when the percentage falls below the target.

    When not: If the ask is to decide how much to commit or what to buy, that is the purchase recommendations that AWS Cost Explorer shows, not a budget.

  • «control spend by account, by service, or by project with a monthly limit»

    A budget can be filtered by dimensions such as service or member account and measured by month, quarter, or year, or over a custom period.

    When not: If the question is about understanding what the money was spent on and seeing trends in charts, the tool is AWS Cost Explorer; Budgets watches against an amount and is not meant for exploring.

Often paired with

  • Amazon SNS
Study AWS Budgets →

AWS Cost Management

AWS Cost Explorer

Tool for viewing and analyzing your AWS costs and usage with charts and reports. It shows up to 13 months of history by default (extendable to 38 months with monthly data), forecasts spend for the next 18 months, and recommends which Reserved Instances to purchase.

Exam phrases that point here

  • «visualize and analyze the costs of the past few months by service or by account»

    AWS Cost Explorer shows cost and usage in charts and reports, with up to 13 months of history by default (extendable to 38 months with monthly data), and lets you filter and group by service, Region, or member account without setting anything up.

    When not: If you need line-by-line detail, by the hour and by resource, to load into your own tools, the answer is the AWS Cost and Usage Report (through AWS Data Exports). If you want an alert when an amount is exceeded, it is AWS Budgets.

  • «find out how much each team or project spends based on their tags»

    With cost allocation tags turned on, Cost Explorer can filter and group spend by those tags, for example project or cost center.

    When not: The tags must be applied to the resources and activated in the billing console; before that they do not appear in the analysis. If you also want to split the cost of Amazon ECS containers based on their consumption, you need the detail of the Cost and Usage Report.

  • «forecast spend for the coming months based on historical usage»

    Cost Explorer calculates a forecast based on past spending patterns: monthly up to 18 months and daily up to 3 months.

    When not: If the goal is to act when a forecasted spend is reached (alert or restrict), that is configured in AWS Budgets. To estimate the cost of an architecture that does not exist yet, AWS Pricing Calculator is used, not Cost Explorer.

  • «recommendations on which Reserved Instances or Savings Plans to purchase»

    Cost Explorer analyzes historical usage and recommends Reserved Instance purchases and the right Savings Plans commitment, and then shows utilization and savings reports.

    When not: If the question is whether the instances are the right size (rightsizing) and not which commitment to buy, AWS Compute Optimizer gives more specific recommendations. The discount itself comes from the Savings Plan or the Reserved Instance, not from Cost Explorer.

Study AWS Cost Explorer →