Billing Method |
- Subscription: A subscription instance is an instance that you can subscribe to for a specified
period and pay for up front. For long-term use, the subscription billing method is
more cost-effective than the pay-as-you-go billing method. You can receive larger
discounts for longer subscription periods.
- Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage.
The pay-as-you-go billing method is suitable for short-term use. If you no longer
need your pay-as-you-go instance, you can release it to reduce costs.
Note A maximum of 30 pay-as-you-go RDS instances are allowed per Alibaba Cloud account.
To increase this quota, you must click here to submit a ticket.
|
Region |
The region to which the RDS instance belongs.
- After you confirm the purchase order, you cannot change the selected region.
- We recommend that you select a region that is in close proximity to the geographic
location where your users reside. This allows you to increase the access speeds of
your users.
- The RDS instance must reside in the same region as the ECS instance that you want
to connect. If the RDS and ECS instances reside in different regions, these instances
cannot communicate over an internal network. In this case, these instances must communicate
over the Internet and therefore cannot deliver optimal performance.
|
Database Engine |
The database engine and version that the RDS instance runs. Select MySQL. Supported MySQL versions are 5.6, 5.7, and 8.0.
Note The available database engines and versions vary based on the selected region.
|
Edition |
- Basic: The database system consists of only one primary RDS instance. Computing is separated
from storage to increase cost-effectiveness.
- High-availability: This is the recommended edition. In this edition, the database system consists of
one primary RDS instance and one secondary RDS instance. These instances work in the
high availability architecture.
- Enterprise: The database system consists of one primary RDS instance and two secondary RDS instances.
These instances can reside in the same zone or in different zones of the same region.
This edition delivers finance-grade reliability
- PolarDB MySQL: The database system is a PolarDB cluster that consists of multiple nodes. This edition
supports faster scaling, larger storage capacity, and lower data replication latency
between the primary and secondary nodes. For more information, see Overview.
|
Storage Type |
- Local SSD: A local SSD resides on the same server as the database engine. You can store data
on local SSDs to reduce I/O latency.
- Enhanced SSD: An enhanced SSD is an ultra-high performance disk that is developed by Alibaba Cloud
based on the next-generation distributed block storage architecture. It integrates
25 Gigabit Ethernet and remote direct memory access (RDMA) technologies. This type
of storage media reduces one-way latency and delivers up to 1 million random input/output
operations per second (IOPS). Three enhanced SSD options are provided in the ApsaraDB
RDS console. Each option represents a specific performance level (PL).
- Enhanced SSD: This option represents an enhanced SSD of PL1.
- ESSD PL2: An enhanced SSD of PL2 delivers IOPS and throughput that are twice higher
than those delivered by an enhanced SSD of PL1.
- ESSD PL3: An enhanced SSD of PL3 delivers IOPS that is 20 times higher than the IOPS
delivered by an enhanced SSD of PL1. It also delivers throughput that is 11 times
higher than the throughput delivered by an enhanced SSD of PL1. Enhanced SSDs of PL3
are suitable for workloads that require high I/O performance to process concurrent
requests. Enhanced SSDs of PL3 are also suitable for workloads that require stable
read/write latency.
- Standard SSD: A standard SSD is an elastic block storage device that is designed based on the
distributed storage architecture. You can store data on standard SSDs to separate
computing from storage.
For more information, see Storage types.
|
Zone |
A zone is an independent physical location within a region. The Zone of Primary Node parameter specifies the zone to which the primary RDS instance belongs. The Zone of Secondary Node parameter specifies the zone to which the secondary RDS instance belongs.
You can select the Single-zone Deployment or Multi-zone Development method.
- Single-zone Deployment: If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are the same.
- Multi-zone Development: This is the recommended deployment method. If you select this deployment method,
the Zone of Primary Node and the Zone of Secondary Node are different. This allows you to provide zone-level disaster recovery. You need
only to specify the Zone of Primary Node, ApsaraDB RDS automatically allocates the Zone of Secondary Node.
Note
- After the RDS instance is created, you can view information about the RDS instance
and its secondary RDS instance on the Service Availability page.
- If you select the RDS Basic Edition, the database system consists of only one primary
RDS instance and supports only the single-zone deployment method.
 |
Instance Type |
- General-purpose (Entry-level): belongs to the general-purpose instance family. A general-purpose instance exclusively
occupies the allocated memory and I/O resources. However, it shares CPU and storage
resources with the other general-purpose instances that are deployed on the same server.
- Dedicated Instance (Enterprise-level): belongs to the dedicated instance family or the dedicated host instance family.
A dedicated instance exclusively occupies the allocated CPU, memory, storage, and
I/O resources. The dedicated host instance family is the top configuration of the
dedicated instance family. A dedicated host instance exclusively occupies all the
CPU, memory, storage, and I/O resources on the server where it is deployed.
- Dedicated: A dedicated cluster exclusively occupies all the resources on a VM or physical host.
The permissions to manage hosts in a dedicated cluster can be authorized to you. This
allows you to create multiple database instances on a host. For more information,
see Create hosts in an ApsaraDB for MyBase dedicated cluster.
Note Each instance type supports a specific number of CPU cores, memory capacity, maximum
number of connections, and maximum IOPS. For more information, see Primary instance types.
|
Capacity |
The storage capacity that the RDS instance has available to store data files, system
files, binary log files, and transaction files. You can adjust the storage capacity
in increments of 5 GB.
Note
- If you select the local SSD storage type, the storage capacity of the RDS instance
may vary based on the instance type. If you select the standard or enhanced SSD storage
type, this limit does not apply. For more information, see Primary instance types.
- If you select the standard or enhanced SSD storage type, the Automatic Storage Expansion option is selected by default. This allows ApsaraDB RDS to automatically scale the
storage capacity when the storage capacity cannot meet your business requirements.
In this case, the RDS instance will not be locked due to an abnormally small storage
capacity.
|