MTN Managed Database Provisioning Workflow on MTN Cloud

v1.0

Overview

The MTN Managed Database is a fully managed MySQL or PostgreSQL service on MTN Cloud. Unlike self‑managed database offerings, MTN Cloud handles the underlying infrastructure, patching, and operational tooling — while you retain control over schema design, users, databases, and access permissions through a dedicated management interface.

Why it matters:

  • Streamlined provisioning: Leveraging the Catalog Item automates deployment, ensuring a consistent, ready‑to‑use managed database platform.
  • Reduced operational overhead: MTN Cloud maintains the underlying infrastructure, freeing your team to focus on data and application logic rather than server maintenance.
  • Built‑in management tooling: A dedicated interface provides user/database management, monitoring, SQL execution, and log shipping without needing separate tools.

Prerequisites

Before you begin, ensure you have:

  • An active MTN Cloud login with permissions to view Provisioning (Instances, Apps, and Catalog) and Infrastructure (Network).
  • A security group already defined for this deployment. For guidance on creating one, see the Security Groups guide.
  • A deployment plan for the database instance (engine choice, sizing, environment, network placement).

Tip: If you don’t see required features and resources, contact your tenancy administrator (Customer Admin User) or support. A refresh of the portal page may also resolve this.

Important Note: Ensure the required ports for your chosen engine (MySQL or PostgreSQL) are added as an inbound rule in your personal security group and applied to the Managed Database server, in addition to the default security group.

Deploy MTN Managed Database Server

Purpose: Enable the automated deployment of a MySQL or PostgreSQL Managed Database server within the MTN Cloud environment using Catalog Items.

Step 1 – Select Catalog Item

  • Navigate to: Provisioning > Catalog.
  • Select the catalog item MTN Managed Database.
Catalog view with the MTN Managed Database item available for order
  • Assign the following fields:
    • Instance Configuration: Name, Labels, Group, Cloud, Environment, Resource Pool, Plan, Volumes, Network(s), Security Groups (default and the security group created earlier), Floating IP.
    • Database Configuration: Database Engine (PostgreSQL or MySQL), Version (based on engine selected), Number of Nodes (locked at 1 — multi‑node support is coming soon), Admin Username, Admin Password.
Order form showing Group, Cloud, Name, Environment, and expandable Instance and Database Configuration sections
  • Click Order Now, then navigate to: Provisioning > Apps.
Provisioning > Apps view showing the deployed Managed Database application

Verify Deployment

  • Clicking on the application shows additional details, including the estimated provisioning time (ETA) and a list of associated instances or virtual machines.
Managed Database application view showing provisioning progress and ETA
  • Once running, the summary view displays health, availability, response time, and live resource usage (CPU, memory, storage).
Running Managed Database application with health and resource metrics

Managed Database Management Tabs

Beyond the standard views, the MTN Managed Database interface includes specialized tabs for visibility, manageability, and direct interaction with your instance.

Connection Details

Displays essential connectivity parameters — hostnames, IP addresses, port configuration, and the credentials or connection strings needed to link applications to the database instance.

Connection Details tab showing host, port, version, database, username, and connection string

Tip: Click the refresh button to apply changes made in the settings.

Connection Details with the refresh prompt and Monitoring & Logging endpoints

Insights

Provides real-time performance monitoring, including database connections, throughput (QPS), queries per second, database size, and cache hit ratio.

Insights tab showing live connection, throughput, cache hit ratio, and row activity charts

Settings

Provides granular control over the Managed Database configuration.

User Management

View existing users, or add and create new accounts. Reset passwords for existing accounts.

Settings tab showing the Users list with password expiry and available actions

To add a user:

  • Click + Add User.
  • Specify the username, password, and an optional expiry (in days).
  • Toggle whether the account is for a service or an individual (human user).
Add User wizard with username, password, expiry, and human-user toggleAdd User wizard with the Human user toggle enabled and details completed

Existing users can be managed by:

  • Resetting passwords
  • Setting expiry dates
  • Locking accounts
  • Dropping them entirely
Users list with Reset Password, Set Expiry, Lock, and Drop actions

Databases

Manage existing databases, create new ones, and assign ownership or access permissions.

Databases panel listing existing databases with owner, size, and actions

To add a database:

  • Click + Add Database.
  • Specify the database name.
  • Assign a user and set their access level: Owner, Read/Write, or Read Only.
Add Database wizard with name, user assignment, and access-level dropdown

Existing databases can be managed by updating or removing user access, or by dropping the database.

Manage database access by updating or removing users, or dropping the database

Network Access (PostgreSQL Only)

Secure remote access by enabling SSL and defining allowed client CIDRs.

  • Select the Require SSL checkbox to enforce secure connections.
Network / Access panel before any CIDR is added
  • Click + Add CIDR and enter the authorized IP range to permit remote access.
  • Click Save to apply.
Network / Access panel with SSL enforcement and allowed client CIDR list

Important Note: Until at least one CIDR is added, remote access is denied entirely.

Active Sessions

Real-time overview of current client connections. Use the refresh button to update this on demand.

Active Sessions panel with a refresh button

