This topic describes how to create an ApsaraDB for Redis instance based on your business requirements.

Discounts and offers

You are offered a discount of up to 80% when you purchase an ApsaraDB for Redis instance for the first time during the specified promotion period. For more information, see ApsaraDB for Redis discounts and offers.

Procedure

  1. Use one of the following methods to open the buy page:
    • Open the ApsaraDB for Redis product landing page and click Buy Now.
      Note If you have not logged on to the Alibaba Cloud website by using an Alibaba Cloud account, after you click Buy Now, you are navigated to the logon page. Enter the username and password of your Alibaba Cloud account on this page.
    • Log on to the ApsaraDB for Redis console and click Create Instance.
  2. Select a billing method.
    • Subscription: When you create an ApsaraDB for Redis instance, you must pay for a purchase plan to use the service in the specified period. If you want to use the instance for long-term services, the subscription billing method is more cost-effective than the pay-as-you-go billing method. A longer purchase plan brings a higher discount.
    • Pay-as-you-go: You do not need to pay for an ApsaraDB for Redis instance when you create the instance. You are charged for the service on an hourly basis. This billing method is suitable for short-term services. You can release idle instances to save costs.
    Notice You can switch the billing method from pay-as-you-go to subscription, but cannot switch it from subscription to pay-as-you-go.
  3. Set the following parameters on the buy page.
    Parameter Description
    Region The geographic location where the instance is located. You cannot change the region after you activate the instance.
    • We recommend that you select a region close to end users to increase the service performance.
    • To enable connections over an internal network, make sure that the ApsaraDB for Redis instance is located in the same region as an Elastic Compute Service (ECS) instance or an ApsaraDB for RDS 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 instance is located. Each zone is an independent area in 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: a recommended type of network. A Virtual Private Cloud (VPC) 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 over an internal network, 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 switch the network type of an ApsaraDB for Redis instance from Classic Network to VPC. However, you cannot switch it 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.
    Edition
    • Community Edition: This edition is compatible with the Redis protocol and provides database solutions that support hybrid storage in memory and disks.
    • Enterprise 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 Type Enterprise Edition includes the following series types:
    Note Community Edition does not support these series types.
    Version ApsaraDB for Redis supports the following engine versions:
    • Redis 2.8
    • Redis 4.0
    • Redis 5.0
    Note
    • Only engine versions supported by the specified edition or series type are displayed in the console.
    • The ApsaraDB for Redis instances with Redis 2.8 will be deprecated. We recommend that you create an instance with the latest engine version to enable 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.
    Node Type

    If Architecture Type is set to Standard or Cluster, Node Type can only be set to Master-Replica. A master-replica node runs in a hot standby mode and supports data persistence.

    If Architecture Type is set to Read/Write Splitting, 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 instance, database metadata is generated and consumes a small amount of storage space.
    • A standard instance has approximately 32 MB of metadata.
    • The metadata size on a cluster instance is approximately 32 MB multiplied by the number of shards.
  4. 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.
  5. Set Instance Name and Quantity. If you purchase a subscription instance, you must set Duration.
  6. Click Buy Now.
  7. On the Confirm Order page, confirm and select ApsaraDB for KVStore Agreement of Service.
  8. Click Activate.
    Note After you pay for the order, the system indicates that you have activated the instance. Then, wait up to five minutes to see the instance displayed in the console.

FAQ

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

    A: The time consumed by the system 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 for the system to allocate resources. For example, it takes 2-3 minutes to create a master-replica standard instance, 10-15 minutes to create a 128-shard master-replica cluster instance, and 20-40 minutes to create a 256-shard master-replica cluster instance.

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

    A: Standalone instances of ApsaraDB for Redis have been deprecated since December 19, 2019. For more information, see Deprecated standalone instances of ApsaraDB for Redis.

Related API operations

Operation Description
CreateInstance Creates an ApsaraDB for Redis instance.