AWS Security ChangesHomeSearch

AWS neptune documentation change

Service: neptune · 2026-03-07 · Documentation medium

File: neptune/latest/userguide/get-started-connecting.md

Summary

Clarified VPC accessibility and public endpoint requirements

Security assessment

Improves documentation about network security configuration without addressing vulnerabilities

Diff

diff --git a/neptune/latest/userguide/get-started-connecting.md b/neptune/latest/userguide/get-started-connecting.md
index 77f91994c..ef1d069df 100644
--- a//neptune/latest/userguide/get-started-connecting.md
+++ b//neptune/latest/userguide/get-started-connecting.md
@@ -27 +27 @@ You can then specify the location of this CA certificate store using the `CURL_C
-An Amazon Neptune DB cluster can _only_ be created in an Amazon Virtual Private Cloud (Amazon VPC). Unless you enable and set up Neptune public endpoints for the DB cluster, its endpoints are accessible within that VPC or using a public endpoint.
+An Amazon Neptune DB cluster can _only_ be created in an Amazon Virtual Private Cloud (Amazon VPC). Its endpoints are accessible only within that VPC unless you enable and set up [Neptune public endpoints](./neptune-public-endpoints.html) for the DB cluster.