Fortinet (BYOL) Provisioning Workflow on MTN Cloud

Overview

The Fortinet (BYOL) provisioning workflow provides a structured process for deploying a Fortinet firewall instance on MTN Cloud. The workflow covers the preparation of users, networks, Security Groups, and resource pools before provisioning the Fortinet instance.

The deployment process also includes an example Security Group configuration for restricting access to the Fortinet instance to a specific laptop IP address.

Why it matters:

  • Provides a structured process for provisioning Fortinet on MTN Cloud.
  • Allows network access to the Fortinet instance to be controlled through Security Groups.
  • Supports Bring Your Own Licence (BYOL) deployments.
  • Enables administrators to restrict management access to specific source IP addresses.
  • Allows additional Security Groups to be attached to the Fortinet instance after provisioning.

Prerequisites

Before beginning the Fortinet provisioning workflow, ensure that:

  • An MTN Cloud login with permissions to view Infrastructure and Provisioning is available.
  • A Project (Resource Pool) has been created.
  • At least one network has been created.
  • If required, a router has been created and the required network has been attached to it.
  • Deployment requirements have been planned, including:
    • Resource specifications.
    • Network placement.
    • IP address requirements.
    • Required inter-communication.
    • Security Group rules.
    • Whether a floating IP is required.

Tip: If your networks or Security Groups are not visible during provisioning, refresh the MTN Cloud portal or contact support.

Provisioning Sequence

The source recommends completing the deployment in the following sequence:

  1. Create the required Linux/Windows user.
  2. Define the required Security Group.
  3. Provision the Fortinet instance.
  4. Attach the appropriate network and floating IP.
  5. Apply the default Security Group during provisioning.
  6. Add any additional Security Group after the Fortinet instance has been created.

The default Security Group provides basic functionality such as console access and instance health checks. The source recommends applying the default Security Group during Fortinet creation.

Create Linux/Windows User

Purpose: Allow logins to instances provisioned through the console and establish resource ownership within MTN Cloud.

Navigation: User Account > User Settings > Linux Settings

  1. Log in to the MTN Cloud user account.
  2. Click the dropdown beside your name at the top-right of the screen.
  3. Select User Settings.
  4. Locate Linux Settings.
  5. Enter the required:
    • Username
    • Password
    • Confirm Password
  6. Select an SSH key entry if one is available (optional).

Scroll to Windows Settings and configure the required Windows username and password. After completing the required settings, scroll to the bottom of the page and click Save.

Define Security Groups

Purpose: Control network access to and from the Fortinet instance, including ingress and egress traffic.

Create a Security Group

Navigation: Infrastructure > Network > Security Groups

  1. Click + Add.
  2. Enter the required:
    • Name
    • Description
    • Scoped Cloud: MTNNG_CLOUD_AZ_1
  3. Save the Security Group.
Security Group creation screen showing the Name, Description and Scoped Cloud fields

Add Security Group Rules

  1. Open the Security Group that was recently created.
  2. Navigate to the Rules tab.
  3. Click + Add Rules.
  4. Configure the required rule fields:
    • Name: Descriptive rule name
    • Direction: Ingress or Egress
    • Rule Type: Custom Rule
    • Protocol: TCP, UDP, or ICMP
    • Port Range: Based on selected protocol
    • Source Type: Required source type
    • Source: Required source
    • Destination Type: Required destination type
    • Destination Port Range: Required destination port range
  5. Scroll down and click Save Changes.
Security Group rule configuration screen showing the direction, protocol, source, destination and port settings

Assign Security Group Location

  1. Navigate to Location.
  2. Click + Add Location.
  3. Select the required Cloud where the workload to be protected is provisioned.
  4. Click Save Changes.

Restrict SSH Access to a Specific Laptop

This use case demonstrates how to configure a Security Group so that only a specified laptop can access the Fortinet instance through the required management ports. In the source example, the laptop’s public IP address is 200.200.113.15. Replace this example address with the actual public IP address of the laptop being authorized.

Create the Laptop-Specific Security Group

Navigation: Infrastructure > Network > Security Groups

  1. Click + Add.
  2. Configure:
    • Name: Laptop-SSH-Only
    • Description: Allow SSH (Secure Remote Connection) only from my laptop
    • Scoped Cloud: MTNNG_CLOUD-AZ1

