The Load Balancer service provides automated traffic distribution from one entry point to multiple servers. Loadbalancing ensures high availability and scalability for applications, even under heavy traffic. It is commonly used to improve website, application, database, and service performance and reliability. Read more

The product is present in the following locations:

• dc-fbg1 (our DC in Falkenberg, Sweden)
• dc-sto1 (our DC in Stockholm, Sweden)

Customer self-service	Yes, managed in GleSYS Cloud
Protocol(s)	TCP, HTTP
Processing of personal data	Transfer

The Load Balancer establishes connections with its backend servers using the protocol and port specified, allowing it to utilize the protocol's capabilities for traffic management.

• HTTP protocol (typically port 80 or port 443 if also using TLS): The Load Balancer forwards HTTP connections to backend servers. Traffic will be forwarded without encryption.
• TCP protocol: The Load Balancer connects to backend servers using TCP and forwards TCP payloads without modification (other than encryption/decryption, where configured).

Sticky sessions	Yes
X-Forwarded-For header	Enabled by default
X-Forwarded-Proto header	Enabled by default
TLS/SSL certificates	Yes, you can add a certificate to the frontend (no integrated feature for auto-renewing Let's Encrypt certifications).

Proxy protocol support

No

The Load Balancer service provides three different types of timeout settings:

• 1. Timeout Client [set to 30 seconds by default]: The timeout client setting determines the maximum duration of client inactivity allowed when connected to the server.
• 2. Timeout Connect [set to 4 seconds by default]: The timeout connect is like a grace period that sets the maximum time for a client to connect to a server.
• 3. Timeout Response [set to 30 seconds by default]: The timeout response, also known as "timeout server," sets the maximum time to receive HTTP response headers from the backend server (after it receives the complete client request).

Each load balancer has the following configuration limits:

• Concurrent sessions: The maximum number of connections that the Load Balancer will accept are, by default, set to 1,000. Maximum value: 200,000.
• One IPv4 address and one IPv6 address.
• No geo-redundancy, private network, Server Name Identification (SNI) or proxy protocol support.

Infrastructure platform	GleSYS
Client setup	Customer
Client troubleshooting	Customer