Optional
createdOptional
failoverScaleway 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.
Port used by the backend when forwarding traffic to backend servers.
Load balancing algorithm to use when determining which backend server to forward new traffic to.
Protocol used by the backend when forwarding traffic to backend servers.
Optional
healthObject defining the health check to be carried out by the backend when checking the status and health of backend servers.
Backend ID.
Optional
ignoreDefines whether the server certificate verification should be ignored.
Optional
lbLoad Balancer the backend is attached to.
Optional
maxMaximum number of connections allowed per backend server.
Optional
maxNumber of retries when a backend server connection failed.
Name of the backend.
Action to take when a backend server is marked as down.
List of IP addresses of backend servers attached to this backend.
Protocol 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
sendOptional
sslDefines whether to enable SSL bridging between the Load Balancer and backend servers.
Defines whether sticky sessions (binding a particular session to a particular backend server) are activated 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).
Optional
updatedDate at which the backend was updated.
Date at which the backend was created.