|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
After you have signed up for ElastiCache, you can create a cache cluster.
In this step, you will use the AWS Management Console to create a cache cluster with a single cache node. You can choose either Memcached or Redis as the cache engine software for this cluster.
The cache cluster you're about to launch will be live (and not running in a sandbox). You will incur the standard ElastiCache usage fees for the instance until you delete it. The total charges will be minimal (typically less than a dollar) if you complete the exercise described here in one sitting and delete your cache cluster when you are finished. For more information about ElastiCache usage rates, go to the ElastiCache product page.
In this section, you will use the AWS Management Console to create a cache cluster with a single cache node. You can choose either Memcached or Redis as the cache engine software for this cluster.
If you are a new ElastiCache user, your cache cluster will be launched in an Amazon Virtual Private Cloud environment (Amazon VPC); for more information, see Using ElastiCache with Amazon Virtual Private Cloud (VPC).
To launch a cache cluster
Sign in to the AWS Management Console and open the Amazon ElastiCache console at https://console.aws.amazon.com/elasticache/.
From the ElastiCache Console Dashboard, click Launch Cache Cluster to start the Launch Cache Cluster Wizard.
On the Cache Cluster Details page, in the Name text box, enter a name for your cache cluster.
In the Engine box, click the cache engine software that you want to run, memcached or redis.
In the Number of Nodes text box, enter 1.
In the Cache Port text box, you can specify a new port number for your cache cluster, or leave it at its default value:
For Memcached, the default port number is 11211.
For Redis, the default port number is 6379.
In the Cache Subnet Group box, click the subnet where you would like to launch the cache cluster:
VPC (recommended) – The cache cluster will be launched in an Amazon Virtual Private Cloud environment. If you are a new ElastiCache user, a VPC is automatically created on your behalf, along with a cache subnet group named default; you should use the default cache subnet group for this exercise.
Not in VPC – The cache cluster will be launched in the AWS public cloud.
In the Topic for SNS notifications box, click Disable Notifications.
Leave the rest of the options on the Cache Cluster Details page at their default values, and then click Continue.
On the Additional Configuration page, you can specify a security group, cache parameter group, and maintenance window for your cache cluster.
If you are launching your cache cluster in a VPC, the Security Group portion of the page will show the VPC security group:
If you chose to launch your cache cluster outside of a VPC, the Security Group portion of the page will show a cache security group instead:
For this exercise, leave all of the values as they are, and then click Continue.
On the Review page, review the options for your cache cluster:
Review the options for your cache cluster:
If you need to correct any options, click Back to return to previous panels and make corrections.
When all your options are entered as you want them, click Launch to launch your new cache cluster.
After you click the Launch button, a message displays stating that your cache cluster is being created.
The launch process can take a few minutes to complete.
When the My Cache Clusters panel appears, your cache cluster is displayed in the list with the creating status until the creation is complete and your cache cluster is ready for use.