Reference Architecture with Terraform: VM-Series in AWS, Centralized Design Model, Common NGFW Option
Palo Alto Networks produces several validated reference architecture design and deployment documentation guides, which describe well-architected and tested deployments. When deploying VM-Series in a public cloud, the reference architectures guide users toward the best security outcomes, whilst reducing rollout time and avoiding common integration efforts. The Terraform code presented here will deploy Palo Alto Networks VM-Series firewalls in AWS based on the centralized design; for a discussion of other options, please see the design guide from the reference architecture guides.
Reference Architecture Design
This code implements:
- a centralized design, which secures outbound, inbound, and east-west traffic flows using an AWS transit gateway (dTGW). Application resources are segmented across multiple VPCs that connect in a hub-and-spoke topology, with a dedicated VPC for security services where the VM-Series are deployed
Detailed Architecture and Design
Centralized Design
This design supports interconnecting a large number of VPCs, with a scalable solution to secure outbound, inbound, and east-west traffic flows using a transit gateway to connect the VPCs. The centralized design model offers the benefits of a highly scalable design for multiple VPCs connecting to a central hub for inbound, outbound, and VPC-to-VPC traffic control and visibility. In the Centralized design model, you segment application resources across multiple VPCs that connect in a hub-and-spoke topology. The hub of the topology, or transit gateway, is the central point of connectivity between VPCs and Prisma Access or enterprise network resources attached through a VPN or AWS Direct Connect. This model has a dedicated VPC for security services where you deploy VM-Series firewalls for traffic inspection and control. The security VPC does not contain any application resources. The security VPC centralizes resources that multiple workloads can share. The TGW ensures that all spoke-to-spoke and spoke-to-enterprise traffic transits the VM-Series.
Prerequisites
The following steps should be followed before deploying the Terraform code presented here.
- Deploy Panorama e.g. by using Panorama example
- Prepare device group, template, template stack in Panorama
- Download and install plugin
sw_fw_license
for managing licenses - Configure bootstrap definition and license manager
- Configure license API key
- Configure security rules and NAT rules for outbound traffic
- Configure interface management profile to enable health checks from GWLB
- Configure network interfaces and subinterfaces, zones and virtual router in template
In example VM-Series are licensed using Panorama-Based Software Firewall License Management sw_fw_license
, from which after configuring license manager values of panorama-server
, auth-key
, dgname
, tplname
can be used in terraform.tfvars
file. Another way to bootstrap and license VM-Series is using VM Auth Key. This approach requires preparing license (auth code) in file stored in S3 bucket or putting it in authcodes
option. More information can be found in document describing how to choose a bootstrap method. Please note, that other bootstrapping methods may requires additional changes in example code (e.g. adding options vm-auth-key
, authcodes
) and/or creating additional resources (e.g. S3 buckets).
Usage
- Copy
example.tfvars
intoterraform.tfvars
- Review
terraform.tfvars
file, especially with lines commented by# TODO: update here
- Initialize Terraform:
terraform init
- Prepare plan:
terraform plan
- Deploy infrastructure:
terraform apply -auto-approve
- Destroy infrastructure if needed:
terraform destroy -auto-approve
Reference
Requirements
Name | Version |
---|---|
terraform | >= 1.0.0, < 2.0.0 |
aws | ~> 5.17 |
local | ~> 2.4.0 |
Providers
Name | Version |
---|---|
aws | ~> 5.17 |
Modules
Name | Source | Version |
---|---|---|
app_lb | ../../modules/nlb | n/a |
gwlb | ../../modules/gwlb | n/a |
gwlbe_endpoint | ../../modules/gwlb_endpoint_set | n/a |
natgw_set | ../../modules/nat_gateway_set | n/a |
public_alb | ../../modules/alb | n/a |
public_nlb | ../../modules/nlb | n/a |
subnet_sets | ../../modules/subnet_set | n/a |
transit_gateway | ../../modules/transit_gateway | n/a |
transit_gateway_attachment | ../../modules/transit_gateway_attachment | n/a |
vmseries | ../../modules/vmseries | n/a |
vpc | ../../modules/vpc | n/a |
vpc_routes | ../../modules/vpc_route | n/a |
Resources
Name | Type |
---|---|
aws_ec2_transit_gateway_route.from_security_to_panorama | resource |
aws_ec2_transit_gateway_route.from_spokes_to_security | resource |
aws_iam_instance_profile.spoke_vm_iam_instance_profile | resource |
aws_iam_instance_profile.vm_series_iam_instance_profile | resource |
aws_iam_role.spoke_vm_ec2_iam_role | resource |
aws_iam_role.vm_series_ec2_iam_role | resource |
aws_iam_role_policy.vm_series_ec2_iam_policy | resource |
aws_instance.spoke_vms | resource |
aws_lb_target_group_attachment.this | resource |
aws_ami.this | data source |
aws_caller_identity.this | data source |
aws_ebs_default_kms_key.current | data source |
aws_kms_alias.current_arn | data source |
aws_partition.this | data source |
Inputs
Name | Description | Type | Default | Required |
---|---|---|---|---|
global_tags | Global tags configured for all provisioned resources | any | n/a | yes |
gwlb_endpoints | A map defining GWLB endpoints. Following properties are available: - name : name of the GWLB endpoint- gwlb : key of GWLB- vpc : key of VPC- vpc_subnet : key of the VPC and subnet connected by '-' character- act_as_next_hop : set to true if endpoint is part of an IGW route table e.g. for inbound traffic- to_vpc_subnets : subnets to which traffic from IGW is routed to the GWLB endpointExample:
|
| {} | no |
gwlbs | A map defining Gateway Load Balancers. Following properties are available: - name : name of the GWLB- vpc_subnet : key of the VPC and subnet connected by '-' characterExample:
|
| {} | no |
name_prefix | Prefix used in names for the resources (VPCs, EC2 instances, autoscaling groups etc.) | string | n/a | yes |
natgws | A map defining NAT Gateways. Following properties are available: - name : name of NAT Gateway- vpc_subnet : key of the VPC and subnet connected by '-' characterExample:
|
| {} | no |
panorama_attachment | A object defining TGW attachment and CIDR for Panorama. Following properties are available: - transit_gateway_attachment_id : ID of attachment for Panorama- vpc_cidr : CIDR of the VPC, where Panorama is deployedExample:
|
| null | no |
region | AWS region used to deploy whole infrastructure | string | n/a | yes |
spoke_lbs | A map defining Network Load Balancers deployed in spoke VPCs. Following properties are available: - vpc_subnet : key of the VPC and subnet connected by '-' character- vms : keys of spoke VMsExample:
|
| {} | no |
spoke_vms | A map defining VMs in spoke VPCs. Following properties are available: - az : name of the Availability Zone- vpc : name of the VPC (needs to be one of the keys in map vpcs )- vpc_subnet : key of the VPC and subnet connected by '-' character- security_group : security group assigned to ENI used by VM- type : EC2 type VMExample:
|
| {} | no |
ssh_key_name | Name of the SSH key pair existing in AWS key pairs and used to authenticate to VM-Series or test boxes | string | n/a | yes |
tgw | A object defining Transit Gateway. Following properties are available: - create : set to false, if existing TGW needs to be reused- id : id of existing TGW or null- name : name of TGW to create or use- asn : ASN number- route_tables : map of route tables- attachments : map of TGW attachmentsExample:
|
| null | no |
vmseries | A map defining VM-Series instances Following properties are available: - instances : map of VM-Series instances- bootstrap_options : VM-Seriess bootstrap options used to connect to Panorama- panos_version : PAN-OS version used for VM-Series- ebs_kms_id : alias for AWS KMS used for EBS encryption in VM-Series- vpc : key of VPC- gwlb : key of GWLB- subinterfaces : configuration of network subinterfaces used to map with GWLB endpoints- system_services : map of system services- application_lb : ALB placed in front of the Firewalls' public interfaces- network_lb : NLB placed in front of the Firewalls' public interfacesExample:
|
| {} | no |
vpcs | A map defining VPCs with security groups and subnets. Following properties are available: - name : VPC name- cidr : CIDR for VPC- security_groups : map of security groups- subnets : map of subnets with properties:- az : availability zone- set : internal identifier referenced by main.tf- routes : map of routes with properties:- vpc_subnet - built from key of VPCs concatenate with - and key of subnet in format: VPCKEY-SUBNETKEY - next_hop_key - must match keys use to create TGW attachment, IGW, GWLB endpoint or other resources- next_hop_type - internet_gateway, nat_gateway, transit_gateway_attachment or gwlbe_endpointExample:
|
| {} | no |
Outputs
Name | Description |
---|---|
app_inspected_dns_name | FQDN of App Internal Load Balancer. Can be used in VM-Series configuration to balance traffic between the application instances. |
public_alb_dns_name | FQDN of VM-Series External Application Load Balancer used in centralized design. |
public_nlb_dns_name | FQDN of VM-Series External Network Load Balancer used in centralized design. |
vmseries_public_ips | Map of public IPs created within vmseries module instances. |