DEPLOY - AWS Gateway Load Balancer (GWLB) with PAN (Palo Alto Network) Firewalls (NGFW)

Aviatrix Transit FireNet without AWS GWLB is by far the best option to deploy, insert and manage NGFW (Palo Alto, Checkpoint, Fortinet, etc.) for Cloud and Multi-Cloud enterprise networks. There are some organizations opting for Gateway Loadbalancer (#GWLB) to front end the 3rd party NGFW for service insertion and chaining. GWLB sits in front of NGFW EC2 instances for an active/active deployment but only in AWS. https://aws.amazon.com/elasticloadbal... If you are not using Aviatrix and only follow AWS or NGFW vendor documentation, to design and deploy NGFW using GWLB, you will find it an extremely complicated, manual, and error-prone process. As an example, try to follow this documentation https://docs.paloaltonetworks.com/vm-... Aviatrix makes is extremely simple and automated so you don't have to deal with the VPC routing table, GWLB end-point, and symmetric complexities. This video shows the design and deployment of #VM-Series using #Aviatrix simple, easy and quick policy-based approach. 0:00 Introduction 2:53 Aviatrix - Foundation of Your Cloud Networking and Security 6:45 GW Load Balancer (GWLB) Reference Design - Egress 7:59 AWS Transit FireNet without Gateway Load Balancer 8:47 AWS Transit FireNet with Gateway Load Balancer - Collapsed 12:42 AWS Transit FireNet with Gateway Load Balancer - Dual FireNet 14:34 AWS Transit Firenet with Gateway Load Balancer - Ingress VPC 17:41 Deploy an Aviatrix Transit Architecture - Deploy tool start up 18:15 Deploy an Aviatrix Transit Architecture - Use the Deploy tool 25:59 Enable the Aviatrix Transit Gateways for Firenet - AWS Console 30:41 Enable Egress Inspection 35:53 Configure the Palo Alto Firewall instances - Basic Configuration 39:08 Testing: Internet Egress 40:13 Verification - CoPilot, Transit 41:02 Verification - CoPilot, Internet Egress 43:29 Verification - Palo Alto logs