ApsaraDB for Redis offers two editions, Community Edition and Enhanced Edition (Tair). ApsaraDB for Redis Enhanced Edition (Tair) has two instance types: the performance-enhanced instances and the hybrid-storage instances. This topic describes how to create an ApsaraDB for Redis instance to meet your business requirements.


  • An Alibaba Cloud account is created. For more information, see Create your Alibaba Cloud account.
  • To create a pay-as-you-go instance, you must keep sufficient balance in your account.


For more information, see Billing items and pricing.


  1. Log on to the ApsaraDB for Redis console.
  2. In the upper-right corner of the page, click Create Instance.
  3. On the buy page, select a billing method for the new instance.
    • Subscription: You must pay for an instance when you create it. We recommend that you select this billing method for long-term subscriptions because it is more cost-effective than the pay-as-you-go billing method. Higher discounts are offered for longer subscription periods.
    • Pay-as-you-go: You must pay for the instance on an hourly basis based on your actual usage. We recommend that you select this billing method for short-term subscriptions. You can release your pay-as-you-go instance to reduce costs when it is no longer used.
    Note You can switch the billing method from pay-as-you-go to subscription, but cannot switch it from subscription to pay-as-you-go.
  4. Configure the instance parameters. The following table describes related parameters.
    Section Parameter Description
    Basic Configuration Region The region where you want to create your ApsaraDB for Redis instance. You cannot change the region after the instance is created.
    • To maximize access speed, we recommend that you select a region that is close to the geographic location of your users.
    • To enable connections over an internal network, make sure that the ApsaraDB for Redis instance is deployed in the same region as an Elastic Compute Service (ECS) instance. Otherwise, the instances must communicate with each other only over the Internet. Connections over the Internet may degrade the service performance.
    Zone Select a zone that belongs to the region. Each region has multiple isolated locations that are known as zones. Each zone has its own independent power supply and network. An ECS instance and an ApsaraDB for Redis instance in the same zone can be connected over the internal network with minimum network latency.
    Note To implement zone-to-zone disaster recovery, you can deploy the ApsaraDB for Redis instance across multiple zones.
    Network Type
    • VPC: A virtual private cloud (VPC) is an isolated network with higher security and better performance than a classic network. We recommend that you select the VPC network type.
    • Classic Network: Cloud services in the classic network are not isolated. Access control to cloud services in a classic network is implemented by the security groups or whitelist policies of the services.
    • To enable connections over an internal network, make sure that the ApsaraDB for Redis instance is connected to the same type of network as an ECS instance or an ApsaraDB for RDS instance.
    • If only the VPC network type is used to enable connections, make sure that the ApsaraDB for Redis instance is connected to the same VPC as the ECS instance or ApsaraDB for RDS instance.
    • You can change the network type of ApsaraDB for Redis instances from Classic Network to VPC. However, you cannot change the network type from VPC to Classic Network.
    VPC Select a VPC in which you want to create the ApsaraDB for Redis instance. For more information about VPC, see Create a VPC.
    VSwitch Select a vSwitch for the VPC. If no vSwitches are created for the VPC in the current zone, see Create a vSwitch.
    Instance Edition
    • Community Edition: This edition is compatible with the Redis protocol and provides database solutions that support hybrid storage in memory and disks.
    • Enhanced Edition (Tair): This edition is developed based on ApsaraDB for Redis Community Edition. It is optimized in terms of performance, storage, and data schemas. For more information, see Overview.
    Series If you set Edition to Enhanced Edition (Tair), you have the following series options:
    • Enhanced Performance: uses a multi-threading model. The performance of this series is three times that of a Community Edition instance of the same specification. It also provides multiple data schema modules to simplify development. For more information, see Performance-enhanced instances.
    • Hybrid Storage: integrates the benefits of the in-memory and on-disk persistence. This series can reduce the storage costs and allows you to maintain a proper balance between the performance and cost. For more information, see Hybrid-storage instances.
    Version The engine version of the ApsaraDB for Redis instance.
    Note The instances that run Redis 2.8 will soon be phased out. We recommend that you create an instance that uses the latest engine version to use more features and achieve stable performance.
    Architecture Type
    • Cluster: resolves the performance bottleneck that is caused by a single-threading model. You can use the instances to process large-capacity or high-performance workloads.
    • Standard: runs in a master-replica architecture, and provides high-performance caching services and high data reliability.
    • Read-Write Splitting: ensures high availability, high performance, and supports multiple specifications. The read/write splitting architecture allows a large number of concurrent requests to read hot data from read replicas. This can reduce the loads on the master node and minimize your costs of operations and maintenance.
    For more information, see Overview.
    Shards Specifies the number of shards for the Redis cluster instance. Data is distributed across the shards in the cluster.
    Note This parameter is supported only when you set Architecture Type to Cluster.
    Node Type
    • If you set Architecture Type to Cluster or Standard, Master-Replica is the only available option. This dual-node hot-standby architecture provides data persistence with high data reliability and availability.
    • If you set Architecture Type to Read-Write Splitting, you can choose the node type based on the number of read-only replicas.
    Instance Class Each instance type contains a group of configurations, such as the memory capacity, maximum number of concurrent connections, and maximum internal bandwidth. For more information, see Overview.
    Note The database metadata is generated after you create an ApsaraDB for Redis instance. The size of the metadata on each shard of cluster instances is 30 MB to 50 MB. The total size of the metadata for a cluster equals the sum of the size of metadata on each shard of the cluster.
    Password Setting
    • Later: Set the password after the instance is created. For more information, see Change or reset the password.
    • Now: Enter the password for the instance.
      • The password must be 8 to 32 characters in length.
      • The password must contain at least three of the following types of characters: uppercase letters, lowercase letters, digits, and special characters.
      • Supported special characters include ! @ # $ % ^ & * ( ) _ + - =
    Purchase Plan Instance Name Enter a name for the instance to identify and manage the instance.
    Quantity Specify the number of instances that you want to create. The instances have the same specifications. You can create up to 99 instances.
    Duration When you select the Subscription billing method, you must specify the duration and select whether to enable auto-renewal.
  5. Click Buy Now.
  6. On the Confirm Order page, read and accept ApsaraDB for Redis Agreement of Service and follow the instructions to pay for the instance.
    After the payment is complete, wait for one to five minutes. Then, you can find the new ApsaraDB for Redis instance in the ApsaraDB for Redis console.


  • Q: How long does it take for the system to create an instance?

    A: The time it takes to create an instance depends on the number of data shards on the instance. A larger number of data shards require more resources. As a result, it takes more time to allocate resources. For example, it takes two to three minutes to create a standard master-replica instance, 10 to 15 minutes to create a 128-shard cluster master-replica instance, and 20 to 40 minutes to create a 256-shard cluster master-replica instance.

    • For Standard Edition instances, the amount of time depends on single-shard instances.
    • The primary node of a read/write splitting instance processes read and write requests. Each primary node is regarded as a shard. Each read replica is regarded as a shard.
  • Q: Why am I unable to find the created instance?

    A: This may be for the following reasons.

    Cause Solution
    You selected the wrong region in the console. Log on to the ApsaraDB for Redis console and reselect the region where the instance is deployed.
    The instance list in the ApsaraDB for Redis console is not updated or is updated before the instance is created. Wait for several minutes and then update the instance list to check whether the instance is added to the list.
    Resources are insufficient. The system may fail to create the instance due to insufficient resources. In this case, your payment is refunded. You can check your refund on the Orders page.

    After you confirm that the payment is refunded, you can try to create your instance in another zone. You can also submit a ticket.

  • Q: Why did I fail to create a standalone instance of ApsaraDB for Redis?

    A: Starting December 19, 2019, standalone instances of ApsaraDB for Redis were phased out. For more information, see Deprecated standalone instances of ApsaraDB for Redis.

Related operations

API Description
CreateInstance Creates an ApsaraDB for Redis instance.