Building network automation solutions

9 module online course

Start now!

Public Cloud Networking Security is Different

If you’re running a typical (somewhat outdated) enterprise data center, you’re using tons of VLANs and firewalls, use VLANs as security zones, and push inter-VLAN traffic through firewalls for inspection. Security vendors love that approach - when inspecting traffic they can add no value to (like database- or backup sessions), the firewalls quickly become choke points that have to be upgraded.

Networking security in public clouds is totally different - you’re supposed to use stateful packet filters (usually called security groups) in front of every VM and use dynamically-updated VM groups instead of IP addresses or subnets to specify traffic source and destination. Inserting your own VM-based firewall into the forwarding path is pretty hard in AWS and Azure… and might become expensive as public cloud providers happily charge you for every VM resource you use.

AWS recently launched Ingress VPC Routing feature that makes it easier to inspect traffic coming from the outside of your cloud environment, but the setup is still interestingly complex.

Is it safe to replace traditional firewalls with packet filters? Should you bring your own firewall appliance or use edge firewalls provided by major public cloud providers? Should you combine edge firewall with intra-cloud security groups? How hard would it be to insert your own firewall VM into the forwarding path, and is it worth it? Can you do it for intra-cloud traffic, or does it work only for external traffic? How could you implement a firewall instance failover? We’ll address all these questions in our Networking in Public Cloud Deployments online course. All you have to do is to register.

4 comments:

  1. The AWS transit gateway service insertion pattern is relatively easy to implement. But you need a firewall that does BGP correctly. Does the the course cover this approach?
    Replies
    1. Most of what you're talking about is (probably) already covered in the AWS Networking materials https://my.ipspace.net/bin/list?id=AWSNET#EXTERNAL.

      Also, there's a huge difference between intra-VPC service insertion, inter-VPC service insertion and north-south (Internet-to-VPC) service insertion.

      Finally, FWIW: BGP on VM appliance is useful only when you're running IPsec tunnels with spoke VPCs. Slow and expensive.
  2. HUB and Spoke topology with VM in the hub.
    For HA use BGP on HUB. In the spoke use cloud VPN with BGP IPSEC.
    This topic is well covered by the networkdesign arena:

    AWS Transit Gateway and Multi-VPC Design Options, for Hybrid Cloud Architecture
    http://www.netdesignarena.com/index.php/2019/01/07/aws-transit-gateway-and-multi-vpc-design-options-for-hybrid-cloud-architecture/


    Also FYI the blog page is not allowing me to publish with IPSPACE account
    Replies
    1. Thanks for the link. Unless you want to use BGP for dynamic routing there are much simpler options than IPsec VPN tunnels between hub appliance and spoke VPCs, using either transit gateway in hub-and-spoke configuration, or simple VPC peering.

      As for using ipSpace account for comments - that's been on my to-do list for years. Unfortunately there's always something more urgent or important to do, like creating new content... but eventually I'll get there, I promise!
Add comment
Sidebar