AWS neptune: Note on IAM auth and SigV4 signing for parameterized queries
Summary
Adds a note explaining that plain curl only works when IAM database authentication is disabled, that Neptune rejects unsigned requests when IAM auth is enabled, and that requests must be signed with AWS Signature Version 4 (e.g. via awscurl), with a link to the IAM authentication connection guide.
Security assessment
The added note documents an authentication requirement: with IAM database authentication enabled, unsigned requests are rejected and callers must sign with SigV4. This is security best-practice/feature documentation (authn) rather than a fix for a specific disclosed vulnerability.
Evidence
+When you enable IAM database authentication, Neptune rejects unsigned requests. Sign each request with AWS Signature Version 4. You can use a tool such as the `awscurl` command in the preceding example.
Diff
diff --git a/neptune/latest/userguide/opencypher-parameterized-queries.md b/neptune/latest/userguide/opencypher-parameterized-queries.md index ab1deb3..d71c926 100644 --- a//neptune/latest/userguide/opencypher-parameterized-queries.md +++ b//neptune/latest/userguide/opencypher-parameterized-queries.md @@ -98,0 +99,10 @@ Using `DIRECT POST`: +###### Note + +In these examples, replace `your-neptune-endpoint` with your cluster endpoint and `port` with the Neptune port (the default is `8182`). + +The plain `curl` form works only when you disable IAM database authentication on your cluster. + +When you enable IAM database authentication, Neptune rejects unsigned requests. Sign each request with AWS Signature Version 4. You can use a tool such as the `awscurl` command in the preceding example. + +For more information about signing requests with AWS Signature Version 4, see [Connecting with IAM authentication](./iam-auth-connecting.html). +