Before Launching the Templates
Before you launch the templates to integrate
a VM-Series firewall auto scaling group with an AWS GWLB, you must
complete the following procedure.
- Ensure that you have the following before you begin.
- Obtain the auth code for a bundle that supports the number of firewalls that might be required for your deployment. You must save this auth code in a text file namedauthcodes(no extensions), and put theauthcodesfile in the/licensefolder of the bootstrap package.
- Download the files required to launch the VM-Series Gateway Load Balancer template from the GitHub repository.
- Create a Transit Gateway. This transit gateway connects your security and application VPCs.
- Take note of the transit gateway ID; you will need it later when deploying the template.
- You must add a 0.0.0.0/0 route to the application attachment route table pointing to the security attachment to protect east-west and outbound traffic.
- Ensure thatDefault route table associationandDefault route table propagationare disabled.
- The recommended VPC CIDR for the firewall and application templates should be larger than /23.
The target group of the gateway GWLB cannot use HTTP for health checks because the VM-Series firewall does not allow access with an unsecured protocol. Instead use HTTPS or TCP. - Deploy Panorama running 10.0.2 and configure the following.Panorama must allow AWS public IP addresses. The VM-Series firewall accesses Panorama using the external IP address of the NAT gateway created by the template.
- Download and install the VM-Series plugin on Panorama.
- Selectand usePanoramaPluginsCheck Nowto look for new plugin packages. The VM-Series plugin name isvm_series.
- Consult the plugin release notes to determine which version provides upgrades useful to you.
- Select a version of the plugin and selectDownloadin the Action column.
- ClickInstallin the Action column. Panorama alerts you when the installation is complete.
- To view the plugin, select.DeviceVM-Series
- Configure the template.
- Log in to the Panorama web interface.
- Selectand clickPanoramaTemplatesAdd.
- Enter a descriptiveName.
- ClickOK.
- Configure the virtual router.
- Select.NetworkVirtual Routers
- Ensure that you have selected the template you create above from theTemplatedrop-down.
- ClickAdd.
- Name the virtual router using the following format: VR-<tempstackname>.
- Enable ECMP on the virtual router.
- ClickOK.
- Configure the interface and create the zone.
- Selectand clickNetworkInterfacesAdd Interface.
- SelectSlot 1and then select the Interface name (for example, ethernet 1/1).
- SetInterface Typeto Layer 3.
- On theConfigtab, selectNew Zonefrom theSecurity Zonedrop-down. In the Zone dialog, define aNamefor new zone, for example Internet, and then clickOK.
- In theVirtual Routerdrop-down, select virtual router your created above.
- SelectIPv4and clickDHCP Client.
- ClickOK.
- Create a management profile that allows HTTPS on the interface created above to support Health Checks.
- Selectand clickNetworkNetwork ProfilesInterface MgmtAdd.
- Select the protocols that the interface permits for management traffic:Ping,Telnet,SSH,HTTP,HTTP OCSP,HTTPS, orSNMP.Don’t enableHTTPorTelnetbecause those protocols transmit in cleartext and therefore aren’t secure.
- Assign the Interface Management profile to an interface.
- Select, select the type of interface (NetworkInterfacesEthernet,VLAN,Loopback, orTunnel), and select the interface.
- Selectand select the InterfaceAdvancedOther infoManagement Profileyou just added.
- ClickOK.
- Configure the DNS server and FQDN refresh time.
- Selectand click the Edit icon.DeviceSetupServices
- Set thePrimary DNS Serverto 169.254.169.253. This is the AWS DNS address.
- Set theMinimum FQDN Refresh Timeto 60 seconds.
- ClickOK.
- Commityour changes. This is required before proceeding to the next step.
- Create an administrator.
- SelectDeviceAdministrators.
- Enterpandemoas theName.
- Set thePasswordtodemopasswordandConfirm.
- ClickOK.
- Commityour changes.
- Configure a template stack and add the template to the template stack.
- SelectandPanoramaTemplatesAdd Stack.
- Enter a uniqueNameto identify the stack.
- ClickAddand select the template.
- ClickOKto save the template stack.
- Create theDevice Group.
- Select.PanoramaDevice Groups
- ClickAdd.
- Enter a descriptiveName.
- ClickOK.
- Add an allow all security pre-rule.
- Selectand clickPoliciesSecurityPre RulesAdd.
- Enter a descriptiveName.
- UnderSource,User,Destination,Application, andService/URL Category, select any.
- UnderActions, selectAllow.
- ClickOK.
- Commityour changes.
- Add the license deactivation API key for the firewall to Panorama.
- Log in to the Customer Support Portal.
- Select.AssetsAPI Key Management
- Copy the API key.
- Use the CLI to install the API key copied in the previous step.request license api-key set key<key>
- After deploying Panorama, you must open the following ports as described below on the Panorama security group in AWS.
- Port 443 (HTTPS)—Upon initial deployment of the firewall template, leave HTTPS open so Lambda can connect to Panorama.When you secure port 443 you specify an IP address range from which you will allow connections, as well as the EIPs assigned to the NAT gateways. The number of NAT gateways in your deployment depends on the number of availability zones you configure. To find NAT gateway EIPs in AWS, go to. Note the EIP information for the security group for HTTPS.VPCNAT GatewaysAdditionally, to allow Panorama to release the firewall license after stack deletion, you must allow traffic from the CIDR range of the region where you deployed the firewall template. You can find the CIDR for your region at this link.
- Port 3978—Port 3978 must be able to receive traffic from any IP address.