News for hackers. Stuff that matters.
Re:TLS Termination for Network Load Balancers by luhn on Thursday January 24, 2019 @04:53PM (#18993402)
They don't mention it in the article, but TLS comes at an additional cost. Same price per hour and per LCU, but an LCU gets you less with TLS. Standard LCU:

- 800 new non-TLS connections or flows per second.

- 100,000 active non-TLS connections or flows (sampled per minute).

- 1 GB per hour for EC2 instances, containers and IP addresses as targets.

TLS LCU:

- 50 new TLS connections or flows per second.

- 3,000 active TLS connections or flows (sampled per minute).

- 1 GB per hour for EC2 instances, containers and IP addresses as targets.

https://aws.amazon.com/elasticloadbalancing/pricing/

Re:TLS Termination for Network Load Balancers by NotAnEconomist on Thursday January 24, 2019 @06:49PM (#18994223)
Just because I found it interesting:

- 16x cost for new connections or flows per second.

- 32x cost for active connections or flows.

- 1x cost for traffic carried in GB per hour, which you'd expect.

Re:TLS Termination for Network Load Balancers by buzzdenver on Friday January 25, 2019 @08:06AM (#18997553)
That's still double the connections compared to having an ALB which only gives you 25/s/LCU. Plus an NLB is 0.6 cents/hour/LCU in us-east-1 vs 0.8 for an ALB.