Service Catalog Version 0.78.1 View SourceFiltered Release Notes
Amazon ElastiCache for Redis
Overview
This service contains code to deploy a Redis Cluster using Amazon ElastiCache. The cluster is managed by AWS and automatically handles standby failover, read replicas, backups, patching, and encryption.
ElastiCache for Redis architecture
Features
- Deploy a fully-managed Redis cluster
- Automatic failover to a standby in another availability zone
- Read replicas
- Automatic nightly snapshots
- Automatic cross account snapshots
- Automatic scaling of storage
- CloudWatch Alarms for alerting when CPU, memory, and disk metrics exceed certain thresholds
- Integrate with Kubernetes Service Discovery
Learn
note
This repo is a part of the Gruntwork Service Catalog, a collection of reusable, battle-tested, production ready infrastructure code. If you’ve never used the Service Catalog before, make sure to read How to use the Gruntwork Service Catalog!
- What is Amazon ElastiCache?
- Common gotchas with ElastiCache
- Amazon ElastiCache for Redis documentation: Amazon’s ElastiCache for Redis docs that cover core concepts such as the options and versions supported, security, backup & restore, and monitoring.
- Designing Data Intensive Applications: the best book we’ve found for understanding data systems, including relational databases, NoSQL, replication, sharding, consistency, and so on.
Deploy
Non-production deployment (quick start for learning)
If you just want to try this repo out for experimenting and learning, check out the following resources:
- examples/for-learning-and-testing folder: The
examples/for-learning-and-testing
folder contains standalone sample code optimized for learning, experimenting, and testing (but not direct production usage).
Production deployment
If you want to deploy this repo in production, check out the following resources:
- examples/for-production folder: The
examples/for-production
folder contains sample code optimized for direct usage in production. This is code from the Gruntwork Reference Architecture, and it shows you how we build an end-to-end, integrated tech stack on top of the Gruntwork Service Catalog.
Reference
- Inputs
- Outputs
alarms_sns_topic_arns
— The ARNs of SNS topics where CloudWatch alarms (e.g., for CPU, memory, and disk space usage) should send notifications.
allow_connections_from_cidr_blocks
— The list of network CIDR blocks to allow network access to ElastiCache from. One ofallow_connections_from_cidr_blocks
orallow_connections_from_security_groups
must be specified for the ElastiCache instances to be reachable.
allow_connections_from_security_groups
— The list of IDs or Security Groups to allow network access to ElastiCache from. All security groups must either be in the VPC specified byvpc_id
, or a peered VPC with the VPC specified byvpc_id
. One ofallow_connections_from_cidr_blocks
orallow_connections_from_security_groups
must be specified for the ElastiCache instances to be reachable.
apply_immediately
— Specifies whether any modifications are applied immediately, or during the next maintenance window.
cluster_mode
— Specifies the number of shards and replicas per shard in the cluster. The list should contain a single map with keys'num_node_groups
' and'replicas_per_node_group
' set to desired integer values.
enable_at_rest_encryption
— Whether to enable encryption at rest.
enable_automatic_failover
— Indicates whether Multi-AZ is enabled. When Multi-AZ is enabled, a read-only replica is automatically promoted to a read-write primary cluster if the existing primary cluster fails. If you specify true, you must specify a value greater than 1 forreplication_group_size
.
enable_cloudwatch_alarms
— Set to true to enable several basic CloudWatch alarms around CPU usage, memory usage, and disk space usage. If set to true, make sure to specify SNS topics to send notifications to usingalarms_sns_topic_arn
.
enable_multi_az
— Indicates whether Multi-AZ is enabled. When Multi-AZ is enabled, a read-only replica is automatically promoted to a read-write primary cluster if the existing primary cluster fails. If you specify true, you must specify a value greater than 1 forreplication_group_size
.
enable_transit_encryption
— Whether to enable encryption in transit.
instance_type
— The compute and memory capacity of the nodes (e.g. cache.m4.large).
maintenance_window
— Specifies the weekly time range for when maintenance on the cache cluster is performed (e.g. sun:05:00-sun:09:00). The format is ddd:hh24:mi-ddd:hh24:mi (24H Clock UTC). The minimum maintenance window is a 60 minute period.
name
— The name used to namespace all resources created by these templates, including the ElastiCache cluster itself (e.g. rediscache). Must be unique in this region. Must be a lowercase string.
parameter_group_name
— Name of the parameter group to associate with this cache cluster. This can be used to configure custom settings for the cluster.
port
— The port number on which each of the cache nodes will accept connections (e.g. 6379).
redis_version
— Version number of redis to use (e.g. 5.0.6).
replication_group_size
— The total number of nodes in the Redis Replication Group. E.g. 1 represents just the primary node, 2 represents the primary plus a single Read Replica.
snapshot_retention_limit
— The number of days for which ElastiCache will retain automatic cache cluster snapshots before deleting them. Set to 0 to disable snapshots.
snapshot_window
— The daily time range during which automated backups are created (e.g. 04:00-09:00). Time zone is UTC. Performance may be degraded while a backup runs. Set to empty string to disable snapshots.
sns_topic_for_notifications
— The ARN of the SNS Topic to which notifications will be sent when a Replication Group event happens, such as an automatic failover (e.g.arn:aws:sns:*:123456789012:my_sns_topic
). An empty string is a valid value if you do not wish to receive notifications via SNS.
subnet_ids
— The list of IDs of the subnets in which to deploy the ElasticCache instances. The list must only contain subnets invpc_id
.
tags
— A set of tags to set for the ElastiCache Replication Group.
vpc_id
— The ID of the VPC in which to deploy RDS.
cache_cluster_ids
— The list of AWS cache cluster ids where each one represents a Redis node.
cache_node_id
— The id of the ElastiCache node. Note: Each Redis cache cluster has only one node and its id is always 0001.
cache_port
— The port number on which each of the cache nodes will accept connections (e.g. 6379).
configuration_endpoint
— When cluster mode is enabled, use this endpoint for all operations. Redis will automatically determine which of the cluster's node to access.
primary_endpoint
— The primary endpoint is a DNS name that always resolves to the primary node in the Redis cluster.
reader_endpoint
— When cluster mode is disabled, use this endpoint for all read operations.