AWS neptune high security documentation change
Summary
Removed TLS/HTTPS enforcement note and replaced with HTTP/1.1 requirement
Security assessment
The removal of documentation about mandatory HTTPS/TLS 1.2 could mislead users into thinking unsecured HTTP connections are allowed, creating a potential security risk if implementations follow this guidance.
Diff
diff --git a/neptune/latest/userguide/access-graph-sparql-http-rest.md b/neptune/latest/userguide/access-graph-sparql-http-rest.md index 330c91c6b..c1cc7aec0 100644 --- a//neptune/latest/userguide/access-graph-sparql-http-rest.md +++ b//neptune/latest/userguide/access-graph-sparql-http-rest.md @@ -7,3 +7 @@ -Amazon Neptune provides an HTTP endpoint for SPARQL queries. The REST interface is compatible with SPARQL version 1.1. - -###### Important +###### Note @@ -11 +9 @@ Amazon Neptune provides an HTTP endpoint for SPARQL queries. The REST interface -[Release: 1.0.4.0 (2020-10-12)](./engine-releases-1.0.4.0.html) made TLS 1.2 and HTTPS mandatory for all connections to Amazon Neptune. It is no longer possible to connect to Neptune using unsecured HTTP, or using HTTPS with a version of TLS earlier than 1.2. +Neptune does not currently support HTTP/2 for REST API requests. Clients must use HTTP/1.1 when connecting to endpoints. @@ -20,0 +19,2 @@ For information about finding the hostname of your Neptune DB instance, see the +Amazon Neptune provides an HTTP endpoint for SPARQL queries. The REST interface is compatible with SPARQL version 1.1. +