Re:Networking on AWS (2018)
by javadocmd on Wednesday January 16, 2019 @07:48PM
(#18927294)
I like using ACLs for my coarse-grained "this subnet is allowed to talk to this subnet" rules, and security groups for everything finer-grained. Maybe I'm over-cautious, but I don't want one rogue security group opening up a tunnel to sensitive subnets.
[ Parent
| on HN ]
Yes, this is one of the best reasons to use network ACLs. (You can also achieve this with routes)
I think the idea is that separate teams with different responsibilities can manage the two different layers. Your app team may manage the security groups but the security team manages network ACLs which limit what can go into or come out of a subnet.
Re:Networking on AWS (2018)
by AmericanChopper on Wednesday January 16, 2019 @07:56PM
(#18927331)
That’s a reasonable design pattern. For my usecase we have those segmentations in place at the VPC level, so ACLs wouldn’t add anything for us.