blast radius

How much of a system is affected when something fails or has to be running for a check to happen.

In more detail

In testing, a test with a large blast radius needs many parts alive and can fail for many unrelated reasons. In operations, the term describes how many users or services a bad change can hurt. Both senses push you towards small, contained checks and changes.

Examples

In AWS: How much harm one failure, mistake or stolen credential can cause before something stops it.
A remediation job that refuses to change more than three resources per run
blast radius: 25 percent of users, for one wave
Starting a canary at 10% of traffic limits a bad release to a tenth of users for a few minutes.
The course frames least privilege as a blast radius question: assume the credential leaks, then ask what it can do in the next few minutes.

Related terms

Taught in

References

Certification courses