Optional
failoverPort to be used by the backend when forwarding traffic to backend servers.
Load balancing algorithm to be used when determining which backend server to forward new traffic to.
Protocol to be used by the backend when forwarding traffic to backend servers.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
Optional
ignoreDefines whether the server certificate verification should be ignored.
Load Balancer ID.
Optional
maxMaximum number of connections allowed per backend server.
Optional
maxNumber of retries when a backend server connection failed.
Optional
name?: stringName for the backend.
Optional
onAction to take when a backend server is marked as down.
Optional
proxyProtocol to use between the Load Balancer and backend servers. Allows the backend servers to be informed of the client's real IP address. The PROXY protocol must be supported by the backend servers' software.
Optional
redispatchWhether to use another backend server on each attempt.
Optional
region?: RegionRegion to target. If none is passed will use default region from the config.
Optional
sendList of backend server IP addresses (IPv4 or IPv6) the backend should forward traffic to.
Optional
sslDefines whether to enable SSL bridging between the Load Balancer and backend servers.
Defines whether to activate sticky sessions (binding a particular session to a particular backend server) and the method to use if so. None disables sticky sessions. Cookie-based uses an HTTP cookie TO stick a session to a backend server. Table-based uses the source (client) IP address to stick a session to a backend server.
Cookie name for cookie-based sticky sessions.
Optional
timeoutMaximum allowed time for establishing a connection to a backend server.
Optional
timeoutMaximum time for a request to be left pending in queue when
max_connections
is reached.
Optional
timeoutMaximum allowed time for a backend server to process a request.
Optional
timeoutMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout).
Scaleway Object Storage bucket website to be served as failover if all backend servers are down, e.g. failover-website.s3-website.fr-par.scw.cloud.