AWS neptune documentation change

Service: neptune · 2025-05-22 · Documentation medium

File: neptune/latest/userguide/export-params-fields.md

Summary

Added documentation for new 'cloneClusterEnableAuditLogs' parameter to control audit logs in cloned clusters

Security assessment

The new parameter documentation enables security monitoring through audit logs, which is a security feature. However, there is no indication this change addresses a specific existing security vulnerability.

Diff

diff --git a/neptune/latest/userguide/export-params-fields.md b/neptune/latest/userguide/export-params-fields.md
index 292b26548..0c7cdd8c9 100644
--- a//neptune/latest/userguide/export-params-fields.md
+++ b//neptune/latest/userguide/export-params-fields.md
@@ -22,0 +23,2 @@ Listed below are all the possible top-level fields that can appear in a `params`
+  * cloneClusterEnableAuditLogs
+
@@ -120,0 +123,11 @@ By default, a cloned DB cluster consists of a single primary instance. The `clon
+### `cloneClusterEnableAuditLogs` field in `params`
+
+_(Optional)_. Default: false.
+
+If the `cloneCluster` parameter is present and set to true, you can use the `cloneClusterEnableAuditLogs` parameter to enable or disable audit logs in the cloned cluster.
+
+By default, audit logging is disabled.
+    
+    
+    "cloneClusterEnableAuditLogs" : true
+