Skip to main content
Service Catalog Version 0.78.1

Amazon ElastiCache for Memcached

View SourceFiltered Release Notes

Overview​

This service contains code to deploy a Memcached Cluster using Amazon ElastiCache. The cluster is managed by AWS and automatically handles automatic node discovery, recovery from failures, patching, and the ability to scale to large clusters of nodes.

ElastiCache for Memcached architectureElastiCache for Memcached architecture

Features​

  • Deploy a fully-managed Memcached cluster
  • Automatic detection and recovery from cache node failures
  • Automatic discovery of nodes within a cluster
  • 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!

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:

Reference​

  • alarms_sns_topic_arns — The ARNs of SNS topics where CloudWatch alarms (e.g., for CPU, memory, and disk space usage) should send notifications.
  • apply_immediately — Specifies whether any database modifications are applied immediately, or during the next maintenance window.
  • az_mode — Specifies whether the nodes in this Memcached node group are created in a single Availability Zone or created across multiple Availability Zones in the cluster's region. Valid values for this parameter are single-az or cross-az. If you want to choose cross-az, num_cache_nodes must be greater than 1.
  • 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 using alarms_sns_topic_arn.
  • 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. Must be unique in this region. Must be a lowercase string.
  • num_cache_nodes — The initial number of cache nodes that the cache cluster will have. Must be between 1 and 20.
  • port — The port number on which each of the cache nodes will accept connections (e.g. 11211).
  • subnet_ids — The list of IDs of the subnets in which to deploy the ElasticCache instances. The list must only contain subnets in vpc_id.
  • vpc_id — The ID of the VPC in which to deploy RDS.