Step 1: Create an ApsaraDB for Redis instance

1. Log on to the ApsaraDB for Redis console.
2. On the Instances page, click Create Instance.
3. Select a billing method.
   • Subscription: You pay for each subscription instance when you create the instance. We recommend that you select this billing method if you have long-term requirements because it is more cost-effective than the pay-as-you-go billing. Higher discounts are offered for longer subscription periods.
   • Pay-as-you-go: You pay for only what you use. The instance is billed on an hourly basis. We recommend that you choose the pay-as-you-go billing for short-term needs. You can release your pay-as-you-go instance to save costs when you no longer need the instance.
   Notice

   • You can change the billing method only from pay-as-you-go to subscription.
4. Set the parameters in the following table.

   Parameter	Description
   Region	The region where you want to create an ApsaraDB for Redis instance. You cannot change the region after you activate the instance. 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 can only communicate with each other over the Internet. Connections over the Internet may degrade the service performance.
   Zone	The zone where the ApsaraDB for Redis instance is deployed. Each zone is an independent geographic location within a region. You can manage your workloads in different zones of the same region with identical service experience.
   Network Type	Classic Network: a traditional network type. VPC: the recommended network type. A VPC network is an isolated virtual network that provides higher security and better performance than a classic network. Notice 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 network as an ECS instance or an 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.
   VSwitch	A VSwitch is the basic network module used to build a VPC network. If no VSwitch is available in the VPC network, we recommend that you create a VSwitch. For more information, see Create a VSwitch.
   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: This edition is developed on the basis of ApsaraDB for Redis Community Edition and has been optimized in terms of performance, storage, and data schemas. For more information, see Overview.
   Series	Enhanced Edition includes the following series: Performance-enhanced series. For more information, see Enhanced multi-threading performance and Integration of multiple Redis modules. Hybrid-storage series. For more information, see Hybrid-storage instances. Note Community Edition does not support these series.
   Version	ApsaraDB for Redis supports the following engine versions: 2.8 4.0 5.0 Note If the required database version does not appear, we recommend that you specify a different database edition or instance type. The ApsaraDB for Redis instances with Redis 2.8 will soon be phased out. We recommend that you create an instance with the latest engine version to use more features and achieve stable performance.
   Architecture Type	Cluster Standard Read-write Splitting For more information, see Overview.
   Shards	The number of shards on a cluster instance. Note You can specify the number of shards only on cluster instances.
   Node Type	If the architecture type is set to Standard or Cluster, the node type can only be set to Master-Replica. A master-replica node runs in a hot standby mode and supports data persistence. If the architecture type is set to Read-Write Splitting, the node type can be set to: 1 Read-only Replica 3 Read-only Replicas 5 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 After you create an ApsaraDB for Redis instance, metadata for a database is generated and uses a minimum amount of storage space. On an ApsaraDB for Redis instance of the standard architecture type, the size of metadata ranges from 30 MB to 50 MB. On each shard of an ApsaraDB for Redis instance of the cluster architecture type, the size of metadata ranges from 30 MB to 50 MB. In a cluster, the total amount of storage space that metadata uses equals the total size of metadata on each shard.

5. Set a password.
   • Now: In the Password field, enter a password.
   • Later: You can set a password after you create the instance. For more information, see Change the password.
6. Set Instance Name and Quantity. If you purchase a subscription instance, you must set Duration.
7. Click Buy Now.
8. On the Confirm Order page that appears, click ApsaraDB for KVStore (Subscription) Agreement of Service.
9. Read and select the ApsaraDB for KVStore (Subscription) Agreement of Service checkbox.
10. Click Pay.
    Note After you pay for the order, the system prompts that you have activated the instance. Then, wait up to five minutes to check the instance displayed in the console.

FAQ

• 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 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 primary node of a read/write splitting instance processes read and write requests. Each primary node is regarded as a shard, and each read replica is regarded as a shard.
• 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 are phased out. For more information, see Deprecated standalone instances of ApsaraDB for Redis.

Related API operations