AWS Security ChangesHomeSearch

AWS aws-backup: Vault Lock limits: deny EC2 snapshot share/tier APIs via IAM

Service: aws-backup · 2026-10-23 · Documentation medium

File: aws-backup/latest/devguide/vault-lock.md · Type: iam

Summary

Adds a note that AWS Backup Vault Lock and vault access policies do not govern actions taken directly through Amazon EC2 APIs: EBS snapshot recovery points can still be shared with ModifySnapshotAttribute and re-tiered with ModifySnapshotTier. It recommends denying ec2:ModifySnapshotAttribute and ec2:ModifySnapshotTier with IAM policies or SCPs (exempting backup plan roles), encrypting source EBS volumes, and enabling block public access for EBS snapshots.

Security assessment

The added text documents a control gap (Vault Lock does not cover direct EC2 snapshot sharing/tiering) and prescribes IAM/SCP deny policies plus EBS block public access to prevent unintended snapshot exposure. It is hardening guidance rather than a fix for a named vulnerability or incident, so it is security documentation with medium impact.

Evidence

+  * Vault Lock and vault access policies govern actions taken through AWS Backup. They don't govern sharing or storage tier changes made directly through Amazon EC2 APIs. Amazon EBS snapshot recovery points can still be shared with `ModifySnapshotAttribute`, and their storage tier can be changed with `ModifySnapshotTier`. Amazon EC2 still can't delete snapshots managed by AWS Backup. To restrict sharing and tier changes, deny `ec2:ModifySnapshotAttribute` and `ec2:ModifySnapshotTier` using IAM policies or SCPs, and exempt the IAM roles that your backup plans use, because AWS Backup uses these actions for cross-account copy and cold storage transitions. You can also encrypt your source EBS volumes and enable [block public access for Amazon EBS snapshots](https://docs.aws.amazon.com/ebs/latest/userguide/block-public-access-snapshots.html). For more information, see [Vault access policies](https://docs.aws.amazon.com/aws-backup/latest/devguide/create-a-vault-access-policy.html).

Diff

diff --git a/aws-backup/latest/devguide/vault-lock.md b/aws-backup/latest/devguide/vault-lock.md
index 6a6a32e..5edf5d5 100644
--- a//aws-backup/latest/devguide/vault-lock.md
+++ b//aws-backup/latest/devguide/vault-lock.md
@@ -230,0 +231,2 @@ If an EC2 backup is disabled, you can [re-enable a disabled AMI](https://docs.aw
+  * Vault Lock and vault access policies govern actions taken through AWS Backup. They don't govern sharing or storage tier changes made directly through Amazon EC2 APIs. Amazon EBS snapshot recovery points can still be shared with `ModifySnapshotAttribute`, and their storage tier can be changed with `ModifySnapshotTier`. Amazon EC2 still can't delete snapshots managed by AWS Backup. To restrict sharing and tier changes, deny `ec2:ModifySnapshotAttribute` and `ec2:ModifySnapshotTier` using IAM policies or SCPs, and exempt the IAM roles that your backup plans use, because AWS Backup uses these actions for cross-account copy and cold storage transitions. You can also encrypt your source EBS volumes and enable [block public access for Amazon EBS snapshots](https://docs.aws.amazon.com/ebs/latest/userguide/block-public-access-snapshots.html). For more information, see [Vault access policies](https://docs.aws.amazon.com/aws-backup/latest/devguide/create-a-vault-access-policy.html).
+