Before Launching the Templates

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 named
authcodes
(no extensions), and put the
authcodes
file in the
/license
folder 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 that
Default route table association
and
Default route table propagation
are 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.
Select
Panorama
Plugins
  and use
Check Now
to look for new plugin packages. The VM-Series plugin name is
vm_series
.
Consult the plugin release notes to determine which version provides upgrades useful to you.
Select a version of the plugin and select
Download
in the Action column.
Click
Install
in the Action column. Panorama alerts you when the installation is complete.
To view the plugin, select
Device
VM-Series
.
Configure the template.
Log in to the Panorama web interface.
Select
Panorama
Templates
and click
Add
.
Enter a descriptive
Name
.
Click
OK
.
Configure the virtual router.
Select
Network
Virtual Routers
.
Ensure that you have selected the template you create above from the
Template
drop-down.
Click
Add
.
Name the virtual router using the following format: VR-<tempstackname>.
Enable ECMP on the virtual router.
Click
OK
.
Configure the interface and create the zone.
Select
Network
Interfaces
and click
Add Interface
.
Select
Slot 1
and then select the Interface name (for example, ethernet 1/1).
Set
Interface Type
to Layer 3.
On the
Config
tab, select
New Zone
from the
Security Zone
drop-down. In the Zone dialog, define a
Name
for new zone, for example Internet, and then click
OK
.
In the
Virtual Router
drop-down, select virtual router your created above.
Select
IPv4
and click
DHCP Client
.
Click
OK
.
Create a management profile that allows HTTPS on the interface created above to support Health Checks.
Select
Network
Network Profiles
Interface Mgmt
and click
Add
.
Select the protocols that the interface permits for management traffic:
Ping
,
Telnet
,
SSH
,
HTTP
,
HTTP OCSP
,
HTTPS
, or
SNMP
.
Don’t enable
HTTP
or
Telnet
because those protocols transmit in cleartext and therefore aren’t secure.
Assign the Interface Management profile to an interface.
Select
Network
Interfaces
, select the type of interface (
Ethernet
,
VLAN
,
Loopback
, or
Tunnel
), and select the interface.
Select
Advanced
Other info
and select the Interface
Management Profile
you just added.
Click
OK
.
Configure the DNS server and FQDN refresh time.
Select
Device
Setup
Services
and click the Edit icon.
Set the
Primary DNS Server
to 169.254.169.253. This is the AWS DNS address.
Set the
Minimum FQDN Refresh Time
to 60 seconds.
Click
OK
.
Commit
your changes. This is required before proceeding to the next step.
Create an administrator.
Select
Device
Administrators.
Enter
pandemo
as the
Name
.
Set the
Password
to
demopassword
and
Confirm
.
Click
OK
.
Commit
your changes.
Configure a template stack and add the template to the template stack.
Select
Panorama
Templates
and
Add Stack
.
Enter a unique
Name
to identify the stack.
Click
Add
and select the template.
Click
OK
to save the template stack.
Create the
Device Group
.
Select
Panorama
Device Groups
.
Click
Add
.
Enter a descriptive
Name
.
Click
OK
.
Add an allow all security pre-rule.
Select
Policies
Security
Pre Rules
and click
Add
.
Enter a descriptive
Name
.
Under
Source
,
User
,
Destination
,
Application
, and
Service/URL Category
, select any.
Under
Actions
, select
Allow
.
Click
OK
.
Commit
your changes.
Add the license deactivation API key for the firewall to Panorama.
Log in to the Customer Support Portal.
Select
Assets
API 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
VPC
NAT Gateways
. Note the EIP information for the security group for HTTPS.
Additionally, 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.