AWS neptune documentation change
Summary
Added clarification that HTTP/1.1 must be used instead of HTTP/2 for REST API
Security assessment
The change addresses protocol compatibility rather than security vulnerabilities. The existing HTTPS requirement (security control) remains unchanged.
Diff
diff --git a/neptune/latest/userguide/access-graph-gremlin-rest.md b/neptune/latest/userguide/access-graph-gremlin-rest.md index fbfcac9e6..b89a4c550 100644 --- a//neptune/latest/userguide/access-graph-gremlin-rest.md +++ b//neptune/latest/userguide/access-graph-gremlin-rest.md @@ -13 +13 @@ Amazon Neptune provides an HTTPS endpoint for Gremlin queries. The REST interfac -As discussed in [Encrypting connections to your Amazon Neptune database with SSL/HTTPS](./security-ssl.html), Neptune now requires that you connect using HTTPS instead of HTTP. +As discussed in [Encrypting connections to your Amazon Neptune database with SSL/HTTPS](./security-ssl.html), Neptune now requires that you connect using HTTPS instead of HTTP. In addition, Neptune does not currently support HTTP/2 for REST API requests. Clients must use HTTP/1.1 when connecting to endpoints.