- Print
- PDF
Prerequisites for using Cloud DB for MySQL
- Print
- PDF
Available in Classic and VPC
View supported environments, server specifications, and restrictions, etc., for smooth use of Cloud DB for MySQL.
Cloud environment specifications
The following details are the cloud environment specifications supported by Cloud DB for MySQL.
Item | Supported specifications |
---|---|
Region | Korea, US West, Singapore, Japan, and Germany |
Classic | Supported |
VPC | Supported |
Language | Korean, Japanese, English, and Chinese (Simplified) |
Server specifications
For NAVER Cloud Platform's Cloud DB for MySQL, you can flexibly select from various server types and use them according to your service size. For server specifications supported by Cloud DB for MySQL, refer to Service > Database > Cloud DB for MySQL in the portal.
Detailed specifications information
The information about server operating system, operating system disk size, storage engine, and license is as follows.
Item | Description |
---|---|
Server operating system | Linux CentOS 7.8 |
Operating system disk size | 50 GB (can't be changed) |
Storage engine | InnoDB, Memory |
License | General Public License |
Restrictions when changing server specifications
While the type of MySQL Server that has been created and is in operation can't be changed, the size of available memory can always be changed using the Change specifications feature of the DB Server menu in the console. For the upgrade method, please refer to DB Server. However, a few restrictions exist when changing the server specifications. You need to fully understand these restrictions before changing the server specifications. The restrictions are as follows.
- They can only be changed within the same type.
- If configured with 2 or more servers (use of high availability and read replica), then they will all be changed to the same specifications.
- 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. If the master server can no longer provide normal service due to a failure, then it automatically fails over to the standby master server. When creating the MySQL Server from the NAVER Cloud Platform console, you can select whether to use high availability (HA). The server configuration will then change according to the use status.
The completion of the failover may take several minutes or longer.
Usage fees
Cloud DB for MySQL is serviced on a pay-as-you-go pricing plan. For details about Cloud DB for MySQL's pricing standards, refer to the Portal > Service > Database > Cloud DB for MySQL menu or the Portal > Pricing menu.