Documentation - Redise Cloud Private

open all | close all

Creating a Subscription in Redise Cloud Private

What is a Subscription?

A Redise Cloud Private (RCP) subscription consists of a selected cloud provider (and respective region, e.g. “AWS – US-West-2”), architectural model, memory limit and feature set. You can have multiple subscriptions in different providers and regions, all easily managed from a single console.


  • AWS Account – RCP is deployed into your AWS environment under a special account you create specifically for it.
  • AWS User – RCP relies on a user in Amazon Identity and Account Management (IAM) with specific privileges in order to create, maintain, and manage your RCP cluster and databases. See “Creating an AWS user for Redise Cloud Private” for help creating this user and the necessary roles, policies, etc.

Create a New Subscription

Creating a subscription is a four step process:

  1. Setup – Select the general settings and input the required credentials for the cloud user account.
  2. Sizing – Describe the specification of the databases you want to provision. After this step RCP will calculate the optimal configuration and required infrastructure.
  3. Review & Create – You will be presented with the required infrastructure and the subscription price. Enter your payment method and you are pretty much done.
  4. Provisioning – Automatically set up the relevant infrastructure and provision the databases.


For a new subscription, you will need to provide the following:

  1. A subscription name
  2. Your cloud provider (currently only AWS is supported; other cloud providers will be added in the future)
  3. The cloud region (e.g. “us-west-2”) you want your databases to be created in. This should be the in same region as the applications that will be connecting as you will be using AWS’ VPC Peering.
  4. Multi-AZ – Select whether or not the cluster should span Availability Zones for better high availability. To work optimally, make sure the selected region contains at least three availability zones.
  5. Select whether you want the subscription to support databases with the ability to span RAM only or RAM + Flash Memory.
  6. Under RCP dedicated AWS account, please create an AWS user in IAM specifically for Redise Cloud Private use as instructed in “Creating an AWS user for Redise Cloud Private.”
  7. For the user created in step six, please supply the following details:
    1. AWS_ACCESS_KEY_ID – RCP user’s AWS access key
    2. AWS_SECRET_ACCESS_KEY – RCP user’s AWS secret key
    3. AWS Console User – RCP AWS console user
    4. AWS Console password – RCP console user’s password
    5. IAM Users sign-in link – This is the link you use to log into the AWS console (e.g.
  8. Please provide the required Deployment CIDR – This is an IPv4 subnet, in CIDR notation, that you would like RCP to use.

Once you have made your selections, click “Continue” to finalize your subscription. RCP will authenticate the credentials with AWS and proceed to the next step.


Now you will have to define the databases you want to provision. Each row in the table represents a group of databases that share the same specifications.

For each row, select the following:

  1. Protocol – Select the relevant database type, either Redis or Memcached
  2. The estimated size of your data. For high availability, replication is on by default therefore double your actual dataset size. Minimum value is 1GB.
  3. Throughput – The estimated total throughput you expect from your database. The units are ops/sec.
  4. Data persistence – Select the relevant data persistence policy for your database.
  5. Enter the number of databases with these settings that you would like to provision.

Once complete, save the row by clicking the “Save” button. Add more rows by clicking the “+” button.

Once done, click the “Continue” button. The system may take a moment to calculate the optimized cloud infrastructure based on your inputs.

Review & Activate

Once planning is complete, please review the subscription and database information presented. Then select an existing payment method or click on the “+” button to add a new payment method.


Select the “Continue” button to create the subscription and deploy the database(s). The subscription will show a “Pending” status and take approximately ten to fifteen minutes to create. You will receive an email once your databases are ready to use.

Once provisioning is complete, please set up a peer between your application VPC and RCP VPC. To find out what your RCP VPC is, either go to View subscription or check the AWS console. To better understand how to set up VPC peering, please consult AWS documentation on the subject.

Once the peering was established please define the the relevant routing groups on your application account and RCP account.

For more information and pricing, please go here.

Viewing Subscriptions

To view the details of a subscription click “Subscriptions” in the menu, and then click on the name of the Subscription you wish to view.

There are three things you can change about an existing subscription:

  1. Subscription name
  2. Payment method used
  3. AWS credentials that RCP utilizes

To edit an item, click on the pencil icon to the right of it.

In addition, you can see:

  • The number of shards purchased and their cost
  • The underlying resources that your subscription is running on

To delete a subscription, click on the “Delete” button at the bottom of the form. You will be prompted to confirm before your subscription is actually deleted. The delete will only occur if the subscription does not have any databases. If it does, you must first delete the databases.