MTN PostgreSQL Database Server Provisioning Workflow on MTN Cloud

Before You Start (prerequisites)

1. Have an MTN Cloud login with permissions to view Provisioning (Instances and Catalog) and Infrastructure (Network).

Tip:If you don’t see required features and resources, contact support or refresh the portal.

2. Define a Security Group
3. Plan your deployments

The Right Sequence

• Create Security Group: Establish a controlled network boundary by defining allowed inbound and outbound traffic to secure deployed resources.
• Deploy MTN PostgreSQL Database Server:Launch a fully configured PostgreSQL‑based database server on the MTN Cloud to provide secure, reliable database services using either Catalog Items or the Instance Tab.

Important Note

Port 5432configured for the PostgreSQL service—must be added as an inbound rule in the personal security group and applied to the PostgreSQL database server, alongside the default security group.

Part 1 — Create Security Group

Purpose: Controls network access to(ingress) and from(egress) your VM.

• Navigate to: Infrastructure > Network > Security Groups

• Click +Add

• Assign:
  • Name
  • Description
  • Scoped Cloud = MTNNG_CLOUD_AZ_1
• Click the Security Group that was recently created
• Navigate to Rules
• Click on +Add Rules
• Assign:
  • Name
  • Direction = (Ingress or Egress)
  • Rule Type = Custom Rule
  • Protocol = (TCP, UDP OR ICMP)
  • Port Range (available depending on protocol selected)
  • Source Type
  • Source
  • Destination Type
  • Destination Port Range

• Scroll Down to Save Changes
• Navigate to Location
• Click on +Add Location
• Select the required Cloud where the workload to be protected is provisioned.
• Click on Save Changes

Part 2 — Deploy MTN MySQL Database Server

Purpose:Enable the automated deployment of a PostgreSQL‑based database server within the MTN Cloud environment. This process leverages Catalog Items to streamline provisioning and ensure a consistent, ready‑to‑use database platform.

• Navigate to: Provisioning > Catalog.

• Select catalog item (MTN PostgreSQL)

• Assign:
  • Group
  • Cloud
  • Name
  • Environment
  • Labels
  • Instance Configuration
    • Resource Pool
    • Plan
    • Volumes
    • Network(s)
    • Security Groups (default and the security group created earlier)
    • Floating IP
  • Database Configuration
    • Postgres Version (15, 16, 17 or 18)
    • Database Name
    • DB Username
    • DB Password
    • (Optional) Make DB Owner? If checked, User created will be DB Owner
    • (Optional) Require SSL for Connections?
    • Allowed CIDRs
    • (Optional) Use HostSSL? If checked, Host CIDRs will be imputed as HostSSL
    • Password Expiry Days
    • (Optional) Auto Security Updates

• Click Order Now
• Navigate to: Provisioning > Instances

• Once provisioning is complete, open the Console tab to verify that the PostgreSQL server has been installed and configured successfully.

• Once the Console is open, you’ll see key details about the newly provisioned PostgreSQL server, confirming that installation and configuration completed successfully.

Additional Deployment Method

The instance can also be provisioned via the Instances tab—the same way you would normally create an instance or virtual machine—by selecting the MTN MTN PostgreSQL Single-Node instance type.

Important Tips & Notes

1. The PostgreSQL server is deployed with default authentication and security settings. For production environments, consider enforcing stronger passwords, adjusting role permissions, and tuning security parameters in postgresql.conf and pg_hba.conf.
2. Remote connections are disabled by default. If external access is required, update the listen address, configure pg_hba.conf to allow the appropriate hosts, and ensure firewall rules permit traffic on the PostgreSQL port.
3. Applications connect using the instance’s public IP and standard PostgreSQL credentials, with no additional client‑side configuration required beyond typical connection parameters.