This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

MariaDB(DBaaS)

1: Overview

1.1: Server type
1.2: Monitoring metrics
1.3: ServiceWatch metric

2: How-to guides

2.1: Managing DB Services
2.2: Backing up and restoring the DB
2.3: Configure Read Replica
2.4: MariaDB(DBaaS) server connection

3: API Reference

4: CLI Reference

5: Release Note

1 - Overview

Service Overview

MariaDB(DBaaS) is an open-source relational database(RDBMS) with high compatibility with MySQL. Samsung Cloud Platform provides an environment that can automate MariaDB installation and perform management functions for operation through a web-based console.

MariaDB(DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and the read‑only server called Replica, used for read load balancing and disaster recovery (DR), is provided up to five instances. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling data recovery at the desired point in time.

Provided features

MariaDB (DBaaS) provides the following features.

Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and provides an Active-standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, a switch-over allows the user to directly perform the Active-Standby node transition.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup time window and storage provider can be configured by the user, and additional charges may be incurred based on the backup size. * It also provides a recovery function for backed‑up data, so when a user initiates a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup creation time or a user‑specified time). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
Version Management: Provides Major and Minor version upgrade features based on certain functionality improvements and security patches.
Replica configuration: For load balancing reads and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
Audit setting: Provides an Audit setting feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
Parameter management: It is possible to modify DB configuration parameters related to performance improvement and security.
Service Status Lookup: Retrieve the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
Archive Management: Within the DB server, you can set the Archive file retention period (1 day~35 days) and configure the Archive mode (On/Off).
Export DB Log: You can export stored logs to the user’s Object Storage via Audit settings.
Migration: Synchronizes data in real time with the operational database and supports migration using replication without service interruption.
OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.

Components

