AWS AmazonElastiCache documentation change
Summary
Consistently replaced 'cache cluster' with 'cluster' in NAT instance configuration documentation
Security assessment
This is a terminology standardization change. The modifications do not alter security controls, vulnerability mitigations, or access management guidance. The proxy performance impact statement remains unchanged in security context.
Diff
diff --git a/AmazonElastiCache/latest/dg/accessing-elasticache.md b/AmazonElastiCache/latest/dg/accessing-elasticache.md index 5a1377647..259ec4986 100644 --- a//AmazonElastiCache/latest/dg/accessing-elasticache.md +++ b//AmazonElastiCache/latest/dg/accessing-elasticache.md @@ -86 +86 @@ The following considerations should be kept in mind when accessing your ElastiCa - * Clients connect to the EIP and cache port of the NAT instance. Port forwarding on the NAT instance forwards traffic to the appropriate cache cluster node. + * Clients connect to the EIP and cache port of the NAT instance. Port forwarding on the NAT instance forwards traffic to the appropriate cluster node. @@ -97 +97 @@ This approach should be used for testing and development purposes only. It is no - * The NAT instance is acting as a proxy between clients and multiple clusters. The addition of a proxy impacts the performance of the cache cluster. The impact increases with number of cache clusters you are accessing through the NAT instance. + * The NAT instance is acting as a proxy between clients and multiple clusters. The addition of a proxy impacts the performance of the cluster. The impact increases with number of clusters you are accessing through the NAT instance. @@ -158 +158 @@ You also need to enable IP forwarding, which is disabled by default: - 1. Create a NAT instance in the same VPC as your cache cluster but in a public subnet. + 1. Create a NAT instance in the same VPC as your cluster but in a public subnet. @@ -164 +164 @@ For information about creating a NAT instance, see [NAT Instances](https://docs. - 2. Create security group rules for the cache cluster and NAT instance. + 2. Create security group rules for the cluster and NAT instance.