Cloud concept · Updated

Error Budgets - Error budgets quantify the amount of unreliability a service can tolerate within a defined period while still meeting its service-level objective.

In short

An error budget translates a reliability target into an allowance for failed requests, excessive latency, or unavailable time. Teams use that allowance to balance delivery speed against operational risk, prioritize resilience work, and protect customer-facing service-level commitments.

Cloud Concepts Hub →

6 key aspects of Error Budgets

Error budgets turn reliability objectives into measurable allowances that guide alerting, release policies, and resilience investment.

01
Measurable reliability allowance

Derive the budget from a defined SLO and measurement window. Specify whether consumption is based on requests, time intervals, or another measurable unit so that calculations reflect the intended user experience.

02
Separation of SLIs, SLOs, and SLAs

SLIs measure performance, SLOs set operational targets, and SLAs define customer-facing commitments and possible remedies. A stricter internal SLO can provide room to act before an SLA breach.

03
Burn-rate monitoring

Compare the observed bad-event fraction with the SLO's allowed bad-event fraction to identify unusually fast budget consumption. Use multiple evaluation windows to detect sustained problems without paging on every brief fluctuation.

04
Policy-driven release decisions

Define what happens when budget consumption accelerates or the budget is exhausted, including release restrictions, escalation, and recovery priorities. Make exceptions for security and corrective changes explicit rather than assuming every deployment must stop.

05
Business-aligned resilience investment

Use budget consumption and incident analysis to prioritize redundancy, recovery automation, and dependency improvements. Balance their cost against customer impact, contractual commitments, and separate recovery-time and data-loss requirements.

06
Representative measurement

Measure critical user journeys and distinguish important customer or workload segments. An aggregate SLO can remain healthy while a low-volume but business-critical operation repeatedly fails.

Cloud services for Error Budgets

CloudWatch provides the measurements and SLO visibility needed to track error-budget consumption. CodeDeploy can respond to configured alarms during releases, while delivery-pipeline policy determines whether remaining budget permits additional changes. Route 53 contributes to resilience through health-based DNS failover, although its recovery behavior must be measured rather than assumed. AWS Fault Injection Service tests whether those protections work under controlled failures. Together, these services support a feedback loop: measure customer impact, detect excessive consumption, limit risky changes, and validate recovery mechanisms. They do not replace clear SLO definitions or an agreed error-budget policy.

Amazon CloudWatchAmazon CloudWatch

CloudWatch collects application metrics and supports alarms for reliability monitoring. CloudWatch Application Signals supports SLOs, error-budget reporting, and burn-rate monitoring, helping teams connect observed service behavior to reliability targets.

AWS CodeDeployAWS CodeDeploy

CodeDeploy supports controlled deployment strategies for supported compute platforms and can stop deployments or initiate automatic rollback in response to configured CloudWatch alarms. Teams can use these controls to limit deployment-related budget consumption; a broader budget-based release freeze requires an explicit delivery policy and integration.

Amazon Route 53Amazon Route 53

Route 53 health checks and DNS failover routing can direct traffic away from unhealthy endpoints, reducing the duration of some failures. DNS caching, health-check timing, and standby readiness affect recovery, so failover must be tested against the application's reliability target.

Error Budgets exam questions

Real practice exam questions on Error Budgets, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAP-C03

A company operates a payment authorization API on Amazon ECS. Request volume varies by a factor of 100 throughout the day, and requests are distributed unevenly across tasks. Each task publishes two custom CloudWatch counters every minute: EligibleRequests and BadRequests. BadRequests counts each eligible request once if it fails authorization processing or takes longer than 800 milliseconds. Health checks and invalid client requests are excluded from both counters.

The company requires at least 99.9% of eligible requests to be good over a rolling 30-day window. The operations team must receive a page before the objective is breached when the bad-request fraction exceeds 14.4 times the objective's allowed bad-request fraction over BOTH the preceding 5 minutes and the preceding hour.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Create a request-based SLO in CloudWatch Application Signals with a 99.9% goal and a rolling 30-day interval, using fleet-wide summed EligibleRequests and BadRequests. Create metric math alarms when summed BadRequests divided by summed EligibleRequests exceeds 1.44% over 5 minutes and over 1 hour. Configure a composite alarm to page only when both alarms are in ALARM.

