Determine your licensing model

This recipe is part of the process of deploying FortiGate for AWS. See below for the rest of the recipes in this process:

1. Determine your licensing model
2. Register and download your licenses
3. Create a VPC and subnets
4. Attach the new VPC to the Internet gateway
5. Subscribe to the FortiGate
6. Create a routing table and associate subnets
7. Connect to the FortiGate
8. [Use case] Set up a Windows Server in the protected network
9. [Connectivity test] Configure FortiGate firewall policies and virtual IPs

FortiGate-VM for AWS supports both on-demand (PAYG) and bring-your-own-license (BYOL) licensing models.

On-demand users don’t need to register from the FortiGate GUI console. If you’re using an on-demand licensing model, once you create the FortiGate-VM instance in AWS, contact Fortinet Customer Support (http://www.fortinet.com/support/contact_support.html) with the following information:

• The serial number of your FortiGate-VM instance
• The email ID of your Fortinet account. If you don’t have a Fortinet account, you can create one at https://support.fortinet.com/login/CreateAccount.aspx.

If you’re deploying a FortiGate-VM in the AWS Marketplace with BYOL, you must obtain a license to activate it.

The post Determine your licensing model appeared first on Fortinet Cookbook.