Fortinet white logo
Fortinet white logo

Cloud provisioning

Cloud provisioning

Cloud provisioning or deployment is the mechanism to connect a FortiGate to FortiGate Cloud Premium and configure it for cloud management and logging. You can provision a FortiGate to FortiGate Cloud Premium using one of the following methods:

After provisioning a FortiGate to FortiGate Cloud Premium using one of the methods described, complete basic configuration by doing the following:

  1. Create a firewall policy with logging enabled. Configure log uploading if necessary.
  2. Log in to FortiGate Cloud Premium using your FortiCloud account.
Note

For FortiGates that are part of a high availability (HA) pair, you must activate FortiGate Cloud Premium on the primary FortiGate. Activate FortiGate Cloud Premium on the primary FortiGate as To provision a FortiGate/FortiWifi to FortiGate Cloud Premium in the FortiOS GUI: describes. FortiGate Cloud Premium activation on the primary FortiGate activates FortiGate Cloud Premium on the secondary FortiGate. Local FortiGate Cloud Premium activation on the secondary FortiGate will fail.

To provision a FortiGate/FortiWifi to FortiGate Cloud Premium using the FortiCloud key:
  1. Log in to the FortiGate Cloud Premium portal.
  2. Go to Assets > Asset list, then click Add FortiGate. If the device is available on the list shown on the inventory slide, select the device and click Provision. If else, click Import FortiGate.
  3. In the FortiCloud or FortiDeploy key field, enter the key printed on your FortiGate.
  4. From the Select Display Timezone for Device dropdown list, select the desired time zone.
  5. Click Submit.
    Note

    After the device is successfully deployed, the device key becomes invalid. You can only use the key once to deploy a device.

To provision a FortiGate/FortiWifi to FortiGate Cloud Premium in the FortiOS GUI:
  1. In the FortiCloud portal, ensure that you have a product entitlement for FortiGate Cloud for the desired FortiGate or FortiWifi.
  2. In FortiOS, in the Dashboard, in the FortiGate Cloud widget, the Status displays as Not Activated. Click Not Activated.
  3. Click the Activate button.
  4. In the Activate FortiGate Cloud panel, the Email field is already populated with the FortiCloud account that this FortiGate is registered to.
  5. In the Password field, enter the password associated with the FortiCloud account.
  6. Enable Send logs to FortiGate Cloud. Click OK.

  7. This should have automatically enabled Cloud Logging. Ensure that Cloud Logging was enabled. If it was not enabled, go to Security Fabric > Fabric Connectors > Cloud Logging, enable it, then set Type to FortiGate Cloud.
  8. You must set the central management setting to FortiCloud, as this is the initial requirement for enabling device management features.
To configure a FortiGate-VM for FortiGate Cloud Premium:

FortiGate-VMs require additional configuration to ensure that they function with FortiGate Cloud Premium. Run the following commands in the FortiOS CLI:

config system fortiguard

unset update-server-location

end

Cloud provisioning

Cloud provisioning

Cloud provisioning or deployment is the mechanism to connect a FortiGate to FortiGate Cloud Premium and configure it for cloud management and logging. You can provision a FortiGate to FortiGate Cloud Premium using one of the following methods:

After provisioning a FortiGate to FortiGate Cloud Premium using one of the methods described, complete basic configuration by doing the following:

  1. Create a firewall policy with logging enabled. Configure log uploading if necessary.
  2. Log in to FortiGate Cloud Premium using your FortiCloud account.
Note

For FortiGates that are part of a high availability (HA) pair, you must activate FortiGate Cloud Premium on the primary FortiGate. Activate FortiGate Cloud Premium on the primary FortiGate as To provision a FortiGate/FortiWifi to FortiGate Cloud Premium in the FortiOS GUI: describes. FortiGate Cloud Premium activation on the primary FortiGate activates FortiGate Cloud Premium on the secondary FortiGate. Local FortiGate Cloud Premium activation on the secondary FortiGate will fail.

To provision a FortiGate/FortiWifi to FortiGate Cloud Premium using the FortiCloud key:
  1. Log in to the FortiGate Cloud Premium portal.
  2. Go to Assets > Asset list, then click Add FortiGate. If the device is available on the list shown on the inventory slide, select the device and click Provision. If else, click Import FortiGate.
  3. In the FortiCloud or FortiDeploy key field, enter the key printed on your FortiGate.
  4. From the Select Display Timezone for Device dropdown list, select the desired time zone.
  5. Click Submit.
    Note

    After the device is successfully deployed, the device key becomes invalid. You can only use the key once to deploy a device.

To provision a FortiGate/FortiWifi to FortiGate Cloud Premium in the FortiOS GUI:
  1. In the FortiCloud portal, ensure that you have a product entitlement for FortiGate Cloud for the desired FortiGate or FortiWifi.
  2. In FortiOS, in the Dashboard, in the FortiGate Cloud widget, the Status displays as Not Activated. Click Not Activated.
  3. Click the Activate button.
  4. In the Activate FortiGate Cloud panel, the Email field is already populated with the FortiCloud account that this FortiGate is registered to.
  5. In the Password field, enter the password associated with the FortiCloud account.
  6. Enable Send logs to FortiGate Cloud. Click OK.

  7. This should have automatically enabled Cloud Logging. Ensure that Cloud Logging was enabled. If it was not enabled, go to Security Fabric > Fabric Connectors > Cloud Logging, enable it, then set Type to FortiGate Cloud.
  8. You must set the central management setting to FortiCloud, as this is the initial requirement for enabling device management features.
To configure a FortiGate-VM for FortiGate Cloud Premium:

FortiGate-VMs require additional configuration to ensure that they function with FortiGate Cloud Premium. Run the following commands in the FortiOS CLI:

config system fortiguard

unset update-server-location

end