Skip to main content

Decide on Elasticache Redis Requirements

Problem

We need to define the use-cases and outline soft requirements for Elasticache Redis.

Context

Amazon ElastiCache for Redis is Amazon’s fully managed version of Open Source https://redis.io/ in-memory data store that provides sub-millisecond latency and powers some of the largest websites out there. Any applications you have that depend on Redis can work seamlessly with ElastiCache Redis without any code changes.

See https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/nodes-select-size.html for Amazon’s recommendations on right-sizing clusters.

Considered Options

info

Ideally, share a screenshot of any existing Elasticache redis requirements and we can provision accordingly.

RequirementRecommendationDescription
Cache EngineRedis
Instance family
Encryption in TransitNoBy default, we don’t require this as


:::info
Native TLS was not supported prior to open source Redis version 6.0. As a result, not every Redis client library supports TLS.
https://redis.io/topics/encryption


:::
Encryption at Rest
Security Group Restrictions10.0.0.0/0
Automated failoveryes
Auto minor upgradeN/AAuto Minor Upgrade is only supported for engine type "redis" and if the engine version is 6 or higher.

(See: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/VersionManagement.html )
Multi-az enableddeployed across 2 AZs (private subnets)
Number of nodes
Cluster Mode Enabled
AWS Backup requirementshttps://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/backups.html
Additional options

Consequences

  • We’ll provision Elasticache Redis using our elasticache-redis component.

  • Define the catalog entries for the various Redis configurations

  • Enable AWS backups, as necessary

References