Fortinet Document Library

Version:


Table of Contents

Copy Link

Uploading licenses for hybrid case

on-demand only case does not need to do this step.

In Hybrid case, that is, a fixed amount of BYOL instances and an autoscaling group consisting of on-demand instances, you need to upload one or more licenses before deployment. With these licenses, the BYOL instances can work correctly after the template deployment is completed.

Upload the license to s3 where you store the deployment package and save it under the <your S3 bucket>/<root dir>/license/ directory.

Please make sure every license is valid and not used by other VM. FortiWeb-VM will contact license server to validate its license. Invalid license or duplicate license will cause the FortiWeb-VM cluster to not work.

The Lambda service ensures that each FortiWeb-VM is assigned a license and one license is not assigned repeatedly.

After FortiWeb-VM receives the license, it checks that the license file is legal, restarts the instance, and contacts the license server to check whether the license is valid again. The procedure for verifying the license is different from importing the license manually through the GUI. Once FortiWeb-VM obtains a license, it will not request a new one, even if the license is later proved to be illegal. So please make sure that each provided license is valid and not duplicated.

If you use the templates to create N (N>=2) hybrid deployments, please delete the license files in the license directory and upload new license files after the previous stack deployment is completed. Because each hybrid deployment has a separate database to record the FortiWeb-VM to which the license is assigned. The new deployment will consider the license files in the license directory to be legal and not used by other FortiWeb-VM, which will lead to failure.

The amount of licenses needs to be greater than or equal to the amount of BYOL instances.

Please prepare a license for each BYOL-FortiWeb you want to start. In the current version, the terminated BYOL-FortiWeb license will not be used again.

If BYOL-FortiWeb is manually terminated, the hybrid solution will start a new BYOL-FortiWeb to maintain a fixed amount of BYOL-FortiWeb. The newly launched BYOL-FortiWeb will try to request a license. If you do not reserve a legal license for it, it becomes unlicensed and it cannot work with other FortiWeb.

If you want to start a new BYOL-FortiWeb by manually modifying the autoscaling parameters, please make sure that there is a legal license reserved for it in the s3 license directory. And this license has not been used by other BYOL-FortiWeb that is running or has been terminated in the hybrid solution.

Uploading licenses for hybrid case

on-demand only case does not need to do this step.

In Hybrid case, that is, a fixed amount of BYOL instances and an autoscaling group consisting of on-demand instances, you need to upload one or more licenses before deployment. With these licenses, the BYOL instances can work correctly after the template deployment is completed.

Upload the license to s3 where you store the deployment package and save it under the <your S3 bucket>/<root dir>/license/ directory.

Please make sure every license is valid and not used by other VM. FortiWeb-VM will contact license server to validate its license. Invalid license or duplicate license will cause the FortiWeb-VM cluster to not work.

The Lambda service ensures that each FortiWeb-VM is assigned a license and one license is not assigned repeatedly.

After FortiWeb-VM receives the license, it checks that the license file is legal, restarts the instance, and contacts the license server to check whether the license is valid again. The procedure for verifying the license is different from importing the license manually through the GUI. Once FortiWeb-VM obtains a license, it will not request a new one, even if the license is later proved to be illegal. So please make sure that each provided license is valid and not duplicated.

If you use the templates to create N (N>=2) hybrid deployments, please delete the license files in the license directory and upload new license files after the previous stack deployment is completed. Because each hybrid deployment has a separate database to record the FortiWeb-VM to which the license is assigned. The new deployment will consider the license files in the license directory to be legal and not used by other FortiWeb-VM, which will lead to failure.

The amount of licenses needs to be greater than or equal to the amount of BYOL instances.

Please prepare a license for each BYOL-FortiWeb you want to start. In the current version, the terminated BYOL-FortiWeb license will not be used again.

If BYOL-FortiWeb is manually terminated, the hybrid solution will start a new BYOL-FortiWeb to maintain a fixed amount of BYOL-FortiWeb. The newly launched BYOL-FortiWeb will try to request a license. If you do not reserve a legal license for it, it becomes unlicensed and it cannot work with other FortiWeb.

If you want to start a new BYOL-FortiWeb by manually modifying the autoscaling parameters, please make sure that there is a legal license reserved for it in the s3 license directory. And this license has not been used by other BYOL-FortiWeb that is running or has been terminated in the hybrid solution.