MariaDB (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it based on the scale of the service they wish to configure.

Engine version

The engine versions supported by MariaDB (DBaaS) are as follows.

Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.

Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.

MariaDB (Community): https://mariadb.org/about/#maintenance-policy

service	Provided version	EOS Date (Samsung Cloud Platform new creation stop date)	EoTS Date(Community Technical Support End Date)
MariaDB (Community)	10.6.5	2026-03-19	2026-07-06
	10.6.9	2026-03-19	2026-07-06
	10.6.10	2026-03-19	2026-07-06
	10.6.12	2026-03-19	2026-07-06
	10.6.14	2026-03-19	2026-07-06
	10.6.15	2026-03-19	2026-07-06
	10.6.16	2026-03-19	2026-07-06
	10.6.17	2026-03-19	2026-07-06
	10.6.19	2026-03-19	2026-07-06
	10.6.22	2026-03-19	2026-07-06
	10.11.8	2027-09 (scheduled)	2028-02-16
	10.11.9	2027-09 (scheduled)	2028-02-16
	10.11.13	2027-09 (scheduled)	2028-02-16
	10.11.15	2027-09 (scheduled)	2028-02-16
	11.4.7	2028-12 (scheduled)	2029-05-29
	11.4.10	2028-12 (scheduled)	2029-05-29

Table. Engine versions provided for MariaDB (DBaaS)

notice

The next version of MariaDB is scheduled to be available after September 2026. The actual service delivery schedule is subject to change.

MariaDB 10.11.16

Server type

The server types supported by MariaDB (DBaaS) are as follows.

For detailed information about the server types provided by MariaDB (DBaaS), see MariaDB(DBaaS) 서버 타입.

Standard db1v2m4

Category	Example	Detailed description
Server type	Standard	Provided server types Standard: Standard configuration commonly used (vCPU, Memory) High Capacity: Large server specifications of 24 vCores or more
Server specifications	db1	Provided server specifications db1: Standard specifications (vCPU, Memory) commonly used dbh2: Large-scale server specifications Provides servers with 24 vCores or more
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. MariaDB (DBaaS) server type components

Preceding Service

This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.

Service Category	service	Detailed description
Networking	VPC	A service that provides an isolated virtual network in a cloud environment

Table. MariaDB (DBaaS) pre-service

1.1 - Server type

MariaDB(DBaaS) server type

MariaDB (DBaaS) provides server types composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating a MariaDB(DBaaS), the Database Engine is installed according to the server type selected for the intended use.

Reference

The server types provided may differ depending on the region and AZ.

The server types supported by MariaDB (DBaaS) are as follows.

Standard db1v2m4

Category	example	Detailed description
Server type	Standard	Provided server type categories Standard: Configured with the commonly used standard specifications (vCPU, Memory) High Capacity: Large-capacity server specifications exceeding Standard
Server specifications	db1	Provided server type classification and generation db1: means a standard specification, and 1 indicates the generation dbh2: h indicates a large-capacity server specification, and 2 indicates the generation
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. MariaDB (DBaaS) server type format

db1 server type

The db1 server type of MariaDB (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
Standard	db1v1m2	1 vCore	2 GB	Up to 10 Gbps
Standard	db1v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	db1v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	db1v2m16	2 vCore	16 GB	Up to 10 Gbps
Standard	db1v2m24	2 vCore	24 GB	Maximum 10 Gbps
Standard	db1v2m32	2 vCore	32 GB	Up to 10 Gbps
Standard	db1v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	db1v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	db1v4m32	4 vCore	32 GB	Up to 10 Gbps
Standard	db1v4m48	4 vCore	48 GB	Up to 10 Gbps
Standard	db1v4m64	4 vCore	64 GB	Up to 10 Gbps
Standard	db1v6m12	6 vCore	12 GB	Up to 10 Gbps
Standard	db1v6m24	6 vCore	24 GB	Up to 10 Gbps
Standard	db1v6m48	6 vCore	48 GB	Up to 10 Gbps
Standard	db1v6m72	6 vCore	72 GB	Up to 10 Gbps
Standard	db1v6m96	6 vCore	96 GB	Up to 10 Gbps
Standard	db1v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	db1v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	db1v8m64	8 vCore	64 GB	Up to 10 Gbps
Standard	db1v8m96	8 vCore	96 GB	Up to 10 Gbps
Standard	db1v8m128	8 vCore	128 GB	Up to 10 Gbps
Standard	db1v10m20	10 vCore	20 GB	Up to 10 Gbps
Standard	db1v10m40	10 vCore	40 GB	Up to 10 Gbps
Standard	db1v10m80	10 vCore	80 GB	Maximum 10 Gbps
Standard	db1v10m120	10 vCore	120 GB	Maximum 10 Gbps
Standard	db1v10m160	10 vCore	160 GB	Up to 10 Gbps
Standard	db1v12m24	12 vCore	24 GB	Up to 12.5 Gbps
Standard	db1v12m48	12 vCore	48 GB	Up to 12.5 Gbps
Standard	db1v12m96	12 vCore	96 GB	Up to 12.5 Gbps
Standard	db1v12m144	12 vCore	144 GB	Up to 12.5 Gbps
Standard	db1v12m192	12 vCore	192 GB	Up to 12.5 Gbps
Standard	db1v14m28	14 vCore	28 GB	Up to 12.5 Gbps
Standard	db1v14m56	14 vCore	56 GB	Up to 12.5 Gbps
Standard	db1v14m112	14 vCore	112 GB	Up to 12.5 Gbps
Standard	db1v14m168	14 vCore	168 GB	Up to 12.5 Gbps
Standard	db1v14m224	14 vCore	224 GB	Up to 12.5 Gbps
Standard	db1v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	db1v16m64	16 vCore	64 GB	Up to 12.5 Gbps
Standard	db1v16m128	16 vCore	128 GB	Up to 12.5 Gbps
Standard	db1v16m192	16 vCore	192 GB	Up to 12.5 Gbps
Standard	db1v16m256	16 vCore	256 GB	Up to 12.5 Gbps

Table. MariaDB(DBaaS) server type specifications - db1 server type

Database passwordRequiredPassword to use when accessing the DB

Include English letters, numbers, and special characters (“ ‘ excluded) and enter 8~30 characters

Check database passwordRequiredRe-enter the same password to use for DB accessDatabase Port numberRequiredPort number required for DB connection

Enter the DB port within the range 1200 ~ 65535

Backup > UseSelectionBackup usage

Select Use to set backup file retention period, backup start time, and Archive backup interval

Backup > Retention PeriodSelectionBackup retention period

Select the backup retention period. Set the file retention period from 7 days to 35 days

Backup files incur additional charges based on size

Backup > Backup Start PeriodSelectionBackup start time

Select backup start time

The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be configured

Backup > Archive backup scheduleSelectionArchive backup interval

Select the archive backup interval

The archive backup interval is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance

Audit Log configurationSelectionWhether to store Audit Log

Select Use to enable the Audit Log feature
- User connection information records are stored
  - Users can specify the types of events to audit via the server_audit_events parameter, and it can be modified through the Parameter screen
  - For details on this parameter, refer to the MariaDB documentation
- Enabling Audit may degrade DB performance
ServiceWatch log collectionSelectionServiceWatch log collection status
- Select Use to configure the ServiceWatch log collection feature
- Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB
- Log groups and log streams are automatically created upon collection and cannot be deleted until the resource itself is deleted
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
ParameterRequiredParameters to be used in the DB
- View button can be clicked to view detailed information of the parameters
- Parameters can be modified after the DB creation is complete, and the DB must be restarted after any modifications
DB character setRequiredCharacter encoding method to be used for the DB
- The character set used when storing text data, which is set as the default with the selected encoding when the DB is created
Time zoneRequiredStandard time zone used by the database

Table. MariaDB(DBaaS) Database configuration items

Category	Detailed description
Cluster status	Cluster status with DB installed Creating: Cluster creation in progress Editing: Cluster is transitioning to an operational state Error: Cluster encountered a failure while performing a task If this persists, contact the administrator Failed: Cluster failed during creation Restarting: Restarting the cluster Running: Cluster is operating normally Starting: Starting the cluster Stopped: Cluster is stopped Stopping: Cluster is being stopped Synchronizing: Synchronizing the cluster Terminating: Deleting the cluster Unknown: Cluster status is unknown If this persists, contact the administrator Upgrading: Cluster is transitioning to an upgrading state
Cluster control	Buttons to change the cluster state Start: Start a stopped cluster Stop: Stop a running cluster Restart: Restart a running cluster Switch-Over: Switch a standby cluster to Active
View more features	Cluster management buttons Service status synchronization: Real-time DB service status lookup Backup history: Verify successful backup execution and view history when backup is configured Database recovery: Recover the DB based on a specific point in time Parameter management: View and modify DB configuration parameters Replica configuration: Configure a read-only cluster as a Replica Replica configuration (Other-Region): Configure a disaster recovery Replica in another region; the button is disabled if the account has no region to configure DB user management: View and manage DB account (user) information registered in the DB DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB Archive settings management: Set archive file retention period and configure archive mode DB Log export: Export stored logs to the user’s Object Storage via Audit settings Migration configuration: Provides Migration functionality using a Replication method Block Storage usage management: Provides usage query functionality per Block Storage type OS (Kernel) upgrade: Upgrade OS Kernel version
Service cancellation	Cancel Service button

Category	Detailed description
Server Information	Server information configured in this cluster Category: Server type (Active, Standby, Replica) Server name: Server name IP Port: Server IP and port Availability Zone: Server creation location Status: Server status
service	Service name
Resource Type	Resource Type
SRN	Unique resource ID in Samsung Cloud Platform In the DB service, it means the cluster SRN
Resource name	Resource name In the DB service, it refers to the cluster name
Resource ID	Unique resource ID in the service
Constructor	User who created the service
Creation Date/Time	Service creation date and time
Modifier	User who edited the service information
Modification date and time	Date and time the service information was modified
Image version	Installed DB image and version information If a version upgrade is required, click the Edit icon to configure For details, refer to Minor 버전 업그레이드하기 and Major 버전 업그레이드하기
Cluster type	Cluster type (Master Cluster, Replica Cluster, Migration Cluster)
Cluster name	Cluster name of the configured DB servers
Master cluster name	Replica’s Master cluster name If it is the Replica’s detailed information, it can be verified
Database name	Server name applied during DB installation
Database username	DB user name
Planned Compute	Resource status with Planned Compute configured For more information, refer to Planned Compute 신청하기
Maintenance period	DB Maintenance Period Status If you need to set the maintenance period, click the Edit icon to configure
Backup	Backup configuration status If backup configuration is required, click the Edit icon to set it If an immediate backup is required, click the Immediate Backup button to set it For detailed information about backups, refer to MariaDB(DBaaS) 백업하기
Audit Log configuration	Audit Log configuration status If Audit Log configuration is required, click the Edit icon to configure For details, see Audit 설정 수정하기
ServiceWatch log collection	ServiceWatch Log Collection Configuration Status If log collection configuration is required, click the Edit icon next to Log Collection to configure
DB character set	Character encoding to use for the DB
Time zone	Standard time zone used by the database
VIP	Virtual IP information can be checked only when high availability is enabled
Network	Network information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP))
IP access control	Service access policy configuration If you need to add or remove an IP, click the Edit icon to configure
Active & Standby	Active/Standby server type, default OS, additional Disk information If you need to modify the server type, click the Edit icon next to the server type to configure it. See the server type modification procedure at 서버 타입 변경하기 Modifying the server type requires a server reboot If you need to expand storage, click the Edit icon next to the storage capacity to expand it. See the storage expansion procedure at 스토리지 증설하기 If you need to add storage, click the Add Disk button next to the additional Disk to add it. See the storage addition procedure at 스토리지 추가하기

