| Basic configuration |
Region and Zone |
The region where you want to create your ApsaraDB for Redis instance. You cannot change
the region after you purchase 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 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 |
Select a zone within the specified region. 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 an internal network.
Note To implement 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 that provides higher security
and better performance than the classic network. We recommend that you select a VPC.
- Classic Network: Cloud services in the classic network are not isolated. Access control to cloud
services in the classic network is implemented by the security groups or whitelist
policies of the services.
Notice
- To enable connections over the internal network, make sure that the ApsaraDB for Redis
instance is connected to the same type of network as the ECS instances or ApsaraDB
RDS instances that need to access the ApsaraDB for Redis instance.
- If you select the VPC network type, 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.
- 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 VPCs, see Create a VPC.
|
| VSwitch |
Select a vSwitch in the VPC. If no vSwitches are created in the VPC in the current
zone, create a vSwitch as needed. For more information, see Create a vSwitch.
|
| Instance |
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.
|
| 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 for more features and more stable
performance.
|
| 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 |
Specifies the number of data shards for the cluster instance. Data is distributed
across the data shards in the cluster instance.
Note This parameter is supported only when you set the Architecture Type parameter to Cluster.
|
| Node Type |
- If you set the Architecture Type parameter to Cluster or Standard, you must set the Node Type parameter to Master-Replica. This creates a dual-node hot-standby architecture that provides data persistence
with high data reliability and availability.
- 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 |
Each instance type 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 cluster instances is 30 MB 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:
! @ # $ % ^ & * ( ) _ + - =.
|
| 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.
|
| Subscription Duration |
If you select the subscription billing method, you must specify the duration and select whether to enable auto-renewal.
|