Key Concepts
The key concepts of the MySQL service are as follows:
| Key Concept | Description |
|---|---|
| Instance group | An object that manages the lifecycle of instances and backups |
| Instance | A VM managed by an instance group, assigned as Primary or Standby based on availability |
| Instance Type | Virtualized hardware resources including vCPU and memory for database use - Supports various types optimized for different workloads |
| Instance group/Instance lifecycle | Operational and task states are managed based on the lifecycle of instance groups/instances |
| Backup | Performed online without database downtime, includes management such as backup creation and deletion |
| Volume | Uses block storage devices to provide the database for MySQL service - No need for users to manually create or configure block storage |
| Network and security | Provides network and security features through VPC, enabling logically separated service environments based on network requirements - All MySQL instances are provided in a VPC environment |
| IAM and security | Grants appropriate access rights based on user roles through IAM and securely manages MySQL resources |
| Parameter group | Manages MySQL configuration parameters by version and group unit |
Instance group
Instance Group is an object that manages the lifecycle of instances and backups.
A MySQL instance group has various status values, including operational and terminated states, which users can check to manage the group.
Instance Group Lifecycle and Status Values
When you create a MySQL instance group, it starts in the Pending state, then transitions through Provisioning and Primary Available before becoming Available. In the Available state, the group can be accessed through the endpoint and port of the selected network. Default ports are 3306 (Primary) and 3307 (Standby), with configurable ports ranging from 1024 to 65535.
MySQL instance group lifecycle
MySQL Instance Group Lifecycle
| Status | Description |
|---|---|
| Pending | Preparing to configure a MySQL instance group - Starts in Pending when first created |
| Provisioning | Creating instances for the MySQL instance group |
| Primary Available | Allocating and configuring virtual resources for Standby instances, group is partially operational * Standby availability is also indicated * HA configuration is maintained with Primary instance available |
| Switching | Manual or automatic failover in progress |
| Available | All instances are in Running state and usable - Accessible via selected network’s endpoint and port - Default ports: 3306 (Primary), 3307 (Standby) |
| Restarting | Restarting (single availability only) |
| Scaling-Out | Adding Standby instances |
| Scaling-In | Removing Standby instances |
| Error | Temporary unavailability due to instance errors |
| Terminating | Terminating all instances and deleting associated backups |
| Terminated | All instances and backups deleted, group is unavailable |
Instance group availability status
When the group is in Primary Available state, the availability of Standby instances is also displayed.
| Instance Group State | Availability State | Description |
|---|---|---|
PRIMARY-AVAILABLE | READY | All Standby HA configurations are ready |
PARTIAL-READY | HA configuration in progress, at least one Standby ready | |
PARTIAL-UNAVAILABLE | At least one Standby configured and one unavailable | |
CONFIGURED | All Standby configurations complete | |
STANDALONE | No usable Standby, at least one unavailable | |
UNAVAILABLE | All Standbys are unavailable | |
AVAILABLE | READY | All Standby configurations complete |
- | No Standbys present |
Instance
An Instance is a VM managed by the instance group.
MySQL instances are virtualized databases with vCPU and memory, and are objects within the instance group. Each instance has a status and a role (Primary or Standby).
Instance roles
| Role | Description |
|---|---|
| Primary | Default instance for read/write operations - Accessible via DNS |
| Standby | HA-purpose instance used in failover scenarios - Can also act as Read Replica - Created when HA is enabled or added later |
Instance types
The service offers optimized instance types based on purpose and expected workload.
Specifications are determined by the instance type selected during creation. Pricing is based on usage. More high-performance types will be added later.
| MySQL Instance Type | vCPU | Memory (GiB) |
|---|---|---|
| m2a.large | 2 | 8 |
| m2a.xlarge | 4 | 16 |
| m2a.2xlarge | 8 | 32 |
| m2a.4xlarge | 16 | 64 |
| m2a.8xlarge | 32 | 128 |
| m2a.12xlarge | 48 | 192 |
| m2a.16xlarge | 64 | 256 |
| m2a.24xlarge | 96 | 384 |
| r2a.large | 2 | 16 |
| r2a.xlarge | 4 | 32 |
| r2a.2xlarge | 8 | 64 |
| r2a.4xlarge | 16 | 128 |
| r2a.8xlarge | 32 | 256 |
| r2a.12xlarge | 48 | 384 |
| r2a.16xlarge | 64 | 512 |
| r2a.24xlarge | 96 | 768 |
Instance lifecycle and status values
An instance starts in the Pending state and transitions through Provisioning and Starting to become Running.
MySQL Instance Lifecycle
| Status | Description |
|---|---|
Pending | Preparing instance configuration |
Starting | Setting up database and configurations |
Running | Instance is operational |
Volume-Extending | Expanding volume size |
Error | Instance temporarily unavailable due to error |
Terminating | Shutting down and releasing the instance |
Terminated | Instance is no longer available |
Instance availability config & roles
Availability configuration determines the number and roles of instances.
| Availability Type | Instance Count | Description |
|---|---|---|
| Single | 1 | Only one Primary instance is created |
| High Availability (HA) | Up to 6 | One Primary and 1–5 Standby instances |
Instance availability status
Refers to the replication status between MySQL instances (applies only to HA configurations).
MySQL Instance Availability
| Availability Status | Description |
|---|---|
CONFIGURED | Replication is functioning normally |
CONFIGURING | Replication setup in progress |
UNAVAILABLE | Replication has stopped |
Backup
Backups are managed at the instance group level.
Backup lifecycle and status values
Backups start in Pending, go through Processing, and complete in Succeeded.
Backup states (Before March 19, 2024)
MySQL Backup Lifecycle (Pre-March 19, 2024)
| Status | Description |
|---|---|
Pending | Initial state |
Processing | Backup in progress |
In-Use-Checking | Verifying if the backup is being used for restore |
Deletion-Pending | Deletion waiting until restore finishes |
Deleted | Backup fully removed |
Succeeded | Backup completed successfully |
Deleting | Backup being deleted |
Fatal | Internal logic |
Error | Backup failed - Cannot be restored, but can be deleted |
Backup status (Created After March 19, 2024)
MySQL Backup Lifecycle (Post March 19, 2024)
| Status | Description |
|---|---|
Pending | Initial backup status |
Processing | Backup is in progress - Even if deleted in this state, the deletion is executed after it either completes successfully ( Succeeded) or fails (Error) |
Restoring | In use for restoration, cannot be deleted |
Deleted | Backup has been completely deleted |
Succeeded | Backup completed successfully |
Deleting | Deletion in progress - If used for restoration, deletion is suspended and status changes to Restoring |
Error | Backup failed - Cannot be restored, but can be deleted |
Failover
MySQL supports High Availability (HA) features. By selecting the high availability option for backup instance types, multiple standby instances can be created. In the event of a failure, failover is performed to minimize service disruption. Both automatic and manual failover are supported.
Service interruption may occur during failover.
Failover lifecycle
Instance group status during failover
| Status | Description |
|---|---|
SWITCHING | Failover is in progress. MySQL service is temporarily unavailable. |
PRIMARY-AVAILABLE | Standby instances are being configured. |
Volume
MySQL uses block storage devices as volumes to provide database services. Users do not need to manually create or manage block storage.
Network and security
All MySQL instances operate within a VPC environment. VPC provides networking and security features, allowing you to build logically isolated service environments according to your network requirements. For more information, refer to the VPC documentation.
Parameter group
MySQL allows configuration parameters to be managed in groups.
Parameter application status
Parameter Group Application Status
| Status | Description |
|---|---|
Pending | Waiting to apply the parameter group. |
Applying | Parameters are currently being applied to the instance group. |
In-Sync | Parameters have been successfully applied to all instances in the group. |
Partial-Sync | Parameters have only been applied to some instances. This may occur if the group is in Failover, Provisioning, or not in Available state. Once successful, status changes to In-Sync. If failed, status becomes Error-Sync. |
Error-Sync | Failed to apply parameters to the cluster. You can Retry, which will change the status back to Applying. |
Suspended | Application is paused because a previous group in the sequence failed. You can Retry, which will change the status back to Applying. |