IMPORTANT NOTE: The source specifically states that the appropriate Availability Zone should be selected rather than ALL.

Allow SSH from the Laptop

Navigate to the Rules tab and click + Add Rules. Configure:

  • Name: Allow-SSH-From-Laptop
  • Direction: Ingress
  • Rule Type: Custom Rule
  • Protocol: TCP
  • Port Range: 22
  • Source Type: Network
  • Source: 200.200.113.15/32
  • Destination Type: Instance
  • Destination Port Range: 22

Click Save Changes.

Security Group rule showing management access restricted to the specified laptop IP address

Allow Additional Management Rules

Repeat the add-rule steps to add the remaining management rules. Each uses Direction: Ingress, Rule Type: Custom Rule, Source Type: Network, Source: 200.200.113.15/32 and Destination Type: Instance. Click Save Changes after each rule.

  • Allow-GUI-From-Laptop: Protocol TCP, Port Range 443, Destination Port Range 443.
  • Allow-SNMP-From-Laptop: Protocol UDP, Port Range 161, Destination Port Range 161.
  • Allow-ICMP-From-Laptop: Protocol ICMP.
  • Allow-FGFM(IPV4)-From-Laptop: Protocol TCP, Port Range 541, Destination Port Range 541.
  • Allow-FGFM(IPV6)-From-Laptop: Protocol TCP, Port Range 542, Destination Port Range 542.

Attach the Security Group

Attach the Laptop-SSH-Only Security Group to the Fortinet instance in addition to the default Security Group.

Expected Result: Only the specified laptop can successfully access the Fortinet instance through the open ports. Other SSH access attempts will be denied.

Provision the Fortinet Instance (BYOL)

Once the required network and Security Group configuration is ready, provision the Fortinet instance through the MTN Cloud Catalog.

Open the Fortinet Catalog

Navigation: Provisioning > Catalog. Select Fortinet Firewall.

Configure the Fortinet Instance

Complete the provisioning form. Configure the following:

  • Group: Select the required group.
  • Cloud: Select the Cloud where Fortinet will be deployed, e.g. MTNNG_Cloud_AZ_1.
  • Environment: Development, Staging, or Production.
  • Plan: Select the plan defining CPU and memory resources.
  • Volume: Select the required volume capacity.
  • Resource Pool: Select the previously created Project / Resource Pool.
  • Network: Select a previously created network.
  • Floating IP: Assign based on the router configuration for the selected network.
  • Security Group: Apply the default Security Group first, then add the previously created Security Group.

IMPORTANT NOTE: The source specifically requires the default Security Group to be assigned first so that necessary firewall rules and traffic access can be managed. The additional Security Group created earlier can then be added to the instance.

Fortinet Firewall provisioning form showing the Group, Cloud, Environment, Plan, Volume, Resource Pool, Network, Floating IP and Security Group selections

Launch the Fortinet Instance

After completing the provisioning form:

  1. Review the selected configuration.
  2. Click Order Now.
  3. MTN Cloud will begin provisioning the Fortinet instance.
  4. Monitor the instance status until deployment is complete.
Fortinet instance status screen showing the provisioning process and deployment status

Access the Fortinet GUI

After the Fortinet instance has been provisioned, access the Fortinet GUI using the assigned connection details. The source specifies the following default credentials:

Username: admin

Password: Password@123

IMPORTANT NOTE: Change the default password after the initial login and store the updated credentials securely.

Fortinet GUI login screen for accessing the provisioned firewall instance

Deployment Notes

  • Naming Conventions: Use consistent naming conventions for keys, networks, instances, Security Groups and Security Group rules.
  • Documentation: Maintain a record of IP addresses, credentials, assigned resources, network assignments and Security Group configurations.
  • BYOL: The Fortinet deployment described in this guide is a Bring Your Own Licence (BYOL) instance.
  • Security Group Management: Regularly review and update Security Group rules to follow the principle of least privilege.
  • Reuse of Configuration: The source states that Security Groups and usernames/passwords may be reused for subsequent Fortinet installations, depending on the applicable security considerations.