AWS neptune high security documentation change
Summary
Modified encrypted snapshot sharing behavior to require copying before restoration
Security assessment
This change introduces a security control by preventing direct restoration of encrypted shared snapshots, requiring copy-first to ensure proper access management. This mitigates potential unauthorized restores of encrypted data.
Diff
diff --git a/neptune/latest/userguide/backup-restore-share-snapshot.md b/neptune/latest/userguide/backup-restore-share-snapshot.md index 3e2410023..5f6ea2f72 100644 --- a//neptune/latest/userguide/backup-restore-share-snapshot.md +++ b//neptune/latest/userguide/backup-restore-share-snapshot.md @@ -13 +13 @@ Using Neptune, you can share a manual DB cluster snapshot in the following ways: - * Sharing a manual DB cluster snapshot, whether encrypted or unencrypted, enables authorized AWS accounts to directly restore a DB cluster from the snapshot instead of taking a copy of it and restoring from that. + * Sharing an unencrypted manual DB cluster snapshot enables authorized AWS accounts to directly restore a DB cluster from the snapshot instead of taking a copy of it and restoring from that. Encrypted snapshots cannot be restored directly; they must be copied first and then restored from the copy.