AWS neptune documentation change
Summary
Fixed URL in security best practices reference
Security assessment
Updates a documentation link but doesn't modify the existing security recommendation about credential management.
Diff
diff --git a/neptune/latest/userguide/iam-auth-connecting-python.md b/neptune/latest/userguide/iam-auth-connecting-python.md index 6ffd3e3dd..029b60d7d 100644 --- a//neptune/latest/userguide/iam-auth-connecting-python.md +++ b//neptune/latest/userguide/iam-auth-connecting-python.md @@ -15 +15 @@ To work with this example program, you need the following: - * An access key (access key ID and secret access key) in environment variables named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. As a best practice, we recommend that you do _not_ embed credentials in code. For more information, see [Best Practices for AWS accounts](https://docs.aws.amazon.com/accounts/latest/reference/best-practices.html) in the _AWS Account Management Reference Guide_. + * An access key (access key ID and secret access key) in environment variables named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. As a best practice, we recommend that you do _not_ embed credentials in code. For more information, see [Best Practices for AWS accounts](https://docs.aws.amazon.com//accounts/latest/reference/best-practices.html) in the _AWS Account Management Reference Guide_.