Memcached Layer Reference
Important
The AWS OpsWorks Stacks service reached end of life on May 26, 2024 and has been disabled for both new and existing customers.
We strongly recommend customers migrate their workloads to other solutions as soon as possible. If you have questions about migration, reach out to the AWS Support Team on AWS re:Post
Note
This layer is available only for Linux-based stacks.
Memcached
To use Memcached in a stack, create a Memcached layer and add one or more instances, which
function as Memcached servers. The instances automatically install Memcached and the stack's
other instances are able to access and use the Memcached servers. If you use a Rails App Server
layer, AWS OpsWorks Stacks automatically places a memcached.yml
configuration
file in the config directory of each instance in the layer. You can obtain the Memcached
server and port number from this file.
Short name: memcached
Compatibility: A Memcached layer is compatible with the following layers: custom, db-master, lb, monitoring-master, nodejs-app, php-app, rails-app, and web.
Open ports: A Memcached layer allows public access to port 22(SSH) and all ports from the stack's web servers, custom servers, and Rails, PHP, and Node.js application servers.
Autoassign Elastic IP addresses: Off by default
Default EBS volume: No
Default security group: AWS-OpsWorks-Memcached-Server
To configure a Memcached layer, you must specify the cache size, in MB.
Setup recipes:
-
opsworks_initial_setup
-
ssh_host_keys
-
ssh_users
-
mysql::client
-
dependencies
-
ebs
-
opsworks_ganglia::client
-
memcached
Configure recipes:
-
opsworks_ganglia::configure-client
-
ssh_users
-
agent_version
Deploy recipes:
-
deploy::default
Shutdown recipes:
-
opsworks_shutdown::default
-
memcached::stop
Installation:
-
AWS OpsWorks Stacks uses the instance's package installer to install Memcached and its log files in their default locations.