Multi-Node setup and Session persistence

[nfederico360insights]

My team is working on deploying Qlik on an AWS multi-node solution, for which we require that proxies V1 and V2 Protocols as well as a "True Source ID". 

Now we have a challenge with the management of the (ticket) sessions across the nodes: 

Can Qlik’s Load Balancer manage sessions across the multinode solutions without an external (AWS) Load Balancer?

What are the pros/cons of enabling or disabling the AWS Load Balancer? 

Would it be advisable to move to a authentication method that doesn't use Certs? 
What is the best solution given the above details? 

Thank you, 
Nico

[Alexis_Touet · Accepted solution]

Hi @nfederico360insights 

Yes, Qlik Sense can manage sessions natively via its QPS (Qlik Proxy Service).

Adding a Network Load Balancer ( ALB in your case) is generally recommended to allow your environment to be highly available (HA).

Typically a NLB would redirect sessions to at least 2 QPS, so if one QPS is down  it should still send users to other QPS. 

Resources that can help:
https://community.qlik.com/t5/Knowledge/How-to-configure-Network-Loadbalancer-NLB-with-Qlik-Sense/ta...
https://community.qlik.com/t5/Knowledge/Network-Load-Balancer-NLB-Requirements-for-Qlik-Sense-Enterp...

Hope this helps

[nfederico360insights]

Thank you @Alexis_Touet , 
Will circle back with the team and let you know if there are further details thy need. 
All the best, 

Nico