AWS AmazonElastiCache: Rename troubleshooting section and update IAM example account ID
Summary
Cosmetic documentation edits: renames the 'Troubleshooting' heading/link to 'Troubleshooting public endpoint connections' and replaces the sample account ID 123456789012 with 111122223333 in the elasticache:Connect IAM policy example.
Security assessment
The only changed lines are a heading rename and a placeholder account ID swap in an IAM policy example; no security behavior, requirement, or vulnerability remediation is introduced.
Evidence
+## Troubleshooting public endpoint connections
Diff
diff --git a/AmazonElastiCache/latest/dg/connecting-public-endpoint.md b/AmazonElastiCache/latest/dg/connecting-public-endpoint.md index b4ff730..b9335d6 100644 --- a//AmazonElastiCache/latest/dg/connecting-public-endpoint.md +++ b//AmazonElastiCache/latest/dg/connecting-public-endpoint.md @@ -7 +7 @@ -IAM policy for connectingOption 1: GLIDE client with built-in IAMOption 2: Developer Toolkit for ElastiCacheOption 3: Manual SigV4 signingToken and session expirationTroubleshooting +IAM policy for connectingOption 1: GLIDE client with built-in IAMOption 2: Developer Toolkit for ElastiCacheOption 3: Manual SigV4 signingToken and session expirationTroubleshooting public endpoint connections @@ -34 +34 @@ All public endpoint connections require IAM authentication and TLS 1.3. There ar - * Troubleshooting + * Troubleshooting public endpoint connections @@ -53,2 +53,2 @@ Create an IAM policy that allows the `elasticache:Connect` action on the ElastiC - "arn:aws:elasticache:us-east-1:123456789012:serverlesscache:my-public-cache", - "arn:aws:elasticache:us-east-1:123456789012:user:default.iam-user" + "arn:aws:elasticache:us-east-1:111122223333:serverlesscache:my-public-cache", + "arn:aws:elasticache:us-east-1:111122223333:user:default.iam-user" @@ -205 +205 @@ Generate the IAM authentication token manually using the AWS SDK. For signing co -## Troubleshooting +## Troubleshooting public endpoint connections