Re:TLS Termination for Network Load Balancers
by e1g on Thursday January 24, 2019 @07:18PM
(#18994392)
AWS LB does not validate backend certificates, so you can put a self-signed cert on the instance. Heck, even if the cert expires it will still work, and make LB<->EC2 connection technically encrypted. Yay compliance.
[ Parent
| on HN ]
Re:TLS Termination for Network Load Balancers
by xyzzy123 on Thursday January 24, 2019 @07:54PM
(#18994556)
You can actually turn this on (for classic ELBs), but it locks to a specific cert (rather than a CA). So yeah no one cares about expiry but the backend does have to present that cert. The thing to look for is "Enable backend authentication".
I would question whether this is a problem though; basically if someone is in a position to MITM traffic in your AWS VPC this would indicate a compromise of AWS at a fundamental level (or loss of your AWS control plane).
Re:TLS Termination for Network Load Balancers
by e1g on Thursday January 24, 2019 @09:12PM
(#18994977)
AWS does not encrypt internal traffic, including traffic between Availability Zones. AZ's are spread over several datacenters, so your VPC traffic (RDS/microservicers etc) travels unencrypted across multiple physical locations. I consider AWS network assurances sufficient so it's not a problem for our standard threat model, but the auditors got their checkboxes to tick...
Re:TLS Termination for Network Load Balancers
by ec109685 on Friday January 25, 2019 @05:07AM
(#18996844)
Do you have a citation that data travels among data centers in aws unencrypted? At least between regions, it is encrypted:
https://aws.amazon.com/blogs/aws/new-almost-inter-region-vpc...
Re:TLS Termination for Network Load Balancers
by illumin8 on Thursday January 24, 2019 @11:23PM
(#18995548)
In case this sounds bad for security reasons (using self-signed certs) keep in mind that the VPC network does not allow clients to spoof IP addresses or receive traffic destined for any other MAC/IP pair. So, there is no need to validate the authenticity of a host on the network because it has already been validated by the VPC software defined network, and spoofing MAC/IP, or ARP poisoning, or any of the other traditional physical network layer attacks just don't work.