AWS neptune documentation change
Summary
Removed commented-out dependency block for gremlin-groovy and simplified SSL/TLS configuration guidance by removing deprecated keyCertChainFile references.
Security assessment
Cleanup of outdated implementation details. SSL/TLS requirements remain unchanged, and the removed content was either commented or described deprecated methods. No security vulnerability is addressed.
Diff
diff --git a/neptune/latest/userguide/access-graph-gremlin-java.md b/neptune/latest/userguide/access-graph-gremlin-java.md index 1298e423d..84103db93 100644 --- a//neptune/latest/userguide/access-graph-gremlin-java.md +++ b//neptune/latest/userguide/access-graph-gremlin-java.md @@ -84,7 +83,0 @@ When prompted, enter the number for Java 11. - <!-- https://mvnrepository.com/artifact/org.apache.tinkerpop/gremlin-groovy - (Not needed for TinkerPop version 3.5.2 and up) - <dependency> - <groupId>org.apache.tinkerpop</groupId> - <artifactId>gremlin-groovy</artifactId> - <version>3.7.2</version> - </dependency> --> @@ -224,3 +217 @@ The following methods submit the query to the Neptune DB instance: -Neptune requires SSL/TLS to be enabled by default. Typically, if the Java driver is configured with `enableSsl(true)`, it can connect to Neptune without having to set up a `trustStore()` or `keyStore()` with a local copy of a certificate. Earlier versions of TinkerPop encouraged use of `keyCertChainFile()` to configure a locally stored `.pem` file, but that has been deprecated and no longer available after 3.5.x. If you were using that setup with a public certificate, using `SFSRootCAG2.pem`, you can now remove the local copy. - -However, if the instance with which you are connecting doesn't have an internet connection through which to verify a public certificate, or if the certificate you're using isn't public, you can take the following steps to configure a local certificate copy: +Neptune requires SSL/TLS to be enabled by default. Typically, if the Java driver is configured with `enableSsl(true)`, it can connect to Neptune without having to set up a `trustStore()` or `keyStore()` with a local copy of a certificate. However, if the instance with which you are connecting doesn't have an internet connection through which to verify a public certificate, or if the certificate you're using isn't public, you can take the following steps to configure a local certificate copy: