MTN Logo

Self-Managed MTN MongoDB Database Server Provisioning Workflow on MTN Cloud

Before You Start (prerequisites)

  • 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.

  • Define a Security Group
  • 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 MongoDB Database Server:Launch a fully configured MongoDB–based database server on the MTN Cloud to provide secure, reliable database services using either Catalog Items or the Instance Tab.

Important Note:Port 27017 and any other relevant port configured for the MongoDB service—must be added as an inbound rule in the personal security group and applied to the MongoDB 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
Navigate to Infrastructure > Network > Security Groups
  • Click +Add
Security Groups tab under NetworksClick +ADD on the Security Groups tab
  • 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
Configuring an ingress/egress rule
  • 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 MongoDB Database Server

Purpose:Enable the automated deployment of a MongoDB–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.
Navigate to Provisioning > Catalog
  • Select catalog item (MTN MongoDB)
Select the MTN MongoDB catalog item
  • 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
      • 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
      • Admin Username
      • 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
      • (Optional) Install Database Tools
      • (Optional) Install Atlas CLI
      • (Optional) Install MCP
      • (Optional) Install MongoSync
      • (Optional) Install MongoSH
MTN MongoDB order form
  • Click Order Now
  • Navigate to: Provisioning > Instances
MongoDB Server provisioning under Provisioning > Instances
  • Once provisioning is complete, open the Console tab to verify that the MongoDB server has been installed and configured successfully.
Open the Console tab on the MongoDB Server instance
  • Once the Console is open, you’ll see key details about the newly provisioned MongoDB server, confirming that installation and configuration completed successfully.
MongoDB deployment complete details in the Console

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

Create Instance with the MTN MongoDB Single-Node instance type

Important Tips & Notes

  • The MongoDB server is deployed with default authentication and security settings. For production use, consider strengthening passwords and adjusting 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.