AWS Security ChangesHomeSearch

AWS neptune: Explain SigV4 signing requirement when IAM auth is enabled

Service: neptune · 2026-11-13 · Documentation medium

File: neptune/latest/userguide/access-graph-opencypher-queries.md · Type: auth

Summary

Adds Content-Type headers to awscurl examples and a new section explaining that with IAM database authentication enabled, every request must be signed with AWS Signature Version 4, and that unsigned curl requests fail with HTTP 403.

Security assessment

The new section documents the authentication requirement (SigV4 signing) for IAM database authentication and warns that unsigned requests are rejected with 403, helping users avoid misconfigured unauthenticated access patterns. It is authentication guidance rather than a fix for a specific vulnerability.

Evidence

+When IAM database authentication is enabled on your DB cluster, Neptune requires you to sign every request with AWS Signature Version 4. The AWS CLI, SDK, and `awscurl` examples sign your requests automatically when you configure your AWS credentials.

Diff

diff --git a/neptune/latest/userguide/access-graph-opencypher-queries.md b/neptune/latest/userguide/access-graph-opencypher-queries.md
index 7f63b44..0a207da 100644
--- a//neptune/latest/userguide/access-graph-opencypher-queries.md
+++ b//neptune/latest/userguide/access-graph-opencypher-queries.md
@@ -77,0 +78 @@ awscurl
+      -H "Content-Type: application/x-www-form-urlencoded" \
@@ -131,0 +133 @@ awscurl
+      -H "Content-Type: application/x-www-form-urlencoded" \
@@ -144,0 +147,6 @@ curl
+###### Unsigned requests fail when IAM database authentication is enabled
+
+When IAM database authentication is enabled on your DB cluster, Neptune requires you to sign every request with AWS Signature Version 4. The AWS CLI, SDK, and `awscurl` examples sign your requests automatically when you configure your AWS credentials.
+
+The plain `curl` example sends an unsigned request. It works only when IAM database authentication is disabled. When IAM database authentication is enabled, the request fails with an HTTP `403` (Forbidden) error. For more information, see [Connecting with IAM authentication](./iam-auth-connecting.html).
+