Reader endpoint (same DNS name as primary, port 6380 for read-optimized access; node-based reader endpoints use a separate DNS name on port 6379)
Node-based
6379
Valkey/Redis OSS data port (both primary and reader endpoints)
Node-based (cluster mode)
16379
Cluster bus port (node-to-node, auto-managed)
Node-based (Memcached)
11211
Memcached data port
Serverless (Memcached)
11211
Memcached serverless endpoint (TLS mandatory)
TLS note: TLS is mandatory for all serverless caches (Valkey/Redis OSS and Memcached). There is no option to disable in-transit encryption on serverless deployments.
Do not open 0.0.0.0/0 on any port. ElastiCache is VPC-internal only.
Do not use IP-based rules when security-group-based rules are possible. SG references survive IP changes.
Do not allow port ranges (e.g., 6379-6400). Use specific ports only.
Do not attach the cache to a default security group that allows all inbound from itself.
For serverless (Valkey/Redis OSS): open ports 6379 (primary) and 6380 (reader) from the app security group. The primary and reader endpoints use the same DNS name on different ports (6379 for primary, 6380 for read-optimized).
For serverless (Memcached): open port 11211 from the app security group.
PrivateLink (VPC Endpoints) covers ElastiCache control-plane APIs only (e.g., CreateCacheCluster, DescribeReplicationGroups). It does not provide data-plane connectivity to cache endpoints.
Cross-VPC data access requires VPC Peering, Transit Gateway (TGW), AWS Direct Connect, or site-to-site VPN. Use security group references (preferred, when peering supports it) or CIDR-based rules to allow traffic between the application VPC and the cache VPC.