---
title: "Cloud DB for MySQL prerequisites"
slug: "clouddbformysql-spec"
updated: 2026-09-17T09:25:07Z
published: 2026-09-17T09:25:07Z
canonical: "guide.ncloud-docs.com/clouddbformysql-spec"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud DB for MySQL prerequisites

Available in Classic and VPC

 

Review supported environments, server specifications, 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, Japan |
| Platform | VPC, Classic |
| Languages | Korean, English, and Japanese |

              Note

              

For more information about the VPC environment, see [VPC overview](https://www.ncloud.com/product/networking/vpc) 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**](https://www.ncloud.com/product/database/cloudDbMysql) in 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 | - Rocky 8.10 - CentOS 7.8 (before October 17, 2024) |
| 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](https://www.mysql.com/about/legal/licensing/oem/) |

    

## 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](/docs/en/database-database-5-2#mysql-server-%EC%8A%A4%ED%8E%99-%EB%B3%80%EA%B2%BD). 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.

              Caution

              

Failover may take several minutes to complete.

## Pricing information

Cloud DB for MySQL uses a pay-as-you-go pricing plan. For detailed description of Cloud DB for MySQL's pricing standard, see **Portal > Services > Database > Cloud DB for MySQL**.

- [**Portal > Services > Database > Cloud DB for MySQL**](https://www.ncloud.com/product/database/cloudDbMysql)