AI Cert Prep
Type to search documentation.

CloudOps Engineer – Associate

Cost management and budgets

AWS Budgets and budget actions, Cost Explorer, Cost and Usage Reports, allocation tags and the cost levers SOA-C03 expects an operator to pull.

Operations notes for AWS Certified CloudOps Engineer – Associate (SOA-C03), the credential formerly called SysOps Administrator – Associate. This is the operator exam: monitoring, remediation, automation, cost control and governance, tested from the point of view of the person on call.

2 topics, 7 study points. Everything here is exam-oriented: each point is a fact or a distinction that SOA-C03 items are built on. Test yourself against the practice exam once you can explain a section without re-reading it.

1. AWS Budgets

AWS Budgets enables you to set proactive cost and usage thresholds and receive alerts before — or when — you exceed them. Unlike AWS Cost Explorer (which shows you what you have already spent), Budgets alerts you in advance based on both actual spend and forecasted spend. This makes Budgets an essential tool for financial governance: development teams can be alerted when their monthly spending is on track to exceed budget, enabling corrective action before the billing period ends and the bill is finalized.

You can create four types of AWS Budgets. Cost Budgets track total spend in dollars and alert when actual or forecasted costs cross a threshold. Usage Budgets track consumption of a specific AWS service in usage units (for example, EC2 hours or S3 GB) rather than dollars — useful when you want to control consumption independently of pricing. Reservation Utilization Budgets alert when your Reserved Instance or Savings Plan utilization drops below a threshold, indicating that you are paying for capacity you are not fully using. Reservation Coverage Budgets alert when the percentage of your On-Demand usage that is covered by Reserved Instances drops below a target, indicating you have more on-demand spend than desired.

Budgets can be scoped to specific dimensions for granular tracking: by AWS service, by linked account (within an Organization), by tag (if you use cost allocation tags to label resources by team or project), by usage type, or by region. Alert notifications are sent via email to up to 10 addresses and/or to an SNS topic — the SNS integration allows downstream automation such as posting to Slack, triggering a Lambda function to take automated cost-reduction actions, or creating a JIRA ticket for the responsible team. The AWS Budgets Dashboard in the Cost Management console provides a centralized view of all your budgets and their current status.

2. AWS Cost Management

AWS Cost Explorer is the primary visualization and analysis tool for understanding your AWS spending. It provides pre-built reports for monthly costs by service, costs by linked account, Reserved Instance utilization and coverage, and Savings Plans utilization. The interactive interface lets you filter and group costs by any combination of dimensions: service, region, account, availability zone, instance type, usage type, and cost allocation tags. You can view historical data up to 12 months back and forecasted data up to 12 months forward, enabling trend analysis and budget planning.

Cost Allocation Tags allow you to label AWS resources with key-value metadata and then use those labels to track costs. For example, tagging every resource with Project

and Environment
lets you see exactly how much the customer portal production environment costs each month in Cost Explorer. There are two types of tags: AWS-generated tags (automatically applied by some services, like an ASG’s “aws:autoscaling
”) and user-defined tags (applied manually or through Infrastructure as Code). Tags must be activated in the Billing console before they appear as cost allocation dimensions in Cost Explorer.

Consolidated Billing, enabled through AWS Organizations, combines the AWS usage from all member accounts into a single monthly invoice paid by the management (payer) account. Beyond simplifying billing, Consolidated Billing provides a significant economic benefit: AWS pricing for many services (S3, EC2 data transfer, etc.) includes volume tiering — the more you use, the lower the per-unit cost. By aggregating usage across all accounts, Consolidated Billing allows the entire organization to achieve higher volume tiers that individual accounts might never reach on their own. Reserved Instance and Savings Plans benefits are also shared across the organization by default — an RI purchased in one account can automatically discount usage in another account if the purchasing account does not fully utilize it.

AWS Cost Anomaly Detection uses machine learning to automatically identify unusual spending patterns and alert you before costs spiral out of control. Instead of manually setting static budget thresholds, Cost Anomaly Detection learns your normal spending patterns over time and alerts you when actual spending deviates significantly from the expected baseline — even if it has not yet crossed a fixed dollar threshold. This is particularly valuable for detecting accidental resource provisioning (someone accidentally left a large EC2 instance running) or security incidents (a compromised account mining cryptocurrency).


Where to go next

Last updated Sep 18, 2026