Item	Detailed description	Whether to restart
`character-set-server`	Specify default character set	Restart required
`collation-server`	Specify default collation (Collation)	Restart required
`init_connect`	SQL statement executed when the client connects to the database	No restart required

Category	Required	Detailed description
Log type	Required	Log type to be saved
Save bucket name	Required	Object Storage bucket name to be saved
Authentication key > Access key	Required	Access key for accessing the Object Storage you want to store
Authentication key > Secret key	Required	Secret key for accessing the Object Storage you want to store
File creation cycle	Required	File creation frequency in Object Storage
Whether to delete the original log	Selection	Whether to delete the original logs when exporting to Object Storage

Category	Required	Detailed description
Source DB Database name	Required	Database name of the source DB to be migrated
Source DB IP	Required	IP of the Source DB that is the migration target
Source DB Port	Required	Port of the Source DB to be migrated
Source DB username	Required	User name of the Source DB to be migrated
Source DB password	Required	Password of the source DB for migration

Category	Required	Detailed description
Recovery type	Required	Set the point in time the user wants to recover Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list Custom point: Recover to a user‑desired point within the recoverable backup time range. The recoverable period depends on the Archive backup interval setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix	Required	Recovery DB server name Start with a lowercase English letter and use lowercase letters, numbers, and special characters (`-`) to enter 3 to 16 characters Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name	Required	Cluster name of the recovery DB Enter using English letters, 3 ~ 20 characters A cluster is a unit that groups multiple servers
Service Type > Server Type	Required	Server type for the recovery DB installation Standard: Standard specifications commonly used High Capacity: Large-capacity server of 24vCore or more (to be provided later)
Service Type > Planned Compute	Selection	Status of resources with Planned Compute set In Use: Number of resources with Planned Compute that are currently in use Configured: Number of resources with Planned Compute set Coverage Preview: Amount applied per resource by Planned Compute Create Planned Compute Service: Go to the Planned Compute service application page For more details, refer to Planned Compute 신청하기
Service Type > Block Storage	Required	Block Storage settings used by the recovery DB Basic OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. Apply the same storage type as set in the original cluster Enter capacity as a multiple of 8 within the range 16 to 5,120 Add: Storage area for DATA, Archive, TEMP, Backup data Apply the same storage type as set in the original cluster In the recovery DB, only DATA, TEMP, and Archive purposes can be added After selecting Use, enter the storage purpose and capacity To add storage, click the Add button; to delete, click the x button Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username	Required	Database username set in the source DB
Database Port number	Required	Database Port number set in the source DB
IP access control	Selection	IP address for accessing the recovery DB Enter in IP format (example: `192.168.10.1`) or CIDR format (example: `192.168.10.1/32`, `192.168.10.1/32`), then click the Add button To delete an entered IP, click the x button next to the entered IP
maintenance period	Selection	DB maintenance window If you select Use, you can set the day, start time, and duration The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and patch tasks within that time are the user’s responsibility. We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or failing to perform tasks within the window.
tag	Selection	Add Tag Add Tag after clicking the button, enter or select Key, Value values

