If your workloads are on the cloud, you need a security solution built specifically to meet cloud requirements. A firewall designed to secure your “perimeter” doesn’t do the trick. You need a cloud generation firewall that meets three key requirements: it supports specific cloud security use cases; it supports automated, packaged deployment best practices; and it provides a commercial model that takes advantage of superior cloud economics.

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
December 5, 2017 | 10:00 AM PT
Help Secure Your Cloud
Deployment. Learn How with
Amazon Web Services, Inc.
(“AWS”) and Barracuda.
© 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Today’s Presenters
Nick Matthews, Solutions Architect, Amazon Web
Services
Tim Jefferson, VP of Public Cloud, Barracuda
Max Longin, Founder, Club Automation

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Today’s Agenda
• Firewalls on Amazon Web Services (AWS)
• How Club Automation uses Cloud Generation Firewalls
• Cloud Generation Firewalls for AWS
• Q&A/Discussion

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Learning Objectives
• The requirements of network security on the cloud
• What makes a firewall “Cloud Generation"?
• How one AWS customer is leveraging Cloud Generation
technology from Barracuda to protect AWS workloads

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Network Security on AWS

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Automating
logging and
monitoring
Simplifying
resource
access
Making it easy
to encrypt
properly
Enforcing
strong
authentication
AWS Can Be More Secure Than Your
Existing Environment
How?

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
“Anti-Patterns” for Firewalls - Before
Elastic Load
Balancing
Web
Instances
Subnets and clustering are
limited to a single Availability
Zone
Firewalls don’t auto-
scale to meet demand,
becoming a bottleneck
Firewalls may not support a
DNS name with NAT or in
security policies, sending all
traffic to a single IP address of
the ELB
Auto-
Scaling
Outbound routing from
the instances is
statically set to a single
firewall
Virtual IP Addresses (VIPs)
operate differently on AWS, so
the firewall must support a
version of high availability
using VPC API calls
Firewall Pair
Route
Table

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Design Considerations
Direction of
Traffic
East-West
Security Policy
Availability
Requirements
Bandwidth VPC Scale
Application and
Protocols

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points
Encryption Insertion Pain Licensing
Choke Points Static Architectures High Availability

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points
Encryption Insertion Pain Licensing
Choke Points Static Architectures High Availability

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
You Can Make Firewalls Work
Requirements for
secure
environments
Requirements to
move quickly and
experiment

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cloud Generation
Firewalls on AWS

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points
Encryption Insertion Pain Licensing
Choke Points Static Architectures High Availability

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points
Insertion Pain
Choke Points High Availability

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling
API integration

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling
API integration
Rapid deployment

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling
API integration
Rapid deployment
High availability

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling
API integration
Rapid deployment
High availability
Network traffic
optimization

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling
API integration
Rapid deployment
High availability
Network traffic
optimization
Well-architected

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Deployment Best
Practices
Insertion PainChoke Points High Availability
Auto Scaling
API integration
Rapid deployment
High availability
Network traffic
optimization
Well-architected
APN Competency certified

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points
Licensing

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  License-Less Billing
Licensing

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  License-Less Billing
Licensing
No multi-year license costs

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  License-Less Billing
Licensing
No multi-year license costs
True utility-based pricing

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  License-Less Billing
Licensing
No multi-year license costs
True utility-based pricing
Pay for security metered on throughput

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points
Encryption
Static Architectures

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Support for Cloud Use
Cases
Encryption Static Architectures

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Support for Cloud Use
Cases
Encryption Static Architectures
Remote connectivity

31. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Support for Cloud Use
Cases
Encryption Static Architectures
Remote connectivity
Highly-distributed, fully-meshed networks

32. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Firewall Friction Points  Support for Cloud Use
Cases
Encryption Static Architectures
Remote connectivity
Highly-distributed, fully-meshed networks
Workload migration

33. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cloud Generation Firewalls are engineered to
support cloud deployment models, utility-based
billing, and cloud use cases.
They are the right tool for the job.

34. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How Club Automation uses
Barracuda Firewalls on AWS
Max Longin, Founder, Club Automation

35. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Who are we?
• From an upstart to a recognized player in the health club
ERP software industry
• Our goal: To revolutionize the entire industry with a SaaS solution
that manages all parts of a health club’s business
• Massive growth in the last year
• 300% YoY growth in sales in 2017
• We chose to move our SaaS solution to the cloud in order to
manage explosive growth

36. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
We ran into scaling challenges

37. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Our move to AWS
• AWS addressed performance
challenges
• Our next challenge: Securing our
VPC
• We chose Barracuda NextGen
Firewall, a Cloud Generation
Firewall, to protect each region in
our AWS deployment

38. How we use
Barracuda
NGF
• Multi-region
support

39. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Advantages of Barracuda NGF
Metered Billing
Spinning up new VPCs for:
• Continuous integration
• QA testing
• Mobile app dev
environment

40. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Q & A

41. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Next steps and further information
90-day free trial:
• Go to https://aws.amazon.com/marketplace/
• Search for “Barracuda”
Learn more about Barracuda cloud generation firewalls on AWS:
• https://www.barracuda.com/cgfonaws
Try AWS for free:
• https://aws.amazon.com/

42. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Thank you!