AWS AmazonElastiCache documentation change
Summary
Minor grammatical updates replacing 'In order to' with 'To' in security group port requirement statements
Security assessment
Changes are purely grammatical improvements without addressing any vulnerabilities or security weaknesses. No CVEs, security advisories, or vulnerability mitigations are mentioned.
Diff
diff --git a/AmazonElastiCache/latest/dg/set-up.md b/AmazonElastiCache/latest/dg/set-up.md index c46911d30..2b6f3d595 100644 --- a//AmazonElastiCache/latest/dg/set-up.md +++ b//AmazonElastiCache/latest/dg/set-up.md @@ -81 +81 @@ You will need to setup an EC2 instance from which you will connect to your cache -ElastiCache node-based clusters use port 6379 for Valkey and Redis OSS commands, and ElastiCache serverless uses both port 6379 and port 6380. In order to successfully connect and execute Valkey or Redis OSS commands from your EC2 instance, your security group must allow access to these ports as needed. +ElastiCache node-based clusters use port 6379 for Valkey and Redis OSS commands, and ElastiCache serverless uses both port 6379 and port 6380. To successfully connect and execute Valkey or Redis OSS commands from your EC2 instance, your security group must allow access to these ports as needed. @@ -94 +94 @@ Many clients establish connections to both ports even if not actively using Read -ElastiCache for Memcached uses the 11211 and 11212 ports to accept Memcached commands. In order to successfully connect and execute Memcached commands from your EC2 instance, your security group must allow access to these ports. +ElastiCache for Memcached uses the 11211 and 11212 ports to accept Memcached commands. To successfully connect and execute Memcached commands from your EC2 instance, your security group must allow access to these ports.