AWS AmazonElastiCache: Fix broken URLs in IAM migration documentation
Summary
Corrected broken hyperlinks for AWS Signature Version 4 documentation by removing double slashes in URLs.
Security assessment
The change fixes broken URLs but does not alter security content; it maintains existing guidance on IAM authentication.
Evidence
+IAM authentication provides enhanced security by eliminating the need for long-lived passwords. Instead, applications generate short-lived authentication tokens (valid for up to 15 minutes) using the [AWS Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html).
Diff
diff --git a/AmazonElastiCache/latest/dg/auth-to-iam-migration.md b/AmazonElastiCache/latest/dg/auth-to-iam-migration.md index a772cc87f..3cae73f3f 100644 --- a//AmazonElastiCache/latest/dg/auth-to-iam-migration.md +++ b//AmazonElastiCache/latest/dg/auth-to-iam-migration.md @@ -19 +19 @@ We recommend testing this migration in a non-production environment before apply -IAM authentication provides enhanced security by eliminating the need for long-lived passwords. Instead, applications generate short-lived authentication tokens (valid for up to 15 minutes) using the [AWS Signature Version 4 signing process](https://docs.aws.amazon.com//general/latest/gr/signature-version-4.html). +IAM authentication provides enhanced security by eliminating the need for long-lived passwords. Instead, applications generate short-lived authentication tokens (valid for up to 15 minutes) using the [AWS Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html). @@ -249 +249 @@ After completing Step 2, your cache supports both authentication methods. Verify -Generate a short-lived IAM authentication token using an [AWS SigV4 pre-signed request](https://docs.aws.amazon.com//general/latest/gr/sigv4-signed-request-examples.html). The following Python example demonstrates token generation. +Generate a short-lived IAM authentication token using an [AWS SigV4 pre-signed request](https://docs.aws.amazon.com/general/latest/gr/sigv4-signed-request-examples.html). The following Python example demonstrates token generation. @@ -318 +318 @@ Run the following command to validate the username: -For Java applications, use the default AWS Credentials provider chain to generate temporary security credentials. For more information, see [Authenticating with IAM](./auth-iam.html). For other languages, generate the IAM authentication token using the [AWS Signature Version 4 signing process](https://docs.aws.amazon.com//general/latest/gr/signature-version-4.html) and pass it as the password in your client's `AUTH` command. +For Java applications, use the default AWS Credentials provider chain to generate temporary security credentials. For more information, see [Authenticating with IAM](./auth-iam.html). For other languages, generate the IAM authentication token using the [AWS Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) and pass it as the password in your client's `AUTH` command.