Create an instance group
This document explains how to create a MySQL instance group.
Create MySQL instance group
A MySQL instance group is an object that manages the lifecycle of instances and backups.
Creating a MySQL instance group consists of four steps: Basic information, Instance configuration, Advanced settings, and Review.
- Go to the KakaoCloud Console > Data Store > MySQL.
- Click [Create instance group].
Step 1. Basic information
Configure availability, multi-availability zone usage, and the instance group name.
| Item | Category | Description |
|---|---|---|
| Instance availability | High availability (Primary and Standby instances) | Configures Primary and Standby instances together. You can select a single or multiple availability zones. |
| Single (Primary instance) | Configures a single Primary instance and supports only one availability zone. | |
| Multiple availability zones | Use | Creates up to six instances in subnets across different availability zones. Multiple availability zones are recommended for high availability. |
| Not use | Creates up to six instances in subnets within a single availability zone. | |
| Basic settings | Instance group name | Name of the instance group |
| Description (optional) | Additional description of the instance group |
If you select Single availability, the multiple availability zones option is disabled.
Step 2. Instance configuration
| Item | Category | Description |
|---|---|---|
| Engine | Engine version | The MySQL database version is selected automatically |
| Primary port | Port used to communicate with the MySQL Primary instance; range: 1024–65535; default: 3306 * Reserved ports (for example, 33060) are unavailable | |
| Standby port | Port used to communicate with MySQL Standby instances; range: 1024–65535; available when high availability is selected; default: 3307 * Reserved ports (for example, 33060) are unavailable | |
| MySQL username | MySQL database user account name - Example: admin * The reserved account name root is unavailable* For details about permissions, see Instance group user account | |
| MySQL password | Initial password for the MySQL database administrator account ⚠️ You can change the administrator password after the database starts ⚠️ You cannot retrieve an administrator password changed after the database starts | |
| Parameter group | Select only a parameter group compatible with the engine version | |
| Instance type | Instance type | Select an instance type - Use condition filters to refine your search |
| Storage capacity | Primary storage | SSD - Volume type: Only SSD is currently supported; more types will be supported later - Volume size: 100 GB–16,384 GB * The minimum capacity may vary by instance type |
| Log storage | SSD - Storage used for database logs; the type cannot be changed after creation - Volume type: Only SSD is currently supported; more types will be supported later - Volume size: 100 GB–16,384 GB * The minimum capacity may vary by instance type | |
| Network | VPC | Select a network |
| Subnet and instance count | Configure the subnets and number of Primary and Standby instances - For differences by availability configuration, see Network settings by availability configuration | |
| Security group | Create a new security group or select existing security groups; multiple selections are supported |
Network settings by availability configuration
The Subnet and instance count table is configured according to the availability and multiple availability zones settings selected in Step 1. For data redundancy, two instances including a Standby instance are recommended depending on the availability configuration of the Primary subnet. You can create only one subnet per availability zone. Whether you can add a subnet depends on the selected availability configuration, and you can add subnets separately after creating the instance group.
| Availability | Multiple availability zones | Number of instances | Add subnet |
|---|---|---|---|
| Single | Not applicable | 1 (fixed) | Not available |
| High availability | Not use | Default: 2; maximum: 6 | Not available |
| High availability | Use | Default: 2; maximum: 6 | Available |
A Primary badge is displayed on the subnet where the Primary instance is created, and a Primary endpoint is created based on the availability zone containing that subnet. A Standby badge is displayed on a subnet that contains only Standby instances, and a Standby endpoint is created based on the availability zone containing that subnet.
Step 3. Advanced settings
Configure operating options such as automated backups, additional settings, and Audit logging.
| Item | Category | Description |
|---|---|---|
| Automated backup | Use | Default: Use- When automated backup is enabled, the first backup starts within 30 minutes. Subsequent backups run according to the automated backup start time. |
| Automated backup retention period | Default: 7 days; automated backup files can be retained for up to 35 days | |
| Automated backup start time | Default: 01:00; the backup starts within 15 minutes of the selected time | |
| Additional settings | Table name case sensitivity | Sets the lower_case_table_names parameter separately from the parameter group value- Default: Use- ⚠️ This setting cannot be changed after instance group creation |
| Audit logging | Use | Default: Not use- Logging starts or stops after the setting is applied, and generated logs can be downloaded from the log export menu - When set to Use, you can configure server_audit_events, server_audit_excl_users, and server_audit_query_log_limit- For details, see Configure Audit logging |
| Recommended alert policy | Use | Configure metric and event alert policies and notification channels for the instance group |
Recommended alert policy
When you use Recommended alert policy, metric and event alert policies for the instance group are automatically created and configured after the group is created. You can view and modify the policies in Alert Center.
- Metric alert policy name:
mysql-metric-{instance group ID} - Event alert policy name:
mysql-event-{instance group ID}
Metric conditions (defaults)
You can enable or disable each metric and configure its conditions.
| Metric | Threshold | Duration | Severity |
|---|---|---|---|
Log storage usage (mysql_logstorage_disk_used_percent) | 95% or higher | 3 minutes | Warning |
Primary storage usage (mysql_defaultstorage_disk_used_percent) | 85% or higher | 3 minutes | Warning |
CPU usage (cpu_usage) | 80% or higher | 3 minutes | Warning |
Memory usage (mem_usage) | 95% or higher | 3 minutes | Warning |
Event conditions
You can enable or disable each event.
| Event name | Description |
|---|---|
| Instance Group Error | Occurs when an error in one or more instances makes the instance group temporarily unavailable |
| Instance Error | Occurs when an instance error makes the instance temporarily unavailable |
| Backup Error | Occurs when a manual backup ends abnormally |
| Scheduled Backup Error | Occurs when an automated backup ends abnormally |
| Instance Storage Warning | Occurs when an instance has 30 GB or less available storage |
| Instance Storage Error | Occurs when an instance has 5 GB or less available storage |
| Instance Group Start Failover | Occurs when instance group Failover starts |
| Instance Group End Failover | Occurs when instance group Failover completes |
| Maintenance Error | Occurs when a maintenance task encounters an error |
Notification channels
Specify the channels that receive notifications from the configured alert policies.
- Select a Channel type and Notification channel. At least one notification channel is required.
- Supported channel types are email, SMS, AlimTalk, Slack, webhook, and Pub/Sub. Use Add channel to configure up to 10 notification channels.
The channel must be active to receive notifications.
Review
Review the basic information, instance configuration, and advanced settings selected in the preceding steps. Click [Create] to start creating the instance group.
- If instance group creation fails due to an unexpected cause such as a network error or insufficient resources, check the event history in Cloud Trail.