A dedicated cluster is the foundational resource in ApsaraDB for MyBase. Create one before you create hosts or database instances.
Before you begin
Before you begin, make sure that you have:
-
A virtual private cloud (VPC) in the target region. To create one, go to the VPC console.
-
(First-time only) Permission to authorize ApsaraDB for MyBase access to elastic network interfaces (ENIs) and security groups of Elastic Compute Service (ECS). You grant this permission during cluster creation.
Decisions you cannot change after creation
The following settings are locked after you create a cluster. Choose carefully before proceeding.
| Setting | Impact if misconfigured |
|---|---|
| Engine | Determines the OS image available when you add hosts and the database engine available when you create instances. MySQL and SQL Server are supported. |
| VPC | The cluster and all its hosts are bound to this VPC. Instances cannot communicate across VPCs without additional configuration. |
| Grant OS permissions | If enabled on a cluster running MySQL or SQL Server, you can log in to hosts to upload, download, or install software. This setting cannot be changed after cluster creation. |
In the Thailand (Bangkok) region, only the SQL Server engine is supported.
Default resource overcommit settings
After the cluster is created, the following overcommit metrics apply by default:
| Metric | Default value |
|---|---|
| CPU overcommit ratio (MySQL, SQL Server) | 200% |
| Storage overcommit ratio (MySQL, SQL Server) | 100% |
| Maximum memory usage (MySQL, SQL Server) | 100% |
To adjust these values, see Configure resource overcommitment to reduce costs.
Learn more
Join DingTalk group 32484333 to get technical support from database experts, view success stories, and watch expert live streams.
What's next
After the cluster is created, add hosts and then create database instances: