Region |
Select 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.
Note 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
through the 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 with higher security and better
performance than the 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 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 |
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 selected zone, create a vSwitch first. For more information,
see Work with vSwitches.
|
Edition |
This parameter is set to Enhanced Edition (Tair) and cannot be modified.
ApsaraDB for Redis Enhanced Edition (Tair) is developed based on ApsaraDB for Redis
Community Edition. Compared with ApsaraDB for Redis Community Edition, ApsaraDB for
Redis Enhanced Edition (Tair) provides better performance, enhanced storage support,
and more data structures. For more information, see Overview.
|
Series |
This parameter is set to Enhanced Performance and cannot be modified. For more information, see Performance-enhanced instances.
|
Version |
This parameter is set to Redis 5.0 and cannot be modified.
|
Architecture Type |
- Standard: runs in a master-replica architecture, provides high-performance caching services,
and ensures high data reliability.
- 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.
- Read-Write Splitting: ensures high availability and high performance, and supports multiple specifications.
The read/write splitting architecture allows a large number of concurrent reads of
hot data from read replicas. This reduces the loads on the master node and minimizes
O&M costs.
For more information, see Overview.
|
Shards |
Select the number of shards for the ApsaraDB for Redis cluster instance.
Note This parameter is supported only when you set Architecture Type to Cluster.
|
Node Type |
This parameter is set to Master-Replica and cannot be modified. A master-replica instance provides a master node and a replica
node that are deployed in hot standby mode to support data persistence.
|
Instance Class |
Select the instance type. Each instance type has the specific memory size, maximum
number of connections, and bandwidth limit. For more information, see Performance-enhanced standard instances and Performance-enhanced cluster instances.
Note The database metadata is generated after an ApsaraDB for Redis instance is created.
The size of the metadata on each shard of a cluster instance is 30 to 50 MB. The total
size of the metadata for a cluster instance equals the sum of metadata on all shards
of the cluster instance.
|
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 |
Enter a name for the instance to identify and manage the instance. |
Quantity |
Select the number of instances to create with the same configurations. Set the value
to 1.
|
Duration |
If you select the Subscription (Local Disk, Including Tair) billing method, you must specify the duration and select whether to enable auto-renewal.
|
Resource Group |
Select the resource group in which the instance is created. |