Setting up - Amazon ElastiCache for Redis
Sign up for an Amazon Web Services accountSecure IAM usersGrant programmatic accessSet up permissionsSet up EC2Grant network accessSet up redis-cli
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Setting up

To set up ElastiCache:

Sign up for an Amazon Web Services account

If you do not have an Amazon Web Services account, use the following procedure to create one.

To sign up for Amazon Web Services

  1. Open http://www.amazonaws.cn/ and choose Sign Up.

  2. Follow the on-screen instructions.

Amazon sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to http://www.amazonaws.cn/ and choosing My Account.

Secure IAM users

After you sign up for an Amazon Web Services account, safeguard your administrative user by turning on multi-factor authentication (MFA). For instructions, see Enable a virtual MFA device for an IAM user (console) in the IAM User Guide.

To give other users access to your Amazon Web Services account resources, create IAM users. To secure your IAM users, turn on MFA and only give the IAM users the permissions needed to perform their tasks.

For more information about creating and securing IAM users, see the following topics in the IAM User Guide:

Grant programmatic access

Users need programmatic access if they want to interact with Amazon outside of the Amazon Web Services Management Console. The Amazon APIs and the Amazon Command Line Interface require access keys. Whenever possible, create temporary credentials that consist of an access key ID, a secret access key, and a security token that indicates when the credentials expire.

To grant users programmatic access, choose one of the following options.

Which user needs programmatic access? To By
IAM Use short-term credentials to sign programmatic requests to the Amazon CLI or Amazon APIs (directly or by using the Amazon SDKs). Following the instructions in Using temporary credentials with Amazon resources in the IAM User Guide.
IAM

(Not recommended)

Use long-term credentials to sign programmatic requests to the Amazon CLI or Amazon APIs (directly or by using the Amazon SDKs).		 Following the instructions in Managing access keys for IAM users in the IAM User Guide.
Related topics:

Set up your permissions (new ElastiCache users only)

To provide access, add permissions to your users, groups, or roles:

Amazon ElastiCache creates and uses service-linked roles to provision resources and access other Amazon resources and services on your behalf. For ElastiCache to create a service-linked role for you, use the Amazon-managed policy named AmazonElastiCacheFullAccess. This role comes preprovisioned with permission that the service requires to create a service-linked role on your behalf.

You might decide not to use the default policy and instead to use a custom-managed policy. In this case, make sure that you have either permissions to call iam:createServiceLinkedRole or that you have created the ElastiCache service-linked role.

For more information, see the following:

Set up EC2

You will need to setup an EC2 instance from which you will connect to your cache.

  • If you don’t already have an EC2 instance, learn how to setup an EC2 instance here: Getting started with EC2.

  • Your EC2 instance must be in the same VPC and have the same security group settings as your cache. By default, Amazon ElastiCache creates a cache in your default VPC and uses the default security group. To follow this tutorial, ensure that your EC2 instance is in the default VPC and has the default security group.

Grant network access from an Amazon VPC security group to your cache

ElastiCache self-designed clusters use port 6379 for Redis commands, and ElastiCache serverless uses both port 6379 and port 6380. In order to successfully connect and execute Redis commands from your EC2 instance, your security group must allow access to these ports as needed.

  1. Sign in to the Amazon Command Line Interface and open the Amazon EC2 console.

  2. In the navigation pane, under Network & Security, choose Security Groups.

  3. From the list of security groups, choose the security group for your Amazon VPC. Unless you created a security group for ElastiCache use, this security group will be named default.

  4. Choose the Inbound tab, and then:

    1. Choose Edit.

    2. Choose Add rule.

    3. In the Type column, choose Custom TCP rule.

    4. In the Port range box, type 6379.

    5. In the Source box, choose Anywhere which has the port range (0.0.0.0/0) so that any Amazon EC2 instance that you launch within your Amazon VPC can connect to your cache.

    6. If you are using ElastiCache serverless, add another rule by choosing Add rule.

    7. In the Type column, choose Custom TCP rule.

    8. In the Port rangebox, type 6380.

    9. In the Source box, choose Anywhere which has the port range (0.0.0.0/0) so that any Amazon EC2 instance that you launch within your Amazon VPC can connect to your cache.

    10. Choose Save

Download and set up redis-cli

  1. Connect to your Amazon EC2 instance using the connection utility of your choice. For instructions on how to connect to an Amazon EC2 instance, see the Amazon EC2 Getting Started Guide.

  2. Download and install redis-cli utility by running the appropriate command for your setup.

    Amazon Linux 2023

    sudo yum install redis6 -y

    Amazon Linux 2

    sudo amazon-linux-extras install epel -y
sudo yum install gcc jemalloc-devel openssl-devel tcl tcl-devel -y
sudo wget http://download.redis.io/redis-stable.tar.gz
sudo tar xvzf redis-stable.tar.gz
cd redis-stable
sudo make BUILD_TLS=yes
Note

  • When you install the redis6 package, it installs redis6-cli with default encryption support.

  • It is important to have build support for TLS when installing redis-cli. ElastiCache Serverless is only accessible when TLS is enabled.

  • If you are connecting to a cluster that isn't encrypted, you don't need the Build_TLS=yes option.