> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-deploy-a-fortigate-vnf.md).

# How to Deploy a FortiGate VNF in the Cloud

A FortiGate VNF is a virtual network function: a Fortinet firewall that you deploy as a server within your subscription and operate yourself.

In this guide you create it from the Marketplace, connect it to your networks, and validate access to its console.

> #### 👍 What you get
>
> A FortiGate deployed and running, with a public IP on its management interface and access confirmed via web console and SSH.

### Before you start

* Have access to the Plenit panel with permissions to create servers.
* Have a name in mind (for example `FortiServer`) and the region and zone for the deployment.
* Reserve at least the resources recommended by Fortinet: **1 vCPU**, **2 GB of RAM** and **2 GB of disk**.
* Decide which networks to connect (one for management and, if applicable, one internal) and whether you will use a manual or auto-generated password.

### Step 1. Create a new server

In the panel, go to **New → Servers**, create a new server subscription and give it an identifying name (for example `FortiServer`). VNF such as FortiGate are managed within the Servers service. Click Continue: the New server wizard opens, with six steps (location, size, image, disks, network, and settings).

![Creation of a new server for the FortiGate VNF](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FrxO475q2MZlRLlq0Mq3C%2Fservidores-fortigate-vnf-01.png?alt=media\&token=aa97708e-af57-47d8-be9f-8cc818f2e46d)

### Step 2. Select region and zone

Choose the region and availability zone that best fit your infrastructure or your client's.

![Selection of deployment region and zone](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F7RTOiZMcqZoykSQ8eNzS%2Fservidores-fortigate-vnf-02.png?alt=media\&token=5e33691f-1859-4d59-9577-47be8f41f1cc)

### Step 3. Assign resources

Choose the CPU and RAM size, starting from Fortinet's minimums (1 vCPU, 2 GB of RAM, 2 GB of disk). If you are going to move a lot of traffic or several VPNs, size above the minimum.

![CPU and RAM assignment](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FyMJv716mpSQgwhCoLStp%2Fservidores-fortigate-vnf-03.png?alt=media\&token=823a13a4-85bc-40f4-8e57-6d834787bd7e)

### Step 4. Select the FortiGate image

In the **Images**section, open the **Marketplace**, choose **FortiGate-VM** and select the version that best fits your infrastructure.

![Selection of the FortiGate image in the Marketplace](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FQgLGFsKT0c7bt9sFtzXH%2Fservidores-fortigate-vnf-04.png?alt=media\&token=42ab364c-a453-446e-8aef-9218d69532cb)

### Step 5. Configure storage

Keep the main disk at **2 GB**: due to a manufacturer limitation, the disk where the VNF is installed only supports that size. If you need space for configurations, logs, or extra storage, add additional disks (up to **1 TB** each, and you can add several).

![Configuration of the main disk and additional disks](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FEeEhqZhVbOui4aapkVTG%2Fservidores-fortigate-vnf-05.png?alt=media\&token=0dc9dfb4-45ef-464c-90f9-9479314445eb)

### Step 6. Configure the network

This image requires at least two network interfaces. For each one you can choose between **Direct IP**, **Standard**, **VPC** or **Layer 2 (L2)**. For a functional deployment, the usual setup is a **management** interface **Direct IP** with **an internal** interface **L2 network** to route traffic for your infrastructure.

The management network you choose changes how you control access:

| Management network | Does it filter by source IP? | Access control                                           |
| ------------------ | ---------------------------- | -------------------------------------------------------- |
| Standard or VPC    | Yes, from the network        | Extra control layer before traffic reaches the FortiGate |
| Direct IP          | No from the network          | With GeoIP or with FortiGate's own policies              |

![Configuration of the management and internal interfaces](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FMSM5IXkADSqy6M3ZzkeS%2Fservidores-fortigate-vnf-06.png?alt=media\&token=c3d8b728-0f64-4187-8809-480b379575f9)

> #### 📘 If you use Direct IP, control access separately
>
> With Direct IP, traffic reaches the FortiGate's public interface directly and you cannot filter by source IP from the network.
>
> Apply control with [GeoIP](https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-configure-geoip-to-block-or-allow-countries.md) or with security policies on the FortiGate itself.

### Step 7. Complete the final configuration

**Identification**: define the **hostname**, the **administrator user** (by default `admin`) and the **password**, manual or auto-generated.

> #### ❗️ The auto-generated password cannot be changed later
>
> If you do not fill in the password, the user will be `admin` and the password will be generated automatically and provided when the server is created.
>
> That auto-generated password cannot be changed later with the password reset function, so save it in a safe place at the time of creation.<br>

**Monitoring (SNMP Community)**: it is disabled by default. Enable it in the deployment to view basic CPU, memory, and disk metrics from the start; if you do not do it here, you can enable it later through the FortiGate CLI, but the panel option will remain disabled.

**Administration ports** on the management network:

* **HTTPS**: you can leave it at 443, although it is recommended **8443**.
* **SSH**: you can map it to an alternative port, for example **2022**.

Review the configuration and click **Create server**. After deployment you will connect with `https://IP:8443` and `ssh admin@IP -p 2022`.

![Hostname, credentials, SNMP, and port configuration](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FXtbLHEucMKgQzdWfJkiV%2Fservidores-fortigate-vnf-07.png?alt=media\&token=a5e767ec-4aa5-47bd-bee2-66663790da6b)

### Step 8. Validate the deployment and connect

In **Servers / My servers**, locate the newly created subscription and check that the status is **Running / Active** and that the **Direct IP** interface has a public IP assigned. Then open the web console in the browser:

```scala
https://IP:8443
```

Enter the credentials from Step 7 (or `admin` and the auto-generated password). If everything is correct, you will see the FortiGate web console ready.

To check it from the terminal, verify that the management port responds and, if you work via CLI, log in via SSH:

```bash
curl -kI https://<IP>:8443
ssh admin@<IP> -p 2022
```

(The `-k` is because the initial certificate is self-signed.)

### Validation

Consider the deployment successful if all of this is true:

* The server appears in status **Running / Active**.
* The interface **Direct IP** has a public IP assigned.
* The web console responds at `https://IP:8443`.
* You log in with the configured credentials or the auto-generated ones.

### Operational and security notes

* With **Direct IP** as management, restrict access with GeoIP or FortiGate policies, since the network does not filter by source IP.
* Change the administration ports to non-standard values (8443 / 2022) to reduce exposure.
* Save the auto-generated password as soon as the server is created.
* After the first access, review the logs and export an initial copy of the configuration.

### Conclusion

With this you have a FortiGate VNF deployed and accessible, ready to be integrated into your infrastructure as a perimeter under your control.

From here, the steps that make the difference are the usual ones in a firewall: register the license and FortiGuard services if applicable, set up the security policies, export a backup of the initial configuration, and leave SNMP monitoring sending metrics.

The sooner you harden management access, the less exposed the device remains.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-deploy-a-fortigate-vnf.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