Category	required status	Detailed description
Region	Required	Region to configure the Replica Replica configuration (Other Region) is displayed only when selected
Replica count	Required	Number of Replicas to configure Up to 5 can be configured per cluster If you select more than one value, additionally enter the Replica name and service type information
Replica name	Required	Replica server name must start with a lowercase English letter, and use lowercase letters, numbers, and special characters (`-`) to enter 3 to 19 characters The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type	Essential	Replica server type Standard: standard specification commonly used High Capacity: large-capacity server with 24vCore or more (to be provided later)
Service Type > Planned Compute	Select	Status of resources with Planned Compute configured In Use: Number of resources with Planned Compute configured that are currently in use Configured: Number of resources with Planned Compute configured Coverage Preview: Amount applied per resource by Planned Compute Create Planned Compute Service: Navigate to the Planned Compute service application page For more details, see Planned Compute 신청하기
Service Type > Block Storage	Required	Block Storage configuration using Replica DB Basic OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. Applied identically with the storage type set in the source cluster Capacity cannot be set Additional: DATA, Archive, TEMP, Backup data storage area Applied identically with the storage type set in the source cluster In a Replica, only DATA and TEMP can be added After selecting Use, input the storage purpose and capacity To add storage, click the Add button, and to delete, click the x button Capacity can be entered in multiples of 8 within the range 16–5,120, and up to a maximum of 9 can be created, including the number set in the source cluster
IP access control	Selection	Service Access Policy Configuration Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required Enter in IP format (example: `192.168.10.1`) or CIDR format (example: `192.168.10.0/24`, `192.168.10.1/32`) and click the Add button To delete an entered IP, click the x button next to the entered IP
maintenance period	Select	Database maintenance window If you select Use, set the day of week, start time, and duration It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions If set to unused, we are not responsible for issues arising from patches not being applied.
tag	Select	Add Tag after clicking the Add Tag button, Key, Value enter or select