Parameters

View and modify configurable settings and performance parameters for your instance. Some parameters require a restart to take effect.

  • MySQL examples: max_connections, innodb_buffer_pool_size
  • PostgreSQL examples: shared_buffers, max_wal_size
Parameters tab for a Managed MySQL instanceParameters tab for a Managed PostgreSQL instance

Monitoring & Logging

Enable Fluent Bit, Prometheus, or both, to configure logging and monitoring for the instance.

Monitoring & Logging panel with Fluent Bit and Prometheus rows

Fluent Bit

Fluent Bit enabled with no destinations yet
  • Click Enable.
  • Select a log destination and enter the required connection details. Supported destination types:
    • Grafana Loki
    • Elasticsearch / OpenSearch
    • HTTP Endpoint
    • Fluent Forward
    • MTN Object Storage (MOS)
Fluent Bit destination form with Type set to Grafana Loki, showing Host, Port, and Labels fieldsFluent Bit destination form with Type set to Elasticsearch / OpenSearch, showing Host, Port, and Index fieldsFluent Bit destination form with Type set to HTTP endpoint, showing Host, Port, and URI fieldsFluent Bit destination form with Type set to Fluent Forward, showing Host and Port fieldsFluent Bit destination form with Type set to MTN Object Storage, showing Endpoint URL, Bucket, Access key, and Secret key fields

(Optional) Enable Use TLS to secure the connection for each destination.

Destination form with the Use TLS checkbox enabled

(Optional) Check Verify Certificate to validate the certificate against the collector’s hostname, and paste the CA certificate if required.

Note: verification requires the collector’s hostname, since certificates rarely match a bare IP address.

Destination form with Verify Certificate enabled and the CA certificate field expanded

Click Test Connection, then Save & Restart to apply.

Completed destination form with the Test Connection button ready to use

Important Note: Saving restarts the Fluent Bit service and may cause a brief connection gap. By default, logs are stored locally on each node; add a destination to ship them externally.

For granular control over log output per destination, click the + Advanced (output tuning) link to access advanced configuration options.

  • For Grafana Loki, configure the line format, retry limits, and worker settings.
Grafana Loki advanced output tuning with line format, retry limit, and workers
  • For Elasticsearch / OpenSearch, configure the Logstash format, replace dots, compression, and worker settings.
Elasticsearch / OpenSearch advanced output tuning with Logstash format, replace dots, compression, retry limit, and workers
  • For HTTP Endpoint, configure the format, compression, retry limits, and worker settings.
HTTP endpoint advanced output tuning with format, compression, retry limit, and workers
  • For Fluent Forward, configure Time as integer, require ack, compression, retry limits, and worker settings.
Fluent Forward advanced output tuning with Time as integer, require ack, compression, retry limit, and workers
  • For MTN Object Storage, configure compression, max file size (MB), upload intervals (seconds), retry limit, and worker settings.
MTN Object Storage advanced output tuning with compression, max file size, upload interval, retry limit, and workers

Note: Increasing the number of parallel upload threads improves performance for high-volume logs but consumes more CPU and RAM.

Prometheus

  • Click Enable on the Prometheus row.
Prometheus row set to Active
  • Once active, connection details for both Fluent Bit and Prometheus appear under the Connection Details tab.
Connection Details tab showing Monitoring & Logging endpoints for Fluent Bit and Prometheus

Tip: Prometheus web access uses your admin username and admin password as login credentials.

SQL Editor

SQL Editor provides an integrated, web-based console for running ad-hoc queries and performing database maintenance directly within the portal.

  • Open multiple query tabs using the + icon.
  • Select which database to run queries against from the Database dropdown.
  • Select the account to run as from the Run As dropdown — Admin and service accounts can query their assigned databases. At the same time, Admin has universal access across all databases on the instance.
SQL Editor with multiple query tabs and a database selector

You can add multiple query tabs by clicking the plus icon.

Adding query tabs with the plus icon

You can select the database against which you want to run queries by clicking on the dropdown menu.

Selecting the database from the dropdown menu

The SQL Editor allows Admin and service accounts to execute queries on their assigned databases, while the Admin account has universal access across all databases.

Run As account selection dropdown

Run a Query

To run a query:

  • Write or paste your query (or highlight part of it to run just that selection).
  • Click Run.
  • Results appear in rows directly below the editor.
SQL Editor showing a query being run as AdminQuery results displayed below the SQL Editor

Topology

The Topology tab displays the managed database’s cluster layout, including single- or multi-node configurations (multi-node support coming soon), and lists each node with its assigned role (primary / replica) and state.

Topology tab showing a single-node MySQL cluster with its primary node online

Tip: Refresh the tab to view the real-time cluster status.

Important Tips & Notes

  • If you cannot see required features or actions don’t reflect, try refreshing the portal page or clearing your browser cache.
  • While MTN Cloud maintains the underlying infrastructure, you retain full responsibility for data management — schema design, query optimization, indexing, and user access control.
  • Access to the MTN Managed Database service is restricted to accounts with the Customer Admin User, Customer Power User, or Customer Database Admin role.