networking - TCP Load Balancer In Front of TLS/SSL Endpoints -
last week playing load balancer tls-enabled endpoints (share same certificate) , surprised possible have tpc load balancer in place in front of ssl endpoint. having configured possible communicate tcp load balancer configured support tls/ssl. so, ensure such network configuration working solution:
- tls/ssl session , handshake workflow stateless, meaning possible start handshake primary server , end mirror. true?
- are there hidden dangers must aware of?
- if previous statements true, reason to tls/ssl work on load balancer itself?
p.s. reason not tls/ssl work on load balancer need balance multiple proprietary endpoint supports ssl/tls.
tls/ssl session , handshake workflow stateless, meaning possible start handshake primary server , end mirror. true?
no. suspect load balancer using tcp keep-alive handshake completing on same server every time.
are there hidden dangers must aware of?
you may incurring significant performance penalty. https has "session keys" are, default, unique server. if aren't able sticky sessions load balancer, full handshake every time client moves 1 server other.
you have session tickets won't work between servers, session resumption not work either, , fall full handshake. servers support configuring common session ticket key, nginx.
if previous statements true, reason to tls/ssl work on load balancer itself?
well, aren't entirely true. there other benefits though. main 1 being load balancer can more intelligent since can see plaintext of session. example might examining request's cookies determine server send request to. common need blue/green deployments.
Comments
Post a Comment