--- title: "Cloud DB for MySQL quickstart" slug: "clouddbformysql-procedure" updated: 2026-10-08T07:06:40Z published: 2026-10-08T07:06:40Z canonical: "guide.ncloud-docs.com/clouddbformysql-procedure" --- > ## 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 quickstart Available in Classic and VPC Cloud DB for MySQL on NAVER Cloud Platform enables you to easily and quickly deploy MySQL Server in a cloud environment. It also helps you operate and manage the database service in a stable manner. Here's the entire process for NAVER Cloud Platform using Cloud DB for MySQL: ![clouddbforpostgresql-procedure_01_vpc_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/clouddbforpostgresql-procedure_01_vpc_en.png?sv=2026-02-06&spr=https&st=2026-10-27T15%3A59%3A17Z&se=2026-10-27T16%3A59%3A17Z&sr=c&sp=r&sig=mW8qSD2NkLC%2F2v9WlLoY%2FyQAflbmlg5PO3zG2eba8Ek%3D) Each step is described as follows: [1. Create application server](/docs/en/clouddbformysql-procedure#1%EC%95%A0%ED%94%8C%EB%A6%AC%EC%BC%80%EC%9D%B4%EC%85%98%EC%84%9C%EB%B2%84%EC%83%9D%EC%84%B1) [2. Set access environment](/docs/en/clouddbformysql-procedure#2%EC%A0%91%EC%86%8D%ED%99%98%EA%B2%BD%EC%84%A4%EC%A0%95) [3. Test application server connection](/docs/en/clouddbformysql-procedure#3%EC%95%A0%ED%94%8C%EB%A6%AC%EC%BC%80%EC%9D%B4%EC%85%98%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D%ED%85%8C%EC%8A%A4%ED%8A%B8) [4. Create MySQL Server](/docs/en/clouddbformysql-procedure#4MySQLServer%EC%83%9D%EC%84%B1) [5. Set ACG](/docs/en/clouddbformysql-procedure#5ACG%EC%84%A4%EC%A0%95) [6. Test MySQL Server connection](/docs/en/clouddbformysql-procedure#6MySQLServer%EC%A0%91%EC%86%8D%ED%85%8C%EC%8A%A4%ED%8A%B8) [7. Create database](/docs/en/clouddbformysql-procedure#7%EB%8D%B0%EC%9D%B4%ED%84%B0%EB%B2%A0%EC%9D%B4%EC%8A%A4%EC%83%9D%EC%84%B1) [8. Integrate external solutions](/docs/en/clouddbformysql-procedure#8%EC%99%B8%EB%B6%80%EC%86%94%EB%A3%A8%EC%85%98%EC%97%B0%EB%8F%99) ## 1. Create application server First, create the application server (App server). This server communicates with the MySQL Server that will be created later in Cloud DB for MySQL. To create an application server, navigate to **Menu** > **All Services** > **Compute** > **Server** in the NAVER Cloud Platform console. For detailed instructions, see: - [Create Server](/docs/en/server-create-vpc) ## 2. Set access environment After you complete the application server creation, configure the connection environment so you can access the application server. There are 2 ways to configure the connection environment: - Configure access by using port forwarding on the NAVER Cloud Platform (Classic environment) - Configure access to the private domain using a public IP on the NAVER Cloud Platform (VPC environment) When you configure access using a public IP, check the administrator (root) password required to access the server by using the **Administrator password check** feature. For detailed instructions, see: - [Guide to checking server information and managing servers](/docs/en/server-manage-vpc) Note SSL VPN makes connecting to MySQL Server more secure. Using SSL VPN is more secure when the server is used for administrative purposes. - [SSL VPN user guide (Classic)](/docs/en/sslvpn-start-classic) - [SSL VPN user guide (VPC)](/docs/en/sslvpn-start-vpc) ## 3. Test application server connection Once you complete setting up the access environment, use the terminal program to test if you can connect to the application server properly. For detailed instructions, see: - [Getting started with Cloud DB for MySQL](/docs/en/clouddbformysql-start) - [Download terminal program (PuTTY)](https://www.putty.org/) ## 4. Create MySQL Server After you complete testing the application server connection, create a MySQL Server that will communicate with the application server. A MySQL Server can be created without a separate service subscription by navigating to **Menu** > **All Services** > **Database** > **Cloud DB for MySQL** on the NAVER Cloud Platform console. For detailed instructions, see: - [Getting started with Cloud DB for MySQL](/docs/en/clouddbformysql-start) ### Server redundancy configuration You can configure server redundancy to prevent data loss and minimize service impact in the event of a failure. Cloud DB for MySQL creates both a Master Server and a Standby Master Server. If a failure occurs on the Master Server, it automatically fails over to the standby Master Server, minimizing service downtime. To configure server redundancy, select **Support high availability** when creating the MySQL Server. ### Monitoring and event management You can monitor the performance and operating system status of a running MySQL Server in the NAVER Cloud Platform console and check any events that occur. This allows you to manage the database service in a stable manner. You can also use Cloud Insight to configure events, notifications, and alarms. Caution Additional fees apply when you subscribe to Cloud Insight. For more information on Cloud Insight introduction and pricing, see [**Services > Management & Governance > Cloud Insight**](https://www.ncloud.com/product/management/cloudInsight) on the NAVER Cloud Platform portal. For detailed instructions, see: - [Monitoring](/docs/en/database-database-5-3) - [Event](/docs/en/database-database-5-5) ### Administrative and operational permissions management You can create sub accounts in addition to the main user account and set various management and administration permissions for Cloud DB for MySQL. You can design detailed permissions by using the System Managed policies and User Created policies of Sub Account. Note Sub Account is a free service with no additional charges. For detailed information about Sub Account and pricing plans, see [Services > Management & Governance > Sub Account](https://www.ncloud.com/product/management/subAccount) on the NAVER Cloud Platform portal. For detailed instructions, see: - [Sub Account permissions management](/docs/en/clouddbformysql-subaccount) ### Set read load balancing You can set the read load balancing of MySQL Server using the Load Balancer of the NAVER Cloud Platform. Caution Load Balancer is a service with additional charges. For more information about Load Balancer and pricing plans, see [Services > Storage > Load Balancer](https://www.ncloud.com/product/networking/loadBalancer) on the NAVER Cloud Platform portal. For detailed instructions, see: - [Set read load balancing](/docs/en/database-database-5-2#%EC%9D%BD%EA%B8%B0%EB%B6%80%ED%95%98%EB%B6%84%EC%82%B0%EC%84%A4%EC%A0%95) ## 5. Set ACG Set the Access Control Group (ACG) for a MySQL Server to allow the access of the application server to the created MySQL Server. For detailed instructions, see: - [ACG configuration guide](/docs/en/server-acg-vpc) ## 6. Test MySQL Server connection Use the MySQL client and test to see if you can properly connect to the created MySQL Server. For detailed instructions, see: - [Getting started with Cloud DB for MySQL](/docs/en/clouddbformysql-start) ## 7. Create database You can create a DB in 1 of the 3 ways below. To prevent misuse of privileges, users are not directly granted permission to create databases. Instead, when a database is created, the account with DDL privileges is granted all permissions on that database. For detailed instructions, see: - [Create a database via the console](/docs/en/database-database-5-2#database-%EA%B4%80%EB%A6%AC) - [Create a database using store procedure](/docs/en/database-database-5-2#database-%EA%B4%80%EB%A6%AC) - [Create a database using Cloud DB for MySQL API](https://api.ncloud-docs.com/docs/en/database-vmysql-addcloudmysqldatabaselist) ## 8. Integrate external solutions You can integrate external solutions such as zero board, GNU board, and so on. You can also use InnoDB as the storage engine during installation. If you require a different storage engine, consider using the MySQL installation-type service. For detailed instructions, see: - [MySQL installation-type service](/docs/en/database-database-1-1)