INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Distinguish actual and forecast alerts, cost scope and delays, and draft a budget configuration with an actionable response.

Prerequisite

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.

Fields to define in a budget proposal
FieldDecision
ScopeThe whole account or a filtered service/other scope
PeriodRecurring monthly or a specific period, including what happens after expiry
Cost measureThe cost basis and treatment of tax, discounts and credits
ConditionActual or forecast, with an amount or percentage threshold
Recipients and responseDelivery destination, responsible person, billing checks and response timing

Usage, aggregation, evaluation and notification take time

Why an alert is not an instantaneous spending cap
Why an alert is not an instantaneous spending cap1: Resource usage — Actual usage is aggregated into billing data later. — Billing aggregation. 2: Billing aggregation — Updated data is used to evaluate the budget. — Budget evaluation. 3: Budget evaluation — Notify according to the conditions; spending can increase before and after notification. — Alert and response123Resource usageBilling aggregationBudget evaluationAlert and responseWhy an alert is not an instantaneous spending cap1: Resource usage — Actual usage is aggregated into billing data later. — Billing aggregation. 2: Billing aggregation — Updated data is used to evaluate the budget. — Budget evaluation. 3: Budget evaluation — Notify according to the conditions; spending can increase before and after notification. — Alert and response123Resource usageBillingaggregationBudgetevaluationAlert andresponse
  1. Resource usage → Billing aggregationActual usage is aggregated into billing data later.
  2. Billing aggregation → Budget evaluationUpdated data is used to evaluate the budget.
  3. 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

The same numeric threshold can refer to different measures
TypeMeaningCheck
Actual alertAggregated actual spend meets the configured conditionNotification follows data updates; live usage may already differ
Forecast alertProjected spending meets the configured conditionDo 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.

No budget alert has arrived. Can you conclude that current charges are below the threshold?
Read the answer and reason

Answer: No, check delays and configuration too · Usage can increase before notification. Check data updates, cost measure, period, recipient and actual/forecast conditions rather than inferring live costs from silence.

Worked example: assign a response to a monthly alert

A synthetic proposal; the owner chooses the amount
FieldWhat to specify
PurposeNotice unexpected cost growth in a learning account
Scope and measureAlign account, month and cost basis with the billing review
Alert conditionRecord the owner’s amount/percentage and actual/forecast choice
ResponderName the recipient and an alternate for absences
After receiptReview 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.

Read the recipient state
StateMeaning
ActiveVerified for the relevant account and able to receive notifications
PendingAwaiting verification; entering an address alone does not establish readiness
InactiveNot 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.

  1. Confirm scope, period, cost measure and threshold with the owner.
  2. Review destination and conditions in the official interface, and assign receipt verification.
  3. Check forecasting history, billing delays and budget expiry.
  4. On receipt, inspect the bill and resources; an authorized person decides and performs the response.

Check, then explain in your own words

  1. Define scope, period and cost measure.
  2. Distinguish actual from forecast and explain the notification delay.
  3. 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.