# Creating a budget


You can create budgets to track and take action on your costs and usage. You can also create budgets to track your aggregate Reserved Instance (RI) and Savings Plans utilization and coverage. By default, single accounts, the management account, and member accounts in an organization can create budgets.

When you create a budget, AWS Budgets provides a Cost Explorer graph to help you see your incurred costs and usage. If you didn't enable Cost Explorer yet, this graph is blank and AWS Budgets will enable Cost Explorer when you create your first budget. You can create your budget without enabling Cost Explorer. It can take up to 24 hours for this graph to appear after you or AWS Budgets enable Cost Explorer.

You can create and set up a budget in two ways:
+ [Using a budget template (simplified)](budget-templates.md)
+ [Customizing a budget (advanced)](custom-budgets.md)

## Billing view prerequisites and monitoring


AWS Budgets supports billing views, allowing you to create and manage budgets based on filtered cost and usage data across multiple accounts within your organization. When creating a budget, you can select a billing view to define the scope of cost and usage data the budget will track. For more information on controlling access to cost management data using billing views, see [Controlling cost management data access with Billing View](https://docs.aws.amazon.com/cost-management/latest/userguide/billing-view.html).

**Note**  
AWS doesn't support billing transfer views for bill transfer accounts.

Before you use billing views with budgets, consider the following permissions requirements:
+ For cross-account billing views, the source account administrator must grant:
  + `budgets:ModifyBudget` permission on the billing view to allow target accounts/users to create budgets
  + `billing:GetBillingViewData` permission to access the billing view data
+ Target accounts/users also need:
  + `iam:CreateServiceLinkedRole` permission for the Budgets service principal (budgets.amazonaws.com):
+ The service-linked role monitors the health status of your billing view access:
  + `HEALTHY`: Indicates the budget has proper access to the billing view data
  + `UNHEALTHY`: Indicates the budget cannot access the billing view data, which might occur if permissions have been revoked or the view has been deleted. Reasons for unhealthy status can be:
    + `BILLING_VIEW_NO_ACCESS`: Indicates that access to the billing view associated with the budget has been removed (unshared) or the view was deleted.
    + `INVALID_FILTER`: Indicates that the budget's filter is invalid. This occurs when a management account becomes a linked account but has a budget that references an account outside their organization. In this situation, budget spend updates are paused.

## Tutorials


You can also use our [walk-through tutorials](https://console.aws.amazon.com/billing/home#/budgets/overview?tutorials=visible) to learn how to achieve your objectives with AWS Budgets.

**To access tutorials**

1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/cost-management/](https://console.aws.amazon.com/cost-management/).

1. In the navigation pane, choose **Budgets**.

1. Next to **Overview**, choose **Info**.

1. In the help panel, choose **Tutorials**.

# Using a budget template (simplified)


You can create a budget using a template with recommended configurations. Budget templates are a simplified way to start using AWS Budgets, with a single page workflow, unlike the 5-step workflow that is required for [Customizing a budget (advanced)](custom-budgets.md).

**To create a budget using a template**

1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/cost-management/](https://console.aws.amazon.com/cost-management/).

1. In the navigation pane, choose **Budgets**.

1. At the top of the page, choose **Create budget**.

1. Under **Budget setup**, choose **Use a template (simplified)**.

1. Under **Templates**, choose a template that best matches your use case:
   + **Zero spend budget**: A budget that notifies you after your spending exceeds AWS Free Tier limits.
   + **Monthly cost budget**: A monthly budget that notifies you if you exceed, or are forecasted to exceed, the budget amount.
   + **Daily Savings Plans coverage budget**: A coverage budget for your Savings Plans that notifies you when you fall below the defined target. This helps you to identify your on-demand spend sooner so that you can consider purchasing a new commitment.
   + **Daily reservation utilization budget**: A utilization budget for your Reserved Instances that notifies you when you fall below the defined target. This helps you to identify when you're not using some of your hourly commitment that you already purchased.

1. Update the details and settings for your specific template.

1. Choose **Create budget**.

While each template has default configurations, they can be changed later. This way, you can use it to create most of the budget, and then edit certain settings in the advanced workflow, such as adding a linked account or a cost category filter. To change any of the settings, under **Template settings**, choose **Custom**.

You can also download a template for offline use in [AWS CLI](https://aws.amazon.com/cli/) or [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Budgets.html), for example. To download a template, under **Template settings**, choose **JSON**.

# Customizing a budget (advanced)


You can customize a budget to set parameters specific to your use case. You can customize the time period, the start month, and specific accounts. Creating a customized budget involves a 5-step workflow.

You can choose between four main budget types that track against the following:
+ Cost (see [Creating a cost budget](create-cost-budget.md))
+ Usage (see [Creating a usage budget](create-usage-budget.md))
+ Savings Plans (see [Creating a Savings Plans budget](create-savingsplans-budget.md))
  + Savings Plans utilization
  + Savings Plans coverage
+ Reservation (see [Creating a reservation budget](create-reservation-budget.md))
  + Reservation utilization
  + Reservation coverage

# Creating a cost budget


Use this procedure to create a budget that's based on your costs.<a name="cost-budget"></a>

**To create a cost budget**

1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/cost-management/](https://console.aws.amazon.com/cost-management/).

1. In the navigation pane, choose **Budgets**.

1. At the top of the page, choose **Create budget**.

1. Under **Budget setup**, choose **Customize (advanced)**.

1. Under **Budget types**, choose **Cost budget**. Then, choose **Next**.

1. Under **Details**, for **Budget name**, enter the name of your budget. Your budget name must be unique within your account. It can contain A-Z, a-z, spaces, and the following characters:

   ```
   _.:/=+-%@
   ```

1. Under **Set budget amount**, for **Period**, choose how often you want the budget to reset the actual and forecasted spend. 
   + **Daily** for every day
   + **Monthly** for every month
   + **Quarterly** for every three months
   + **Annually** for every 12 months
   + **Custom** to specify your own start and end dates
**Note**  
With a **Monthly** or **Quarterly** budget period, you can set future budgeted amounts using the budget planning feature. **Custom** period budgets align with time periods outside of standard reset options. For example, you can create a budget period that matches your fiscal year or project timeline.

1. For **Budget renewal type**, choose **Recurring budget** for a budget that resets after the budget period. Or, choose **Expiring budget** for a one-time budget that doesn't reset after the budget period.

1. Choose the start date or period to begin tracking against your budgeted amount. For an **Expiring budget**, choose the end date or period for the budget to end on.

   All budget times are in the UTC format.

1. For **Budgeting method**, select the way that you want your budget amount to be determined each budget period:
   + **Fixed**: Set one amount to monitor every budget period.
   + **Planned**: Set different amounts to monitor each budget period.
   + **Auto-adjusting**: Set your budget amount to be adjusted automatically based on your spending pattern over a time range that you specify.

   For more information about each method, see [Budget methods](budget-methods.md)

1. Enter your budgeted amount for the selected period. This is the value the budget will track against.

1. (Optional) Under **Budget scope**, for **Filters**, choose **Add filter** to apply one or more of the [available filters](budgets-create-filters.md). Your choice of budget type determines the set of filters that's displayed on the console.
**Note**  
You can't use the **Linked account** filter within a linked account.

1. (Optional) **Under Budget scope**, for **Advanced options**, choose how to aggregate costs:
   + **Use blended costs**: View averaged costs across accounts with evenly distributed Reserved Instance and Savings Plans benefits. Useful for organizations sharing commitment benefits.
   + **Use unblended costs**: View actual resource costs charged at time of usage. Suitable for individual account tracking.
   + **Use net unblended costs**: View actual costs after all discounts and credits are applied. Helps with monitoring final costs.
   + **Use amortized costs**: View costs with upfront and recurring payments spread across the term. Assists in consistent month-to-month budget planning.
   + **Use net amortized costs**: View spread payments with all discounts and credits applied. Supports long-term budget planning.

1. Choose **Next**.

1. Choose **Add an alert threshold**.

1. Under **Set alert threshold**, for **Threshold**, enter the amount that must be reached for you to be notified. This can be either an absolute value or a percentage. For example, say you have a budget of 200 dollars. To be notified at 160 dollars (80% of your budget), enter **160** for an absolute budget or **80** for a percentage budget.

   Next to the amount, choose **Absolute value** to be notified when your costs exceed the threshold amount. Or, choose **% of budgeted amount** to be notified when your costs exceed the threshold percentage.

   Next to the threshold, choose **Actual** to create an alert for actual spend. Or, choose **Forecasted** to create an alert for forecasted spend.

1. (Optional) Under **Notification preferences**, for **Email recipients**, enter the email addresses that you want the alert to notify. Separate multiple email addresses with commas. A notification can be sent to a maximum of 10 email addresses.

1. (Optional) Under **Notification preferences**, for **Amazon SNS Alerts**, enter the Amazon Resource Name (ARN) for your Amazon SNS topic. For instructions on how to create a topic, see [Creating an Amazon SNS topic for budget notifications](budgets-sns-policy.md).
**Important**  
After you create a budget with Amazon SNS notifications, Amazon SNS sends a confirmation email to the email addresses that you specified. The subject line is **AWS Notification - Subscription Confirmation**. The recipient must choose **Confirm subscription** in the confirmation email to receive future notifications.

1. (Optional) Under **Notification preferences**, for **AWS Chatbot Alerts**, you can choose to configure AWS Chatbot to send budget alerts to an Amazon Chime or Slack chat room. You configure these alerts on the AWS Chatbot console.

1. Choose **Next**.

1. (Optional) For **Attach actions**, you can configure an action that AWS Budgets performs on your behalf when the alert threshold is exceeded. For more information and instructions, see [To configure a budget action](budgets-action-configure.md#create-budget-action).

1. Choose **Next**.
**Note**  
To proceed, you must configure at least one of the following parameters for each alert:  
An email recipient for notifications
An Amazon SNS topic for notifications
A budget action

1. Review your budget settings, and then choose **Create budget**.

# Creating a usage budget


Use this procedure to create a budget that's based on your usage.<a name="usage-budget"></a>

**To create a usage budget**

1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/cost-management/](https://console.aws.amazon.com/cost-management/).

1. In the navigation pane, choose **Budgets**.

1. At the top of the page, choose **Create budget**.

1. Under **Budget setup**, choose **Customize (advanced)**.

1. Under **Budget types**, choose **Usage budget**. Then, choose **Next**.

1. Under **Details**, for **Budget name**, enter the name of your budget. Your budget name must be unique within your account. It can contain A-Z, a-z, spaces, and the following characters:

   ```
   _.:/=+-%@
   ```

1. Under **Choose what you’re budgeting against**, for **Budget against**, choose **Usage type groups** or **Usage types**. A usage type group is a collection of usage types that have the same unit of measure. For example, resources that measure usage by the hour is one usage type group.
   + For **Usage type groups**, choose the unit of measurement and the applicable service usage that you want the budget to monitor.
   + For **Usage types**, choose the specific service usage measurements that you want the budget to monitor.

1. Under **Set budget amount**, for **Period**, choose how often you want the budget to reset the actual and forecasted usage.
   + **Daily** for every day
   + **Monthly** for every month
   + **Quarterly** for every three months
   + **Annually** for every 12 months
   + **Custom** to specify your own start and end dates
**Note**  
With a **Monthly** or **Quarterly** budget period, you can set future budgeted amounts using the budget planning feature. **Custom** period budgets align with time periods outside of standard reset options. For example, you can create a budget period that matches your fiscal year or project timeline.

1. For **Budget renewal type**, choose **Recurring budget** for a budget that resets at the end of each budget period. Or, choose **Expiring budget** for a one-time budget that doesn't reset after the given budget period.

1. Choose the start date or period to begin tracking against your budgeted amount. For an **Expiring budget**, choose the end date or period for the budget to end on.

   All budget times are in the UTC format.

1. For **Budgeting method**, select the way that you want your budget amount to be determined each budget period:
   + **Fixed**: Set one amount to monitor every budget period.
   + **Planned**: Set different amounts to monitor each budget period.
   + **Auto-adjusting**: Set your budget amount to be adjusted automatically based on your usage pattern over a time range that you specify.

   For more information about each method, see [Budget methods](budget-methods.md)

1. (Optional) Under **Budget scope**, for **Filters**, choose **Add filter** to apply one or more of the [available filters](budgets-create-filters.md). Your choice of budget type determines the set of filters that's displayed on the console.
**Note**  
You can't use the **Linked account** filter within a linked account.

1. Choose **Next**.

1. Choose **Add an alert threshold**.

1. Under **Set alert threshold**, for **Threshold**, enter the amount that must be reached for you to be notified. This can be either an absolute value or a percentage. For example, say you have a budget of 200 hours. To be notified at 160 hours (80% of your budget), enter **160** for an absolute budget or **80** for a percentage budget.

   Next to the amount, choose **Absolute value** to be notified when your usage exceeds the threshold amount. Or, choose **% of budgeted amount** to be notified when your usage exceeds the threshold percentage.

   Next to the threshold, choose **Actual** to create an alert for actual usage. Or, choose **Forecasted** to create an alert for forecasted usage.

1. (Optional) Under **Notification preferences**, for **Email recipients**, enter the email addresses that you want the alert to notify. Separate multiple email addresses with commas. A notification can be sent to a maximum of 10 email addresses.

1. (Optional) Under **Notification preferences**, for **Amazon SNS Alerts**, enter the Amazon Resource Name (ARN) for your Amazon SNS topic. For instructions on how to create a topic, see [Creating an Amazon SNS topic for budget notifications](budgets-sns-policy.md).
**Important**  
After you create a budget with Amazon SNS notifications, Amazon SNS sends a confirmation email to the email addresses that you specified. The subject line is **AWS Notification - Subscription Confirmation**. The recipient must choose **Confirm subscription** in the confirmation email to receive future notifications.

1. (Optional) Under **Notification preferences**, for **AWS Chatbot Alerts**, you can choose to configure AWS Chatbot to send budget alerts to an Amazon Chime or Slack chat room. You configure these alerts on the AWS Chatbot console.

1. Choose **Next**.

1. (Optional) For **Attach actions**, you can configure an action that AWS Budgets performs on your behalf when the alert threshold is exceeded. For more information and instructions, see [To configure a budget action](budgets-action-configure.md#create-budget-action).

1. Choose **Next**.
**Note**  
To proceed, you must configure at least one of the following parameters for each alert:  
An email recipient for notifications
An Amazon SNS topic for notifications
A budget action

1. Review your budget settings, and then choose **Create budget**.

# Creating a Savings Plans budget


Use this procedure to create a budget that's specifically for Savings Plans utilization or coverage.

**Note**  
It can take up to 48 hours for Savings Plans utilization and coverage metrics to generate, which is longer than the time frame for cost and usage data.<a name="savingsplans-budget"></a>

**To create a Savings Plans budget**

1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/cost-management/](https://console.aws.amazon.com/cost-management/).

1. In the navigation pane, choose **Budgets**.

1. At the top of the page, choose **Create budget**.

1. Under **Budget setup**, choose **Customize (advanced)**.

1. Under **Budget types**, choose **Savings Plans budget**. Then, choose **Next**.

1. Under **Details**, for **Budget name**, enter the name of your budget. Your budget name must be unique within your account. It can contain A-Z, a-z, spaces, and the following characters:

   ```
   _.:/=+-%@
   ```

1. Under **Utilization threshold**, for **Period**, choose how often you want the budget to reset the tracked utilization or coverage. 
   + **Daily** for every day
   + **Monthly** for every month
   + **Quarterly** for every three months
   + **Annually** for every 12 months
   + **Custom** to specify your own start and end dates

   All budget times are in the UTC format.
**Note**  
**Custom** period budgets align with time periods outside of standard reset options. For example, you can create a budget period that matches your fiscal year or project timeline.

1. For **Monitor my spend against**, choose **Utilization of Savings Plans** to track how much of your Savings Plans you used. Or, choose **Coverage of Savings Plans** to track how much of your instance usage is covered by Savings Plans.

   For **Utilization threshold**, enter the utilization percentage that you want AWS to notify you at. For example, for a utilization budget where you want to stay above 90% Savings Plans utilization, enter **90**. The budget notifies you when your overall Savings Plans utilization is below 90%.

   For **Coverage threshold**, enter the coverage percentage that you want AWS to notify you at. For example, for a coverage budget where you want to stay above 80%, enter **80**. The budget notifies you when your overall coverage is below 80%.

1. (Optional) Under **Budget scope**, for **Filters**, choose **Add filter** to apply one or more of the [available filters](budgets-create-filters.md). Your choice of budget type determines the set of filters that's displayed on the console.
**Note**  
You can't use the **Linked account** filter within a linked account.

1. Choose **Next**.

1. Under **Notification preferences**, for **Email recipients**, enter the email addresses that you want the alert to notify. Separate multiple email addresses with commas. A notification can be sent to a maximum of 10 email addresses.

1. (Optional) For **Amazon SNS Alerts**, enter the Amazon Resource Name (ARN) for your Amazon SNS topic. For instructions on how to create a topic, see [Creating an Amazon SNS topic for budget notifications](budgets-sns-policy.md).
**Important**  
After you create a budget with Amazon SNS notifications, Amazon SNS sends a confirmation email to the email addresses that you specified. The subject line is **AWS Notification - Subscription Confirmation**. The recipient must choose **Confirm subscription** in the confirmation email to receive future notifications.

1. (Optional) For **AWS Chatbot Alerts**, you can choose to configure AWS Chatbot to send budget alerts to an Amazon Chime or Slack chat room. You configure these alerts through the AWS Chatbot console.

1. Choose **Next**.
**Note**  
To proceed, you must configure at least one email recipient or an Amazon SNS topic for notifications.

1. Review your budget settings, and then choose **Create budget**.

# Creating a reservation budget


Use this procedure to create a budget for RI utilization or coverage.

**Note**  
It can take up to 48 hours for Reservations utilization and coverage metrics to generate, which is longer than the time frame for cost and usage data.<a name="reservation-budget"></a>

**To create a reservation budget**

1. Open the Billing and Cost Management console at [https://console.aws.amazon.com/cost-management/](https://console.aws.amazon.com/cost-management/).

1. In the navigation pane, choose **Budgets**.

1. At the top of the page, choose **Create budget**.

1. Under **Budget setup**, choose **Customize (advanced)**.

1. Under **Budget types**, choose **Reservation budget**. Then, choose **Next**.

1. Under **Details**, for **Budget name**, enter the name of your budget. Your budget name must be unique within your account. It can contain A-Z, a-z, spaces, and the following characters:

   ```
   _.:/=+-%@
   ```

1. Under **Utilization threshold**, for **Period**, choose how often you want the budget to reset the tracked utilization or coverage. 
   + **Daily** for every day
   + **Monthly** for every month
   + **Quarterly** for every three months
   + **Annually** for every 12 months
   + **Custom** to specify your own start and end dates

   All budget times are in the UTC format.
**Note**  
**Custom** period budgets align with time periods outside of standard reset options. For example, you can create a budget period that matches your fiscal year or project timeline.

1. For **Monitor my spend against**, choose **Utilization of reservations** to track how much of your reservation you used. Or, choose **Coverage of reservations** to track how much of your instance usage is covered by reservations.

1. For **Service**, choose the service that you want the budget to track.

1. For **Utilization threshold**, enter the utilization percentage that you want AWS to notify you at. For example, for a utilization budget where you want to stay above 90% RI utilization, enter **90**. The budget notifies you when your overall RI utilization is below 90%.

   For **Coverage threshold**, enter the coverage percentage that you want AWS to notify you at. For example, for a coverage budget where you want to stay above 80%, enter **80**. The budget notifies you when your overall coverage is below 80%.

1. (Optional) Under **Budget scope**, for **Filters**, choose **Add filter** to apply one or more of the [available filters](budgets-create-filters.md). Your choice of budget type determines the set of filters that's displayed on the console.
**Note**  
You can't use the **Linked account** filter within a linked account.

1. Choose **Next**.

1. Under **Notification preferences**, for **Email recipients**, enter the email addresses that you want the alert to notify. Separate multiple email addresses with commas. A notification can be sent to a maximum of 10 email addresses.

1. (Optional) For **Amazon SNS Alerts**, enter the Amazon Resource Name (ARN) for your Amazon SNS topic. For instructions on how to create a topic, see [Creating an Amazon SNS topic for budget notifications](budgets-sns-policy.md).
**Important**  
After you create a budget with Amazon SNS notifications, Amazon SNS sends a confirmation email to the email addresses that you specified. The subject line is **AWS Notification - Subscription Confirmation**. The recipient must choose **Confirm subscription** in the confirmation email to receive future notifications.

1. (Optional) For **AWS Chatbot Alerts**, you can choose to configure AWS Chatbot to send budget alerts to an Amazon Chime or Slack chat room. You configure these alerts through the AWS Chatbot console.

1. Choose **Next**.
**Note**  
To proceed, you must configure at least one email recipient or an Amazon SNS topic for notifications.

1. Review your budget settings, and then choose **Create budget**.

# Budget methods


You can set the budgeted amount of your cost or usage budget in one of the following ways. You can set one of these budgets no matter whether you're budgeting in a traditional sense—tracking to plan, for example—or if you want to monitor spend and receive alerts when costs increase beyond your threshold.

**Fixed**  
With a fixed budget, you can monitor the same amount every budget period. For example, you can use a cost budget with the fixed method to monitor your costs against \$1100 every budget period.

**Planned**  
The planned budgeting method is available for only monthly or quarterly budgets. With a planned budget, you can set a different amount to monitor each budget period. For example, you can use a monthly cost budget with the planned method to monitor your costs against \$1100 in the first month, \$1110 in the second month, and other amounts in the remaining months.  
With a planned budget, you can set the budget amount for up to 12 months or 4 quarters. After 12 months or 4 quarters, your budget amount is fixed at the last budget amount.

**Auto-adjusting**  
An auto-adjusting budget dynamically sets your budget amount based on your spending or usage over a time range that you specify. The historical or forecast time range that you select is the auto-adjustment baseline for your budget.  
At the beginning of each new period, AWS Budgets calculates your budget amount from your cost or usage data within the baseline time range. Make sure to select a time range that best matches your expectations for your account’s AWS costs or usage. If you select a time range with lower usage than you typically expect, then you might get more budget alerts than you need. If you select a time range with higher usage than you typically expect, then you might not get as many budget alerts as you need.  
For example, you can create an auto-adjusting cost budget with a baseline time range of the last six months. In this scenario, if your average spending each budget period in the last six months was \$1100, your auto-adjusted budget amount in the new period is \$1100.  
If AWS Budgets updates your budget amount based on changes in your spending or usage, all budget alert notification subscribers get a notification that the budget amount changed.  
+ When calculating your auto-adjusted budget amount, AWS Budgets doesn't include periods at the beginning of your baseline time range that don't have cost or usage data. For example, assume that you set your baseline time range as the last four quarters. However, your account had no cost data in the first quarter. Then, in this case, AWS Budgets calculates your auto-adjusted budget amount from only the last three quarters.
+ You see a temporary forecast while you're creating or editing a budget. After you save your budget, your auto-adjusted budget is set for the first time.

# Budget filters


Based on your choice of budget type, you can choose one or more of the available budget filters.

**API operation**  
Choose an action, such as `CreateBucket`.

**Availability zone**  
Choose the `Availability zone` in which the resource that you want to create a budget for is running.

**Billing entity**  
Helps you identify whether your invoices or transactions are for AWS Marketplace or for purchases of other AWS services. Possible values include:  
+ AWS: Identifies a transaction for AWS services other than in AWS Marketplace.
+ AWS Marketplace: Identifies a purchase in AWS Marketplace.

**Charge type**  
Different types of charges or fees.  
+ **Credit**: Any AWS credits that are applied to your account.
+ **Other out-of-cycle charges**: Any subscription charges that aren't upfront reservation charges or support charges.
+ **Recurring reservation fee**: Any recurring charges to your account. When you purchase a Partial Upfront or No Upfront Reserved Instance from AWS, you pay a recurring charge in exchange for a lower rate for using the instance. The recurring fees can result in spikes on the first day of every month, when AWS charges your account.
+ **Refund**: Any refunds that you received. Refunds are listed as a separate line item in the data table. They don't appear as an item in the chart because they represent a negative value in the calculation of your costs. The chart displays only positive values.
+ **Reservation applied usage**: Usage that AWS applied reservation discounts to.
+ **Savings Plan covered usage**: Any on-demand cost that's covered by your Savings Plan. In an Unblended costs view, this represents the covered usage at on-demand rates. In an Amortized costs view, this represents the covered usage at your Savings Plan rates. Savings Plan covered usage line items are offset by the corresponding Savings Plan negation items.
+ **Savings Plan negation**: Any offset cost through your Savings Plan benefit that’s associated with the corresponding Savings Plan covered usage item.
+ **Savings Plan recurring fee**: Any recurring hourly charges that correspond with your No Upfront or Partial Upfront Savings Plan. The Savings Plan recurring fee is initially added to your bill on the day that you purchase a No Upfront or Partial Upfront Savings Plan. After the initial purchase, AWS adds the recurring fee hourly. For an All Upfront Savings Plan, the line item indicates the portion of the Savings Plan unused during the billing period. For example, if a Savings Plan was 100% utilized for a billing period, this shows as “0” in your amortized costs view. Any number greater than “0” indicates an unused Savings Plan.
+ **Savings Plan upfront fee**: Any one-time upfront fee from your purchase of an All Upfront or Partial Upfront Savings Plan.
+ **Support fee**: Any charges that AWS charges you for a support plan. When you purchase a support plan from AWS, you pay a monthly charge in exchange for service support. The monthly fees can result in spikes on the first day of every month, when AWS charges your account.
+ **Tax**: Any taxes that are associated with the charges or fees in your cost chart. Cost Explorer adds all taxes together as a single component of your costs. If you select five or fewer filters, Cost Explorer displays your tax expenses as a single bar. If you select six or more filters, Cost Explorer displays five bars, stacks, or lines, and then aggregates all remaining items, including taxes, into a sixth bar, stack slice, or plot line that's labeled **Other**.
+ **Upfront reservation fee**: Any upfront fees that are charged to your account. When you purchase an All Upfront or Partial Upfront Reserved Instance from AWS, you pay an upfront fee in exchange for a lower rate for using the instance. The upfront fees can result in spikes in the chart for the days or months when you make your purchases.
+ **Usage**: Usage that AWS didn't apply reservation discounts to.

**Cost category**  
 Choose the cost category group and value to track with this budget. To learn more about setting up cost categories, see [Organizing costs using AWS Cost Categories](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-cost-categories.html).

**Instance family**  
 Choose the family of instances to track using this budget.

**Instance type**  
Choose the type of instance that you want to track with this budget. 

**Invoicing entity**  
The AWS entity that issues the invoice. Possible values include:  
+ Amazon Web Services, Inc. – The entity that issues invoices to customer globally, where applicable.
+ Amazon Web Services India Private Limited – The entity that issues invoices to customers based in India.
+ Amazon Web Services South Africa Proprietary Limited – The entity that issues invoices to customers in South Africa.

**Legal entity**  
The Seller of Record of a specific product or service. In most cases, the invoicing entity and legal entity are the same. The values might differ for third-party AWS Marketplace transactions. Possible values include:  
+ Amazon Web Services, Inc. – The entity that sells AWS services.
+ Amazon Web Services India Private Limited – The local Indian entity that acts as a reseller for AWS services in India.
Amazon Web Services EMEA SARL is the marketplace operator for your purchases if your account is located in EMEA (excluding Turkey and South Africa), and the seller is eligible in EMEA. Purchases include subscriptions. Amazon Web Services, Inc. is the marketplace operator for purchases if the seller isn’t eligible for EMEA. For more information, see [AWS Europe](https://aws.amazon.com/legal/aws-emea/).

**Linked account**  
Choose an AWS account that is a member of the consolidated billing family that you're creating the budget for. For more information, see [Consolidated billing for AWS Organizations](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html) in the *AWS Billing User Guide*.  
Do not use this filter within a member account. If the current account is a member account, filtering by `linked account` is not supported.

**Platform**  
Choose the operating system that your RI runs on. **Platform** is either **Linux** or **Windows**.

**Purchase option**  
Choose `On Demand Instances`, `Standard Reserved Instances`, or `Savings Plans`.

**Region**  
Choose the Region in which the resource that you want to create a budget for is running.

**Savings Plans type**  
Choose what you want to budget for, between **Compute Savings Plans** and **EC2 Instance Savings Plans**. The Savings Plans type filter is only available for Savings Plans utilization budgets.

**Scope**  
Choose the scope of your RI. The scope is either regional or zonal.

**Service**  
Choose an AWS service. Combined with **Billing entity**, **Invoicing entity**, and **Legal entity**, you can also use the **Service** dimension to filter costs by specific AWS Marketplace purchases. This includes your costs for specific AMIs, web services, and desktop apps. For more information, see [ What Is AWS Marketplace?](https://docs.aws.amazon.com/marketplace/latest/controlling-access/what-is-marketplace.html)  
You can use this filter only for cost, Savings Plans and Reserved Instance (RI) utilization, or Savings Plans and RI coverage budgets. Cost Explorer doesn't show revenue or usage for the AWS Marketplace software seller.   
The Savings Plans utilization, RI utilization, Savings Plans coverage reports, and RI coverage reports lets you filter by only one service at a time and only for the following services:  
+ Amazon Elastic Compute Cloud
+ Amazon Redshift
+ Amazon Relational Database Service
+ Amazon ElastiCache
+ Amazon OpenSearch Service

**Tag**  
If you activated any tags, choose a resource tag. A tag is a label that you can use to organize your resource costs and track them on a detailed level. There are AWS generated tags and user-defined tags. User-defined tag keys must use the `user:` prefix. You must activate tags to use them. For more information, see [Activating the AWS-Generated Cost Allocation Tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activate-built-in-tags.html) and [Activating User-Defined Cost Allocation Tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html).

**Tenancy**  
Choose whether you share an RI with another user. **Tenancy** is either **Dedicated** or **Default**.

**Usage type**  
Usage types are the units each service uses to measure the usage for specific types of resources. If you choose a filter such as `S3` and then choose a usage type value, such as `DataTransfer-Out-Bytes (GB)`, your costs are limited to S3 `DataTransfer-Out-Bytes (GB)`. You can create a usage budget only for a specific unit of measure. If you choose **Usage type** but not **Usage type group**, the budget monitors all of the available units of measure for the usage type.

**Usage type group**  
A usage type group is a collection of usage types that have the same unit of measure. If you choose both the **Usage type group** and the **Usage type** filters, Cost Explorer shows you usage types that are automatically constrained to the group unit of measure. For example, assume you choose the group `EC2: Running Hours (Hrs)`, and then choose the `EC2-Instances` filter for **Usage type**. Cost Explorer shows you only the usage types that are measured in hours.