Available in Classic and VPC
Review supported environments, service limits, and pricing information before using Cloud DB for MySQL.
Cloud specifications
Cloud DB for MySQL supports the following cloud environment specifications:
| Item | Specification |
|---|---|
| Region | Korea, Western U.S., Singapore, and Japan |
| Platform | VPC, Classic |
| Language | Korean, English, and Japanese |
For more information about the VPC environment, see VPC overview on the NAVER Cloud Platform portal.
Server specifications
For NAVER Cloud Platform's Cloud DB for MySQL, you can flexibly select from various types of server type and use them according to your service size. For server specifications supported by Cloud DB for MySQL, see Services > Database > Cloud DB for MySQL on the portal.
Specification details
The server operating system, operating system disk size, storage engine, and licensing information are as follows:
| Item | Platform | Description |
|---|---|---|
| Server operating system | VPC |
|
| Classic | CentOS 7.8 | |
| Operating system disk size | VPC, Classic | 50 GB (not changeable) |
| Storage engine | VPC, Classic | InnoDB, Memory |
| License | VPC, Classic | General Public License |
Service limits when changing server specifications
The type of an operational MySQL Server that has been created and is in operation cannot be changed, but the available memory size can be changed at any time using the Change specifications feature in the console DB Server menu. When creating a server with G3 in the Korea Region, you can change the server type.
For information on how to change the available memory size, see DB Server. However, a few service limits exist when changing the server specifications. Make sure you are aware of the following service limits before making any changes to the server specifications:
- They can only be changed within the same type.
- If configured with more than 2 servers (using high availability and using Read Replica), change all to the same specification.
- The server restarts upon completion of the change. Therefore, the service may possibly be affected.
Server redundancy configuration
Cloud DB for MySQL supports the high availability (HA) feature. Automatic Failover to the Standby Master Server if the operating Master Server fails and normal service is not possible. When creating MySQL Server in the NAVER Cloud Platform console, you can choose whether to use high availability (HA) or not, and the server configuration depends on whether to use it.
It may take several minutes to tens of minutes for completing Failover.
Pricing information
Cloud DB for MySQL uses a pay-as-you-go pricing plan. For detailed description of Cloud DB for MySQL's pricing information, see Portal > Services > Database > Cloud DB for MySQL.