Step 1: Create an ApsaraDB for Redis instance

Select a series type and specification

Before you create an ApsaraDB for Redis instance, you must select an instance type based on various factors, such as performance, price, and workload. For more information, see Best practices for instance type selection.

Create an ApsaraDB for Redis Community Edition instance or a performance-enhanced instance of ApsaraDB for Redis Enhanced Edition (Tair)

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 product type.

   

   • Subscription (Local Disk, Including Tair): You are charged when you create the instance that uses local disks. We recommend that you select this product type for long-term use because it is more cost-effective than the product type that uses the pay-as-you-go billing method. Higher discounts are offered for longer subscription periods.
   • Pay-as-you-go (Local Disk, Including Tair): You are charged for using the pay-as-you-go instance on an hourly basis. We recommend that you select this product type for short-term use. You can release your pay-as-you-go instance to reduce costs when it is no longer used.
4. Set the instance parameters, as described in the following table.

   Parameter	Description
   Region and Zone	The region in which you want to create the 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 the internal network, make sure that the ApsaraDB for Redis instance is deployed in the same region as Elastic Compute Service (ECS) instances that need to access the ApsaraDB for Redis instance. Otherwise, the ECS instances can access the ApsaraDB for Redis instance only over the Internet. Connections over the Internet may degrade the service performance.
   Zone	The zone in which you want to create the ApsaraDB for Redis instance. Each region has multiple isolated locations that are known as zones. Each zone has its own independent power supply and network. To minimize the network latency between an ECS instance and an ApsaraDB for Redis instance that are deployed in the same zone, connect them over the internal network. Note To implement zone-disaster recovery, you can deploy the ApsaraDB for Redis instance across multiple zones.
   Network Type	This parameter is set to VPC and cannot be modified. A virtual private cloud (VPC) is an isolated network that provides higher security and better performance than the traditional classic network. Notice Make sure that the ApsaraDB for Redis instance is connected to the same VPC as the ECS instances or ApsaraDB RDS instances that need to access the ApsaraDB for Redis instance. Otherwise, the ECS instances or ApsaraDB RDS instances cannot access the ApsaraDB for Redis instance over the internal network.
   VPC	The VPC in which you want to create the ApsaraDB for Redis instance. If you do not have a VPC, create one first. For more information, see Create and manage a VPC.
   VSwitch	The vSwitch to be used by the ApsaraDB for Redis instance in the VPC. If no vSwitches are created in the VPC in the current zone, create a vSwitch as needed. For more information, see Work with vSwitches.
   Edition	Community Edition: This edition is compatible with the open source Redis protocol and provides high performance. Enhanced Edition (Tair): This edition is developed based on ApsaraDB for Redis Community Edition. ApsaraDB for Redis Enhanced Edition (Tair) is optimized in terms of performance, storage, and data schemas. For more information, see Overview.
   Series	Enhanced Performance: uses a multi-threading model. This parameter is available only if the Edition parameter is set to Enhanced Edition (Tair). The performance of this series is three times that of a Community Edition instance of the same specifications. This series also provides multiple data schema modules to simplify development. For more information, see Performance-enhanced instances. Note Hybrid-storage instances are discontinued. For more information, see Sales of ApsaraDB for Redis hybrid-storage instances are discontinued.
   Version	The engine version of the ApsaraDB for Redis instance.
   Architecture Type	Cluster: eliminates the performance bottleneck that is caused by a single-threading model. You can use the high-performance cluster instance to process large-capacity workloads. Standard: runs in a master-replica architecture, provides high-performance caching services, and ensures high data reliability. Read-Write Splitting: ensures high availability and 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 reduces the loads on the master node and minimizes the O&M cost. For more information, see Overview.
   Shards	The number of data shards for the cluster instance. Data is distributed across the data shards in the cluster instance. Note This parameter can be modified only if the Architecture Type parameter is set to Cluster.
   Node Type	If you set the Architecture Type parameter to Cluster or Standard, this parameter is set to Master-Replica and cannot be modified. If you set the Architecture Type parameter to Read-Write Splitting, you can choose the node type based on the number of read replicas.
   Instance Class	The instance specifications. Each option contains a group of configurations, such as the memory capacity, maximum number of concurrent connections, and maximum 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 data shard of a cluster instance is 30 to 50 MB. The total size of the metadata for a cluster equals the sum of metadata on all data shards of the cluster.
   Password Setting	Later: Set a password after the instance is created. For more information, see Change or reset the password. Now: Enter a 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. The following special characters are supported: ! @ # $ % ^ & * ( ) _ + - =.
   Quantity	The number of instances that you want to create. The instances have the same specifications. You can create up to 99 instances.
   Instance Name	The name of the instance, which is used to identify and manage the instance.
   Duration	If you select the Subscription billing method, you must specify the duration and select whether to enable auto-renewal.
   Resource Group	The resource group to which the instance belongs. For more information, see What is Resource Management?.

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 1 to 5 minutes. Then, you can find the new ApsaraDB for Redis instance in the ApsaraDB for Redis console.

Create a persistent memory-optimized or storage-optimized instance of ApsaraDB for Redis Enhanced Edition (Tair)

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, set the Product Type parameter to Tair (Subscription).
   

   Note Only the subscription billing method is supported. In this billing method, you are charged when you create the instance.
4. Set the instance parameters, as described in the following table.

   Parameter	Description
   Types	Tair Persistent Memory: allows users to store and query data in persistent memory. This instance type provides command-level persistence capabilities. It is suitable for scenarios that require high performance and data consistency. For more information, see Persistent memory-optimized instances. Tair Massive Storage: allows users to store and query data in enhanced solid-state disks (ESSDs). This instance type provides command-level persistence capabilities and large storage capacities. It is suitable for scenarios that require moderate performance and low costs. For more information, see Storage-optimized instances.
   Districts and Regions	The region in which you want to create the 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 the internal network, make sure that the ApsaraDB for Redis instance is deployed in the same region as Elastic Compute Service (ECS) instances that need to access the ApsaraDB for Redis instance. Otherwise, the ECS instances can access the ApsaraDB for Redis instance only over the Internet. Connections over the Internet may degrade the service performance.
   Primary Zone	The zone in which you want to create the ApsaraDB for Redis instance. Each region has multiple isolated locations that are known as zones. Each zone has its own independent power supply and network. To minimize the network latency between an ECS instance and an ApsaraDB for Redis instance that are deployed in the same zone, connect them over the internal network. Note To implement zone-disaster recovery, you can deploy the ApsaraDB for Redis instance across multiple zones.
   Network Type	This parameter is set to VPC and cannot be modified. A VPC is an isolated network that provides higher security and better performance than the traditional classic network. Notice Make sure that the ApsaraDB for Redis instance is connected to the same VPC as the ECS instances or ApsaraDB RDS instances that need to access the ApsaraDB for Redis instance. Otherwise, the ECS instances or ApsaraDB RDS instances cannot access the ApsaraDB for Redis instance over the internal network.
   VPC	The VPC in which you want to create the ApsaraDB for Redis instance. If you do not have a VPC, create one first. For more information, see Create and manage a VPC.
   vSwitch	The vSwitch to be used by the ApsaraDB for Redis instance in the VPC. If no vSwitches are created in the VPC in the current zone, create a vSwitch as needed. For more information, see Work with vSwitches.
   Architecture	Standalone: uses the master-replica architecture. For more information, see Standard master-replica instances. Cluster: uses a sharded cluster architecture. For more information, see Cluster master-replica instances. Note Storage-optimized instances do not support the cluster architecture.
   Shard Specification	The instance specifications. Each option contains a group of configurations, such as the memory capacity, maximum number of concurrent connections, and maximum bandwidth. For more information, see Persistent memory-optimized instances and Storage-optimized instances. Note The database metadata is generated after you create an ApsaraDB for Redis instance. The size of the metadata on each data shard of a cluster instance is 30 to 50 MB. The total size of the metadata for a cluster equals the sum of metadata on all data shards of the cluster.
   Replicas	This parameter is set to 2 and cannot be modified. Each shard has a master node and a replica node to ensure high availability.
   Storage Class	This parameter is set to ESSD PL1 and cannot be modified. For more information about Alibaba Cloud ESSDs of the PL1 performance level, see ESSDs.
   Storage Space	If you set the Types parameter to Tair Massive Storage, you can select a storage size based on your business requirements. Note You cannot modify this parameter for a persistent memory-optimized instance. In a persistent memory-optimized instance, ESSDs are used only to store system operating data, such as logs and backup data. ESSDs are not used as the media to read or write data.
   Password Setting	Later: Set a password after the instance is created. For more information, see Change or reset the password. Now: Enter a 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. The following special characters are supported: ! @ # $ % ^ & * ( ) _ + - =.
   Instance Name	The name of the instance, which is used to identify and manage the instance.
   Subscription Duration	The subscription duration of the instance.
   Resource Group	The resource group to which the instance belongs. For more information, see What is Resource Management?.

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 1 to 5 minutes. Then, you can find the new ApsaraDB for Redis instance in the ApsaraDB for Redis console.

FAQ

• How long does it take to create an instance?

  The time that is required to create an instance depends on the number of data shards in 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 2 to 3 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.

  Note

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

  The following table describes the possible causes and solutions.

  Possible cause	Solution
  The region that you selected in the console is not the region in which the instance is deployed.	Log on to the ApsaraDB for Redis console and select the region in which 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 appears in 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.

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

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

Related operations