The request-based SLO weights every eligible request equally, regardless of traffic volume or task placement. A 99.9% goal permits a 0.1% bad-request fraction. A burn rate of 14.4 therefore corresponds to a 1.44% bad-request fraction. The two window-specific alarms combined with AND implement the required paging policy before the rolling objective is necessarily breached.

DOP-C02

A company operates a stateless transaction API on Amazon EC2 in one AWS Region. Its customer SLA requires 99.9% time-based availability, and its internal SLO requires 99.95% availability during each 30-day month. A minute counts as unavailable whenever the API cannot process the full peak transaction rate within the required latency. The application has already accumulated 18 minutes of unavailability this month.

A DevOps engineer must prepare for one additional Availability Zone outage during peak traffic without exceeding the remaining internal error budget. Load tests show that launching and initializing additional instances takes 5 minutes. Removing unhealthy targets and routing traffic to already healthy instances takes at most 1 minute. All dependencies outside the EC2 application tier are already resilient to an Availability Zone outage.

Which configuration meets these requirements?

Show answerCORRECT ANSWER

Distribute running instances across two Availability Zones, with either zone independently able to serve the full peak transaction rate. Use health-based load balancing and verify that traffic shifts to the surviving zone within 1 minute.

A 99.95% time-based SLO allows 21.6 minutes of unavailability in a 30-day month. After 18 minutes have been consumed, 3.6 minutes remain. Maintaining full peak capacity in either zone avoids waiting for instance initialization, and the verified 1-minute traffic shift fits within the remaining budget.

Practice Error Budgets in a full exam

Questions on Error Budgets in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Error Budgets

2 min read

An error budget is the permitted amount of failure implied by a service-level objective (SLO). A service-level indicator (SLI) measures actual behavior, such as the proportion of valid requests that succeed or complete within a latency threshold. The SLO sets the required performance over a defined measurement window. For a proportion-based SLO, the allowed bad-event fraction is one minus the target good-event fraction. The remaining budget is the allowed amount of bad events minus the bad events already observed within that window.

For example, an API with a 99.9% successful-request SLO can tolerate 0.1% failed requests. If the evaluation window contains one million eligible requests, its allowance is 1,000 failures. After 700 failures, 300 remain. For a time-based availability SLO measured continuously over 30 days, 99.9% permits 43.2 minutes of unavailability. These examples are not interchangeable: request-based measurement weights failures by traffic, whereas time-based measurement weights them by duration. Define eligibility, measurement boundaries, timeout behavior, and exclusions before using either calculation.

A service-level agreement (SLA) is a customer-facing commitment that may specify remedies such as service credits. An SLO is an operational target and is often stricter than the corresponding SLA, leaving a margin for intervention. Error budgets usually derive from SLOs rather than directly from contractual thresholds. An application's SLA also does not automatically match the SLA of its cloud infrastructure. Dependency failures, deployment defects, configuration mistakes, and application behavior all affect the customer experience, while provider SLA calculations have their own scope and exclusions.

In cloud operations, teams collect user-relevant telemetry and calculate budget consumption over a calendar or rolling window. Burn rate compares the observed bad-event fraction with the fraction allowed by the SLO. With a 99.9% SLO, a 1% failure rate represents a burn rate of 10. If sustained under comparable traffic conditions, that rate consumes the budget ten times faster than planned. Alerts across short and long windows help distinguish a brief spike from sustained degradation and provide time to intervene before the objective is missed.

A documented error-budget policy connects these measurements to decisions. Healthy remaining budget can support normal releases and controlled experiments. Rapid consumption may trigger rollback, smaller deployment batches, or incident response. Exhaustion commonly pauses discretionary changes while the team addresses reliability, but security fixes and recovery changes may remain permitted. These actions require explicit ownership and automation; monitoring alone does not enforce a release policy.

Error budgets also guide architecture choices. Multi-AZ deployment, redundant dependencies, tested failover, and automated recovery can reduce consumption, but add cost and operational complexity. Cross-Region recovery may be justified by business requirements rather than by an availability percentage alone. Evaluate recovery time and data-loss requirements separately because an availability budget does not define an acceptable recovery point. A budget is neither permission to cause avoidable outages nor a guarantee of customer satisfaction: aggregate success can hide severe failures for one tenant or critical workflow, so segment important journeys and review incidents even when the overall SLO is met.

Learn Error Budgets in lessons

4 short lessons on Error Budgets in 2 certification courses.

Open the lessons