Direction	Remote	Target address	Protocol	Port	Explanation
Inbound	CIDR	User PC IP	TCP	3389 (RDP)	Bastion access PC → Bastion host
Outbound	CIDR	DB IP	TCP	Database Port (manual entry)	Bastion host → Database

Required input element item	input value
Connection Name	Custom (ex. service name)
Host name	Database server IP
Port	Database Port
Username	Database username

MariaDB(DBaaS)

1 - Overview

Service Overview

Provided features

Components

Engine version

Server type

Preceding Service

1.1 - Server type

MariaDB(DBaaS) server type

db1 server type

MariaDB(DBaaS) Check detailed information

Detailed Information

Replica information

tag

Job History

MariaDB(DBaaS) Managing Resources

Operation Control

Synchronize service status

Change Server Type

Add storage

Expanding Storage

Terminate MariaDB(DBaaS)

2.1 - Managing DB Services

Parameter Management

Parameter View

Edit Parameter

Managing DB Users

Query DB Users

Change DB user status

Managing DB Access Control

View DB Access Control

Add DB access control

Delete DB Access Control

Configure Archive mode

Modify Audit Settings

DB Log Export

Setting DB Log Export Mode

Manage DB Log Export

Upgrade version

Major version upgrade

Minor version upgrade

Configure Migration

Promote Migration Cluster to Master Cluster

Managing Block Storage Usage

OS Kernel Upgrade

2.2 - Backing up and restoring the DB

Backing up MariaDB(DBaaS)

Configure Backup

Perform backup immediately

Check backup history

Delete backup file

Recover MariaDB(DBaaS)

2.3 - Configure Read Replica

Configure Replica

Reconfigure Replica

Promote Replica Cluster to Master Cluster

2.4 - MariaDB(DBaaS) server connection

Scenario Overview

Scenario components

Scenario setup method

1. ## Configure Network

1-1. ### Create VPC

1-2. ### Create Subnet

1-3. ### Create Internet Gateway

1-4. ### Create Public IP

1-5. ### Create Security Group

2. ## Create Bastion host

2-1. ### Create Server Keypair

2-2. ### Create Bastion host

2-3. ### Check Bastion host login ID and PW

3. ## Create Database

3-1. ### MariaDB(DBaaS) Create Service

4. ## Configure Rules

4-1. ### Security Group Add security rule

4-2. ### Add IGW Firewall rule

5. ## Database Connect

5-1. ### Connecting to Bastion host

5-2. ### Install the DB client program (MySQL Workbench) on the Bastion host

5-3. ### Connect to the database using a DB client program (MySQL Workbench)