AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2025-11-19 · Documentation low

File: prescriptive-guidance/latest/neptune-well-architected-framework/security-pillar.md

Summary

Updated 'AWS CloudFormation' reference to 'CloudFormation' in encryption configuration documentation

Security assessment

Change is purely a branding update in existing security documentation about encryption at rest. Security practices and recommendations remain unchanged.

Diff

diff --git a/prescriptive-guidance/latest/neptune-well-architected-framework/security-pillar.md b/prescriptive-guidance/latest/neptune-well-architected-framework/security-pillar.md
index da73e951d..2384d5f97 100644
--- a//prescriptive-guidance/latest/neptune-well-architected-framework/security-pillar.md
+++ b//prescriptive-guidance/latest/neptune-well-architected-framework/security-pillar.md
@@ -43 +43 @@ Data leakage and breaches put your customers at risk and can cause substantial n
-To enable encryption for a new Neptune DB instance, choose **Yes** in the **Enable encryption** section on the Neptune console (selected by default), or by setting the [AWS::Neptune::DBCluster::StorageEncrypted](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-neptune-dbcluster.html#cfn-neptune-dbcluster-storageencrypted) property in AWS CloudFormation. If encryption is enabled, Neptune will use the [Amazon Relational Database Service (Amazon RDS) AWS managed key by default](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Encryption.Keys.html), or you can create a [customer managed key](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk). For information about creating a Neptune DB instance, see [Creating a new Neptune DB cluster](https://docs.aws.amazon.com/neptune/latest/userguide/get-started-create-cluster.html). For more details, see [Encrypting Neptune Resources at Rest](https://docs.aws.amazon.com/neptune/latest/userguide/encrypt.html). Your automated and manual snapshots use the same encryption that you selected for your Neptune cluster.
+To enable encryption for a new Neptune DB instance, choose **Yes** in the **Enable encryption** section on the Neptune console (selected by default), or by setting the [AWS::Neptune::DBCluster::StorageEncrypted](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-neptune-dbcluster.html#cfn-neptune-dbcluster-storageencrypted) property in CloudFormation. If encryption is enabled, Neptune will use the [Amazon Relational Database Service (Amazon RDS) AWS managed key by default](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Encryption.Keys.html), or you can create a [customer managed key](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk). For information about creating a Neptune DB instance, see [Creating a new Neptune DB cluster](https://docs.aws.amazon.com/neptune/latest/userguide/get-started-create-cluster.html). For more details, see [Encrypting Neptune Resources at Rest](https://docs.aws.amazon.com/neptune/latest/userguide/encrypt.html). Your automated and manual snapshots use the same encryption that you selected for your Neptune cluster.