Topic lessonTopic: Costs, Free Tier and budgets
AWS Budgets explained: actual and forecast alerts, recipients and spending limits
AWS Budgets compares actual or forecast costs and usage against a configured budget. An alert amount does not guarantee that the final bill stops there. Define scope, period, cost measure, threshold, recipient and response so an alert leads to a useful billing investigation.
Distinguish actual and forecast alerts, cost scope and delays, and draft a budget configuration with an actionable response.
Understand AWS cost components and billing details. This lesson drafts a configuration only; it changes no AWS settings and sends no real notifications.
A budget is a comparison baseline; an alert draws attention
Actual means accumulated cost or usage; forecast estimates future spend. Budgets can also address usage and reservation/Savings Plans utilization or coverage. This lesson focuses on monthly cost alerts.
| Field | Decision |
|---|---|
| Scope | The whole account or a filtered service/other scope |
| Period | Recurring monthly or a specific period, including what happens after expiry |
| Cost measure | The cost basis and treatment of tax, discounts and credits |
| Condition | Actual or forecast, with an amount or percentage threshold |
| Recipients and response | Delivery destination, responsible person, billing checks and response timing |
Usage, aggregation, evaluation and notification take time
- Resource usage → Billing aggregationActual usage is aggregated into billing data later.
- Billing aggregation → Budget evaluationUpdated data is used to evaluate the budget.
- Budget evaluation → Alert and responseNotify according to the conditions; spending can increase before and after notification.
- Resource usage
- Charges arise here, and usage may continue.
- Billing aggregation
- Usage takes time to appear in billing data.
- Budget evaluation
- Conditions are checked using the available cost and usage data.
- Alert and response
- After receipt, an owner investigates the cause and response.
Actual and forecast alerts evaluate different values
| Type | Meaning | Check |
|---|---|---|
| Actual alert | Aggregated actual spend meets the configured condition | Notification follows data updates; live usage may already differ |
| Forecast alert | Projected spending meets the configured condition | Do not rely on a forecast in a new environment without the required history |
AWS documents usage-history requirements for forecasting. An unavailable forecast does not mean there is no use or that future spend will remain below a budget. Continue checking actual costs and active resources.
Choose an option to see the result and explanation.
Worked example: assign a response to a monthly alert
| Field | What to specify |
|---|---|
| Purpose | Notice unexpected cost growth in a learning account |
| Scope and measure | Align account, month and cost basis with the billing review |
| Alert condition | Record the owner’s amount/percentage and actual/forecast choice |
| Responder | Name the recipient and an alternate for absences |
| After receipt | Review the period and service breakdown, then propose a response to the owner |
Totals can differ when a budget and another billing view treat credits or tax differently. Before explaining a numeric difference, align period, scope and cost measure.
Verify recipient readiness after registration
For email recipients added directly, check verification status. A new unverified address receives a confirmation email, and its recipient must complete verification in the relevant AWS account. An address already verified in that account may not need another confirmation. Do not re-register every existing active recipient indiscriminately.
| State | Meaning |
|---|---|
| Active | Verified for the relevant account and able to receive notifications |
| Pending | Awaiting verification; entering an address alone does not establish readiness |
| Inactive | Not yet registered for notifications; review registration |
| Active (legacy) | A pre-verification-era recipient that continues to receive alerts without new action |
Amazon SNS (Simple Notification Service) subscription confirmation is separate from direct email-recipient verification. Investigate the address, recipient state, relevant account and notification method when delivery fails. This lesson neither collects addresses nor sends confirmation messages.
Review budget actions separately from notifications
Budget actions can affect permissions or stop specified resources. Do not add them as though they were merely an email alert. An administrator must review authorization, trigger conditions, impact and recovery. Auto Scaling or other automation may undo a stop, so an action is not a guarantee that all charges cease.
- Confirm scope, period, cost measure and threshold with the owner.
- Review destination and conditions in the official interface, and assign receipt verification.
- Check forecasting history, billing delays and budget expiry.
- On receipt, inspect the bill and resources; an authorized person decides and performs the response.
Check, then explain in your own words
- Define scope, period and cost measure.
- Distinguish actual from forecast and explain the notification delay.
- Assign recipients and their next checks.
Check your understanding: Does adding an automatic stop action guarantee an exact billing cap?
No. Notifications and actions alone do not guarantee a strict cap.
Data/notification delays, permissions, targeted resources, retained storage and automatic restarts are separate conditions. Verify both the notification and the outcome of any action.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Managing costs with AWS BudgetsChecked:
Scope and conditionsNotification and billing delays; alert is not a hard cap
Used in this lessonA budget is a comparison baseline; an alert draws attention Usage, aggregation, evaluation and notification take time Actual and forecast alerts evaluate different values Worked example: assign a response to a monthly alert Review budget actions separately from notifications
- Understanding your billChecked:
Scope and conditionsBilling period, service/Region breakdown and estimated charges
Used in this lessonWorked example: assign a response to a monthly alert
- Best practices for AWS BudgetsChecked:
Scope and conditionsActual versus forecast alerts, history requirements, period and cost filters, update lag and separate action permissions.
Used in this lessonA budget is a comparison baseline; an alert draws attention Usage, aggregation, evaluation and notification take time Actual and forecast alerts evaluate different values Worked example: assign a response to a monthly alert Review budget actions separately from notifications
- Creating an AWS cost budgetChecked:
Scope and conditionsCost budget scope, periods, thresholds, actual/forecast conditions and direct email versus SNS verification.
Used in this lessonVerify recipient readiness after registration
Scope and conditionsAccount-specific direct recipient verification, Active/Pending/Inactive/legacy states, separate SNS subscriptions; no real verification performed.
Used in this lessonVerify recipient readiness after registration