Skip to content
Cloud Governance Tools

Enforce a 30-day KMS key deletion window

Enforce a 30-day KMS key deletion window is an AWS guardrail written in service control policies. Denies kms:ScheduleKeyDeletion when the pending window is shorter than 30 days. What it breaks: scheduling key deletion with a pending window under 30 days fails for every principal in the affected accounts, because the policy has no exception condition.

More encryption and keys guardrails ยท About Service control policies

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": "kms:ScheduleKeyDeletion",
      "Resource": "*",
      "Condition": {
        "NumericLessThan": {
          "kms:ScheduleKeyDeletionPendingWindowInDays": "30"
        }
      }
    }
  ]
}
Blocks
Denies kms:ScheduleKeyDeletion when the pending window is shorter than 30 days.
Breaks
Scheduling key deletion with a pending window under 30 days fails for every principal in the affected accounts, because the policy has no exception condition. (source)
Test before applying
As for every Service control policies guardrail: how to test before enforcing
Mechanism
Service control policies (SCPs): IAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles.
Taken from
open source set, MIT-0 (README states MIT-0; LICENSE file fetched, MIT-0 text, Copyright Amazon.com, Inc.): https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/LICENSE

What the policy text names

It names 1 action or pattern: kms:ScheduleKeyDeletion. Its conditions test kms:ScheduleKeyDeletionPendingWindowInDays.

What the source says

"kms:ScheduleKeyDeletionPendingWindowInDays: 30" (read 10 Nov 2026).

What it breaks is documented for every guardrail of this mechanism: see Service control policies.

Sources

  1. Enforce a 30-day KMS key deletion window, read 10 Nov 2026
  2. What it breaks, read 10 Nov 2026
  3. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.