It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

Amazon AWS Deployment

  • Last updated on

The NextGen Firewall F-Series can secure your AWS resources and connect them to your on-premises network. The firewall VM replaces both the NAT gateway Instances and the AWS VPN gateway with one single product. Using a firewall instead of the built-in security features of the AWS VPC allows for traffic visibility and more granular security policies, as well as central management using a NextGen Control Center. The Control Center can be deployed either in the AWS, Azure public cloud, or on-premises.


Deploy via the Web Portal

The Barracuda NextGen Firewall F in AWS secures and connects the services running in your AWS virtual private cloud (VPC). The firewall monitors and secures all traffic between subnets to and from the Internet. It also connects your cloud resources either to your on-premises networks with site-to-site VPN, or to your remote users with client-to-site VPN and SSL VPN.

For more information, see How to Deploy an F-Series Firewall in AWS via Web Portal.

Deploy via CloudFormation Template

CloudFormation templates are JSON files that include the definition of all your cloud resources. By launching the template via CloudFormation, you can automate your AWS deployments and create consistent environments for multiple purposes such as a deployment for production, cold standby, testing developing etc...

For more information, see How to Deploy an F-Series Firewall in AWS via CloudFormation Template.

Deploy two F-Series Firewalls in a High Availability Cluster in AWS

To avoid downtime when the primary firewall is unavailable due to maintenance or hardware failure, configure a high availability cluster. Incoming traffic is directed to the active firewall via Route 53 or the TCP-only AWS load balancer. The firewall then applies your policies and forwards the traffic accordingly to the backend. The AWS route table is monitored by the firewall. Routes where the destination is set to the firewall are updated by the active firewall after a failover event to ensure that the active firewall is always used as the gateway.

For more information, see High Availability in AWS.

Last updated on