MTN MongoDB Database Server Provisioning Workflow on MTN Cloud
Overview
The MTN MongoDB Database Server is a self–managed, pre–configured MongoDB instance deployed within the MTN Cloud environment. It provides a secure, production–ready NoSQL database platform, provisioned via a 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 ships with optional tooling (mongosh, Atlas CLI, Database Tools) and configurable security settings to suit different environments.
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 27017, and any other port relevant to the MongoDB 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 MongoDB Database Server
Purpose: Enable the automated deployment of a MongoDB–based database server within the MTN Cloud environment using Catalog Items.
Provision via Catalog
- Navigate to: Provisioning > Catalog.
- Select catalog item MTN MongoDB.

- 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:
- MongoDB Version (6.0, 7.0, 8.0 or 8.2)
- Database Name
- DB Username
- DB Password
- MongoDB User Role (Read & Write, Read, DB Admin, DB Owner)
- (Optional) Enable Auth, with accompanying Admin Username and Admin Password
- Allowed Host CIDRs
- (Optional) Require SSL for Connections
- (Optional) Auto Security Updates
- (Optional) Initialise Replica Set
- Wired Tiger Cache (GB)
- (Optional) Install MongoSH, Database Tools, Atlas CLI, MCP, and MongoSync

- 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 MongoDB server has been installed and configured successfully.

- The console output displays server details (IP address, port, data directory, config and log file paths, database name, usernames), security settings (authentication, SSL/TLS, replica set, allowed CIDRs), and which optional tools were installed.

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 MongoDB Single–Node instance type.

Important Tips & Notes
- The server deploys with default authentication and security settings. For production use, strengthen passwords and adjust access controls in the MongoDB configuration.
- Remote connections are restricted by default. If external access is required, update the bind–address and user permissions, and ensure that firewall rules allow traffic on the MongoDB port.
- Applications connect using the instance’s public IP and standard MongoDB credentials, with no additional client–side configuration required.