AWS AmazonElastiCache documentation change
Summary
Minor wording change from 'creating and reading from replicas' to 'reading from replicas' in the context of read performance optimization
Security assessment
This is a minor editorial correction that clarifies users should read from existing replicas rather than create them. No security implications are mentioned or implied in this change. It's purely a documentation clarification about performance best practices.
Diff
diff --git a/AmazonElastiCache/latest/dg/GettingStarted.serverless-valkey.step2.md b/AmazonElastiCache/latest/dg/GettingStarted.serverless-valkey.step2.md index a68acd8cc..d0b130d32 100644 --- a//AmazonElastiCache/latest/dg/GettingStarted.serverless-valkey.step2.md +++ b//AmazonElastiCache/latest/dg/GettingStarted.serverless-valkey.step2.md @@ -13 +13 @@ This section also assumes that you have setup VPC access and security group sett -In addition to the steps below, if you have a large or global application you can greatly increase read performance by creating and reading from replicas. For more information on this more advanced step see [Best Practices for using Read Replicas](./ReadReplicas.html). +In addition to the steps below, if you have a large or global application you can greatly increase read performance by reading from replicas. For more information on this more advanced step see [Best Practices for using Read Replicas](./ReadReplicas.html).