Reference Architecture with Terraform: VM-Series in AWS, Isolated 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:
- an isolated design, which secures outbound and inbound traffic flows using AWS Gateway Load Balancer (GWLB). Application resources are segmented across multiple VPCs that distribute traffic to the dedicated VPC for security services where the VM-Series are deployed.
Detailed Architecture and Design
Isolated Design
The Isolated Design model centralizes the security instances in a dedicated security VPC, while providing one or more isolated VPCs inbound and outbound security services. This design leverages a VPC dedicated to security. In the security VPC, you deploy the VM-Series firewalls, in separate availability zones, and a GWLB to distribute traffic to the firewalls. This design uses overlay routing for outbound security on the VM-Series firewalls. Outbound traffic from instances in the isolated VPCs uses the PrivateLink connections from GWLB endpoints in the applications. VPCs to the GWLB in the security VPC to egress the AWS environment through the VM-Series firewalls.
Inbound traffic originates outside the VPC and is destined to applications or services hosted within your VPCs, such as web servers. This design uses the GWLB and VM-Series firewalls in the security VPC, with GWLB endpoints in the application VPCs for the transparent inspection of inbound traffic.
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 |
Providers
Name | Version |
---|---|
aws | ~> 5.17 |
Modules
Name | Source | Version |
---|---|---|
gwlb | ../../modules/gwlb | n/a |
gwlbe_endpoint | ../../modules/gwlb_endpoint_set | n/a |
public_alb | ../../modules/alb | n/a |
public_nlb | ../../modules/nlb | n/a |
subnet_sets | ../../modules/subnet_set | n/a |
vmseries | ../../modules/vmseries | n/a |
vpc | ../../modules/vpc | n/a |
vpc_routes | ../../modules/vpc_route | n/a |
Resources
Name | Type |
---|---|
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_vpc_peering_connection.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 |
panorama_connection | A object defining VPC peering and CIDR for Panorama. Following properties are available: - security_vpc : key of the security VPC- peering_vpc_id : ID of the VPC 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_albs | A map defining Application Load Balancers deployed in spoke VPCs. Following properties are available: - rules : Rules defining the method of traffic balancing- vms : Instances to be the target group for ALB- vpc : The VPC in which the load balancer is to be run- vpc_subnet : The subnets in which the Load Balancer is to be run- security_gropus : Security Groups to be associated with the ALB
|
| n/a | yes |
spoke_nlbs | 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 |
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- nacls : map of network ACLs- security_groups : map of security groups- subnets : map of subnets with properties:- az : availability zone- set : internal identifier referenced by main.tf- nacl : key of NACL (can be null)- 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 |
---|---|
application_load_balancers | FQDNs of Application Load Balancers |
network_load_balancers | FQDNs of Network Load Balancers. |
vmseries_public_ips | Map of public IPs created within vmseries module instances. |