AWS neptune-analytics documentation change
Summary
Updated documentation links and maintained existing security group configuration guidance
Security assessment
Changes include URL formatting fixes and minor text consistency updates. The security group recommendations (e.g., allowing port 22/443) are pre-existing and not new security documentation. No evidence of addressing a specific security vulnerability.
Diff
diff --git a/neptune-analytics/latest/userguide/gettingStarted-connecting-within-VPC.md b/neptune-analytics/latest/userguide/gettingStarted-connecting-within-VPC.md index 649a2d4d2..3e6b98d4d 100644 --- a//neptune-analytics/latest/userguide/gettingStarted-connecting-within-VPC.md +++ b//neptune-analytics/latest/userguide/gettingStarted-connecting-within-VPC.md @@ -9 +9 @@ For graphs using private endpoints, you can connect to your graph from any resou -For details on how to use notebooks and how to create one capable of connecting to the private endpoint of your graph, see the Neptune Analytics user guide section on [notebooks](https://docs.aws.amazon.com/neptune-analytics/latest/userguide/notebooks.html), making sure to supply the necessary VPC and subnet identifier when setting up your network options. If the VPC CIDR is 172.17.0.0/16, notebooks will have some difficult connecting the graph endpoints. +For details on how to use notebooks and how to create one capable of connecting to the private endpoint of your graph, see the Neptune Analytics user guide section on [notebooks](https://docs.aws.amazon.com//neptune-analytics/latest/userguide/notebooks.html), making sure to supply the necessary VPC and subnet identifier when setting up your network options. If the VPC CIDR is 172.17.0.0/16, notebooks will have some difficult connecting the graph endpoints. @@ -11 +11 @@ For details on how to use notebooks and how to create one capable of connecting -You can also create an Amazon EC2 instance to connect to the private endpoint of your graph. You will need to select the correct VPC and availability zone to match your graph’s private endpoint. When prompted for a security group to associate with the instance, create or choose one that has inbound TCP rules allowing ingress traffic over ports 22 (for SSH), and egress traffic over port 443 if custom egress rules are needed. For the detailed prerequisites and steps to create and connect to an Amazon EC2 instance, see the [Amazon EC2 user guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html). +You can also create an Amazon EC2 instance to connect to the private endpoint of your graph. You will need to select the correct VPC and availability zone to match your graph’s private endpoint. When prompted for a security group to associate with the instance, create or choose one that has inbound TCP rules allowing ingress traffic over ports 22 (for SSH), and egress traffic over port 443 if custom egress rules are needed. For the detailed prerequisites and steps to create and connect to an Amazon EC2 instance, see the [Amazon EC2 user guide](https://docs.aws.amazon.com//AWSEC2/latest/UserGuide/EC2_GetStarted.html). @@ -15 +15 @@ You can also create an Amazon EC2 instance to connect to the private endpoint of -For troubleshooting connectivity issues refer to the [reachability analyzer](https://docs.aws.amazon.com/vpc/latest/reachability/what-is-reachability-analyzer.html) guide. You can get destination VPC endpointId by using the [GetPrivateGraphEndpoint](https://docs.aws.amazon.com/neptune-analytics/latest/apiref/API_GetPrivateGraphEndpoint.html) API. +For troubleshooting connectivity issues refer to the [reachability analyzer](https://docs.aws.amazon.com//vpc/latest/reachability/what-is-reachability-analyzer.html) guide. You can get destination VPC endpointId by using the [GetPrivateGraphEndpoint](https://docs.aws.amazon.com//neptune-analytics/latest/apiref/API_GetPrivateGraphEndpoint.html) API.