# Explicit deny

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

A policy statement with a Deny effect that matches a request. In AWS, an explicit deny in any applicable policy overrides every allow, so the request fails. A deny is the one policy statement no other policy can override. It cannot be overridden.

## An example, sourced

AWS documents that within an account the permissions for an entity can be affected by identity-based policies, resource-based policies, permissions boundaries, Organizations SCPs or session policies, and states: "If any one of these policy types explicitly denies access for an operation, then the request is denied." Deny in an identity policy or a boundary overrides the allow. The same page says an explicit deny in an identity-based policy or a boundary overrides the allow.

## Why it matters here

Most guardrails in the library are explicit denies, because a deny holds wherever it is attached and survives later grants. Look for the deny first when you debug an access failure. If a request fails and the identity policy allows it, a deny somewhere in the stack is the first thing to rule out. The simulator names the matching policy.

## Related pages

- [Implicit deny: meaning and an example](/glossary/implicit-deny/)
- [Organizational unit: meaning and an example](/glossary/organizational-unit/)
- [Management account: meaning and an example](/glossary/management-account/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/explicit-deny/
