MTN PostgreSQL Database Server Provisioning Workflow on MTN Cloud
Overview
The MTN PostgreSQL Database Server is a self‑managed, pre‑configured PostgreSQL instance deployed within the MTN Cloud environment. It provides a secure, production‑ready relational database platform, provisioned via Catalog Item to ensure consistent configuration and rapid availability for application workloads.
Why it matters:
- Streamlined provisioning: Leveraging the Catalog Item automates deployment, ensuring a consistent, ready‑to‑use database instance.
- Controlled access: A dedicated security group restricts inbound and outbound traffic to only what the database service requires.
- Operational flexibility: The instance can be reconfigured post‑deployment (SSL enforcement, password policy, security updates) to suit production requirements.
Prerequisites
Before you begin, ensure you have:
- An active MTN Cloud login with permissions to view Provisioning (Instances 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 (sizing, environment, network placement).
Tip: If you don’t see required features and resources, contact support or refresh the portal.
IMPORTANT NOTE: Port 5432, used by the PostgreSQL service, must be added as an inbound rule in the personal security group and applied to the database server, alongside the default security group.
Deploy MTN PostgreSQL Database Server
Purpose: Enable the automated deployment of a PostgreSQL‑based database server within the MTN Cloud environment using Catalog Items.
Provision via Catalog
- Navigate to: Provisioning > Catalog.
- Select catalog item MTN PostgreSQL.

Assign the following fields:
- Group
- Cloud
- Name
- Environment
- Labels
- Instance Configuration: Resource Pool, Plan, Volumes, Network(s), Security Groups (default and the security group created earlier), Floating IP
Configure the Database
Under Database Configuration, provide:
- Postgres Version (15, 16, 17 or 18)
- Database Name
- DB Username
- DB Password
- (Optional) Make DB Owner—if checked, the created user becomes the DB owner
- (Optional) Require SSL for Connections
- Allowed CIDRs
- (Optional) Use HostSSL—if checked, host CIDRs are imputed as HostSSL
- Password Expiry Days
- (Optional) Auto Security Updates

Click Order Now once all fields are set.
Verify Deployment
- Navigate to: Provisioning > Instances.
- Once provisioning is complete, open the instance’s Console tab to confirm the PostgreSQL server has been installed and configured successfully.

- The console output displays server details (public IP, port, version, database name, username), security settings (SSL enforcement, password expiry, DB owner mode), and both remote and local/SSH connection instructions.

Alternative Provisioning
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 PostgreSQL Single-Node instance type.

Important Tips & Notes
- The server deploys with default authentication and security settings. For production environments, enforce stronger passwords, adjust role permissions, and tune security parameters in postgresql.conf and pg_hba.conf.
- 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.
- Applications connect using the instance’s public IP and standard PostgreSQL credentials, with no additional client‑side configuration required beyond typical connection parameters.