Neptune DB clusters should be encrypted with a customer-managed KMS key

Description

Neptune DB clusters should be encrypted using a customer-managed KMS key rather than the default AWS-managed key. Customer-managed keys provide full control over key rotation policies, access permissions via KMS key policies, and the ability to revoke or disable the key.

Remediation

Create a new Neptune cluster with a customer-managed KMS key specified. Existing clusters cannot have their encryption key changed after creation. For guidance, refer to Encrypting Neptune resources at rest.