AWS neptune-analytics documentation change
Summary
Updated multiple documentation links with corrected URL formatting
Security assessment
While the documentation discusses VPC connectivity and cross-account IAM roles (security-adjacent topics), the changes only fix URL syntax. No new security guidance or vulnerability mitigation is introduced.
Diff
diff --git a/neptune-analytics/latest/userguide/gettingStarted-connecting-different-VPC.md b/neptune-analytics/latest/userguide/gettingStarted-connecting-different-VPC.md index 666c38d74..789590e8c 100644 --- a//neptune-analytics/latest/userguide/gettingStarted-connecting-different-VPC.md +++ b//neptune-analytics/latest/userguide/gettingStarted-connecting-different-VPC.md @@ -11 +11 @@ In some cases, you may be required to connect to your graph from a different VPC -You can use any method that allows traffic to move between VPCs. For example, [VPC peering](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html) or [AWS Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html). In addition to establishing the network connection, make sure your security groups and network ACLs allow traffic between the two VPCs. You can verify network connectivity with the [reachability analyzer](https://docs.aws.amazon.com/vpc/latest/reachability/what-is-reachability-analyzer.html). +You can use any method that allows traffic to move between VPCs. For example, [VPC peering](https://docs.aws.amazon.com//vpc/latest/peering/what-is-vpc-peering.html) or [AWS Transit Gateway](https://docs.aws.amazon.com//vpc/latest/tgw/tgw-getting-started.html). In addition to establishing the network connection, make sure your security groups and network ACLs allow traffic between the two VPCs. You can verify network connectivity with the [reachability analyzer](https://docs.aws.amazon.com//vpc/latest/reachability/what-is-reachability-analyzer.html). @@ -15 +15 @@ You can use any method that allows traffic to move between VPCs. For example, [V -If you haven’t already, create a private graph endpoint in VPC A. This can be done through the console or the [ CreatePrivateGraphEndpoint ](https://docs.aws.amazon.com/neptune-analytics/latest/apiref/API_CreatePrivateGraphEndpoint.html) API. Once created, collect the DNS name for the VPC endpoint that was deployed. +If you haven’t already, create a private graph endpoint in VPC A. This can be done through the console or the [ CreatePrivateGraphEndpoint ](https://docs.aws.amazon.com//neptune-analytics/latest/apiref/API_CreatePrivateGraphEndpoint.html) API. Once created, collect the DNS name for the VPC endpoint that was deployed. @@ -17 +17 @@ If you haven’t already, create a private graph endpoint in VPC A. This can be - 1. Find the VPC endpoint ID from the value of **vpcEndpointId** when calling the [ ListPrivateGraphEndpoints ](https://docs.aws.amazon.com/neptune-analytics/latest/apiref/API_ListPrivateGraphEndpoints.html) API. + 1. Find the VPC endpoint ID from the value of **vpcEndpointId** when calling the [ ListPrivateGraphEndpoints ](https://docs.aws.amazon.com//neptune-analytics/latest/apiref/API_ListPrivateGraphEndpoints.html) API. @@ -19 +19 @@ If you haven’t already, create a private graph endpoint in VPC A. This can be - 2. From the console or using the [DescribeVpcEndpoints](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeVpcEndpoints.html) API, collect the DNS name of the VPC endpoint. This should have the format of `vpce-<alphanumeric>.vpce-svc-<alphanumeric>.<region>.vpce.amazonaws.com`. + 2. From the console or using the [DescribeVpcEndpoints](https://docs.aws.amazon.com//AWSEC2/latest/APIReference/API_DescribeVpcEndpoints.html) API, collect the DNS name of the VPC endpoint. This should have the format of `vpce-<alphanumeric>.vpce-svc-<alphanumeric>.<region>.vpce.amazonaws.com`. @@ -21 +21 @@ If you haven’t already, create a private graph endpoint in VPC A. This can be - 3. Use Amazon Route 53 to create a [private hosted zone](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-creating.html) for VPC B. + 3. Use Amazon Route 53 to create a [private hosted zone](https://docs.aws.amazon.com//Route53/latest/DeveloperGuide/hosted-zone-private-creating.html) for VPC B. @@ -41 +41 @@ Add a record to route traffic destined for the graph endpoint to the VPC endpoin -To use private hosted zones, `enableDnsHostnames` and `enableDnsSupport` should be set to `true` for both VPCs. Depending on your networking configuration, other considerations may apply when using private hosted zones. See [Route 53 private hosted zone considerations](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html) documentation to validate your setup. +To use private hosted zones, `enableDnsHostnames` and `enableDnsSupport` should be set to `true` for both VPCs. Depending on your networking configuration, other considerations may apply when using private hosted zones. See [Route 53 private hosted zone considerations](https://docs.aws.amazon.com//Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html) documentation to validate your setup. @@ -45 +45 @@ To use private hosted zones, `enableDnsHostnames` and `enableDnsSupport` should -In addition to the network connectivity established in prior steps, if the client in VPC B is in a different account (Account B), they will also need appropriate credentials to access the Neptune Analytics graph in VPC A (in Account A). You can use [ cross-account IAM roles ](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html#access_policies-cross-account-using-roles) to give permissions to the client. +In addition to the network connectivity established in prior steps, if the client in VPC B is in a different account (Account B), they will also need appropriate credentials to access the Neptune Analytics graph in VPC A (in Account A). You can use [ cross-account IAM roles ](https://docs.aws.amazon.com//IAM/latest/UserGuide/access_policies-cross-account-resource-access.html#access_policies-cross-account-using-roles) to give permissions to the client.