AWS neptune-analytics documentation change
Summary
Fixed broken IAM URL and standardized documentation links by adding double slashes after domain
Security assessment
Changes only correct URL formatting and fix a broken IAM link. No security vulnerabilities are addressed, and no new security documentation is added.
Diff
diff --git a/neptune-analytics/latest/userguide/gettingStarted-connecting.md b/neptune-analytics/latest/userguide/gettingStarted-connecting.md index 22eae2a80..8eedd9b4a 100644 --- a//neptune-analytics/latest/userguide/gettingStarted-connecting.md +++ b//neptune-analytics/latest/userguide/gettingStarted-connecting.md @@ -11 +11 @@ If your graph is configured for public connectivity, you can connect to your gra -Graphs are created with public connectivity disabled by default. However, this can be configured by enabling public connectivity at [graph creation](https://docs.aws.amazon.com/neptune-analytics/latest/apiref/API_CreateGraph.html) or by [updating the graph configuration](https://docs.aws.amazon.com/neptune-analytics/latest/apiref/API_UpdateGraph.html) post-creation. +Graphs are created with public connectivity disabled by default. However, this can be configured by enabling public connectivity at [graph creation](https://docs.aws.amazon.com//neptune-analytics/latest/apiref/API_CreateGraph.html) or by [updating the graph configuration](https://docs.aws.amazon.com//neptune-analytics/latest/apiref/API_UpdateGraph.html) post-creation. @@ -15 +15 @@ Graphs are created with public connectivity disabled by default. However, this c -All Neptune Analytics graphs are configured to use AWS Identity and Access Management ([IAM](https://aws.amazon.com/https://aws.amazon.com/iam/)) for authentication and authorization. This means that all requests to the graph should be signed using AWS Signature Version 4 [(SIGV4)](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html). If you are using the AWS CLI or SDK to connect, then the signing of the requests is handled by the client library. The library requires the user to provide the credentials to sign using one of the known methods. You can also make HTTP requests to the APIs by using [AWSCurl](https://github.com/okigan/awscurl), which provides a curl like interface to make HTTP requests and supports SIGV4. For Neptune Analytics specific IAM documentation please refer to the Neptune Analytics user guide [Security IAM](https://docs.aws.amazon.com/neptune-analytics/latest/userguide/security-iam.html#security_iam_authentication) section. +All Neptune Analytics graphs are configured to use AWS Identity and Access Management ([IAM](https://aws.amazon.com/iam/)) for authentication and authorization. This means that all requests to the graph should be signed using AWS Signature Version 4 [(SIGV4)](https://docs.aws.amazon.com//AmazonS3/latest/API/sig-v4-authenticating-requests.html). If you are using the AWS CLI or SDK to connect, then the signing of the requests is handled by the client library. The library requires the user to provide the credentials to sign using one of the known methods. You can also make HTTP requests to the APIs by using [AWSCurl](https://github.com/okigan/awscurl), which provides a curl like interface to make HTTP requests and supports SIGV4. For Neptune Analytics specific IAM documentation please refer to the Neptune Analytics user guide [Security IAM](https://docs.aws.amazon.com//neptune-analytics/latest/userguide/security-iam.html#security_iam_authentication) section.