The Load Balancer backend object. It represents a set of backend servers that the frontend forwards requests to using the specified configuration (port, protocol, proxy protocol etc). You can create multiple backends for each of your Load Balancers. Use the backends endpoint to create backends, list, manage and update them and their healthchecks / backend servers, and delete them as required
Get a backend of a given Load Balancer
Get the full details of a given backend, specified by its backend ID. The response contains the backend's full configuration parameters including protocol, port and forwarding algorithm.
path Parameters
zoneThe zone you want to target
backend_idBackend ID.
Get a backend of a given Load Balancer › Responses
idBackend ID.
nameName of the backend.
forward_protocolProtocol used by the backend when forwarding traffic to backend servers.
forward_portPort used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to use when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
poolList of IP addresses of backend servers attached to this backend.
Load Balancer the backend is attached to.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
created_atDate at which the backend was created. (RFC 3339 format)
updated_atDate at which the backend was updated. (RFC 3339 format)
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
Update a backend of a given Load Balancer
Update a backend of a given Load Balancer, specified by its backend ID. Note that the request type is PUT and not PATCH. You must set all parameters.
path Parameters
zoneThe zone you want to target
backend_idBackend ID.
Update a backend of a given Load Balancer › Request Body
nameBackend name.
forward_protocolProtocol to be used by the backend when forwarding traffic to backend servers.
forward_portPort to be used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to be used when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
Update a backend of a given Load Balancer › Responses
idBackend ID.
nameName of the backend.
forward_protocolProtocol used by the backend when forwarding traffic to backend servers.
forward_portPort used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to use when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
poolList of IP addresses of backend servers attached to this backend.
Load Balancer the backend is attached to.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
created_atDate at which the backend was created. (RFC 3339 format)
updated_atDate at which the backend was updated. (RFC 3339 format)
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
Delete a backend of a given Load Balancer
Delete a backend of a given Load Balancer, specified by its backend ID. This action is irreversible and cannot be undone.
path Parameters
zoneThe zone you want to target
backend_idID of the backend to delete.
Delete a backend of a given Load Balancer › Responses
Update a health check for a given backend
Update the configuration of the health check performed by a given backend to verify the health of its backend servers, identified by its backend ID. Note that the request type is PUT and not PATCH. You must set all parameters.
path Parameters
zoneThe zone you want to target
backend_idBackend ID.
Update a health check for a given backend › Request Body
portPort to use for the backend server health check.
check_delayTime to wait between two consecutive health checks. (in milliseconds)
check_timeoutMaximum time a backend server has to reply to the health check. (in milliseconds)
check_max_retriesNumber of consecutive unsuccessful health checks after which the server will be considered dead.
check_send_proxyDefines whether proxy protocol should be activated for the health check.
tcp_configObject to configure a basic TCP health check.
Object to configure a MySQL health check. The check requires MySQL >=3.22 or <9.0. For older or newer versions, use a TCP health check.
Object to configure a PostgreSQL health check.
ldap_configObject to configure an LDAP health check. The response is analyzed to find the LDAPv3 response message.
redis_configObject to configure a Redis health check. The response is analyzed to find the +PONG response message.
Object to configure an HTTP health check.
Object to configure an HTTPS health check.
transient_check_delayTime to wait between two consecutive health checks when a backend server is in a transient state (going UP or DOWN). (in seconds)
Update a health check for a given backend › Responses
portPort to use for the backend server health check.
check_delayTime to wait between two consecutive health checks. (in milliseconds)
check_timeoutMaximum time a backend server has to reply to the health check. (in milliseconds)
check_max_retriesNumber of consecutive unsuccessful health checks after which the server will be considered dead.
tcp_configObject to configure a basic TCP health check.
Object to configure a MySQL health check. The check requires MySQL >=3.22 or <9.0. For older or newer versions, use a TCP health check.
Object to configure a PostgreSQL health check.
ldap_configObject to configure an LDAP health check. The response is analyzed to find the LDAPv3 response message.
redis_configObject to configure a Redis health check. The response is analyzed to find the +PONG response message.
Object to configure an HTTP health check.
Object to configure an HTTPS health check.
check_send_proxyDefines whether proxy protocol should be activated for the health check.
transient_check_delayTime to wait between two consecutive health checks when a backend server is in a transient state (going UP or DOWN). (in seconds)
Define all backend servers for a given backend
For a given backend specified by its backend ID, define the set of backend servers (identified by their IP addresses) that it should forward traffic to. Any existing backend servers configured for this backend will be removed.
path Parameters
zoneThe zone you want to target
backend_idBackend ID.
Define all backend servers for a given backend › Request Body
server_ipList of IP addresses for backend servers. Any other existing backend servers will be removed.
Define all backend servers for a given backend › Responses
idBackend ID.
nameName of the backend.
forward_protocolProtocol used by the backend when forwarding traffic to backend servers.
forward_portPort used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to use when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
poolList of IP addresses of backend servers attached to this backend.
Load Balancer the backend is attached to.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
created_atDate at which the backend was created. (RFC 3339 format)
updated_atDate at which the backend was updated. (RFC 3339 format)
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
Add a set of backend servers to a given backend
For a given backend specified by its backend ID, add a set of backend servers (identified by their IP addresses) it should forward traffic to. These will be appended to any existing set of backend servers for this backend.
path Parameters
zoneThe zone you want to target
backend_idBackend ID.
Add a set of backend servers to a given backend › Request Body
server_ipList of IP addresses to add to backend servers.
Add a set of backend servers to a given backend › Responses
idBackend ID.
nameName of the backend.
forward_protocolProtocol used by the backend when forwarding traffic to backend servers.
forward_portPort used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to use when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
poolList of IP addresses of backend servers attached to this backend.
Load Balancer the backend is attached to.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
created_atDate at which the backend was created. (RFC 3339 format)
updated_atDate at which the backend was updated. (RFC 3339 format)
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
Remove a set of servers for a given backend
For a given backend specified by its backend ID, remove the specified backend servers (identified by their IP addresses) so that it no longer forwards traffic to them.
path Parameters
zoneThe zone you want to target
backend_idBackend ID.
Remove a set of servers for a given backend › Request Body
server_ipList of IP addresses to remove from backend servers.
Remove a set of servers for a given backend › Responses
idBackend ID.
nameName of the backend.
forward_protocolProtocol used by the backend when forwarding traffic to backend servers.
forward_portPort used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to use when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
poolList of IP addresses of backend servers attached to this backend.
Load Balancer the backend is attached to.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
created_atDate at which the backend was created. (RFC 3339 format)
updated_atDate at which the backend was updated. (RFC 3339 format)
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
List backend server statistics
List information about your backend servers, including their state and the result of their last health check.
path Parameters
zoneThe zone you want to target
lb_idLoad Balancer ID.
query Parameters
pageThe page number to return, from the paginated results.
page_sizeNumber of items to return.
backend_idID of the backend.
List backend server statistics › Responses
List of objects containing backend server statistics.
total_countThe total number of objects.
List the backends of a given Load Balancer
List all the backends of a Load Balancer, specified by its Load Balancer ID. By default, results are returned in ascending order by the creation date of each backend. The response is an array of backend objects, containing full details of each one including their configuration parameters such as protocol, port and forwarding algorithm.
path Parameters
zoneThe zone you want to target
lb_idLoad Balancer ID.
query Parameters
nameName of the backend to filter for.
order_bySort order of backends in the response.
pageThe page number to return, from the paginated results.
page_sizeNumber of backends to return.
List the backends of a given Load Balancer › Responses
List of backend objects of a given Load Balancer.
total_countTotal count of backend objects, without pagination.
Create a backend for a given Load Balancer
Create a new backend for a given Load Balancer, specifying its full configuration including protocol, port and forwarding algorithm.
path Parameters
zoneThe zone you want to target
lb_idLoad Balancer ID.
Create a backend for a given Load Balancer › Request Body
nameName for the backend.
forward_protocolProtocol to be used by the backend when forwarding traffic to backend servers.
forward_portPort to be used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to be used when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
server_ipList of backend server IP addresses (IPv4 or IPv6) the backend should forward traffic to.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.
Create a backend for a given Load Balancer › Responses
idBackend ID.
nameName of the backend.
forward_protocolProtocol used by the backend when forwarding traffic to backend servers.
forward_portPort used by the backend when forwarding traffic to backend servers.
forward_port_algorithmLoad balancing algorithm to use when determining which backend server to forward new traffic to.
sticky_sessionsDefines 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.
sticky_sessions_cookie_nameCookie name for cookie-based sticky sessions.
Object defining the health check to be carried out by the backend when checking the status and health of backend servers.
poolList of IP addresses of backend servers attached to this backend.
Load Balancer the backend is attached to.
timeout_serverMaximum allowed time for a backend server to process a request. (in milliseconds)
timeout_connectMaximum allowed time for establishing a connection to a backend server. (in milliseconds)
timeout_tunnelMaximum allowed tunnel inactivity time after Websocket is established (takes precedence over client and server timeout). (in milliseconds)
on_marked_down_actionAction to take when a backend server is marked as down.
proxy_protocolProtocol 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.
created_atDate at which the backend was created. (RFC 3339 format)
updated_atDate at which the backend was updated. (RFC 3339 format)
failover_hostScaleway 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.
ssl_bridgingDefines whether to enable SSL bridging between the Load Balancer and backend servers.
ignore_ssl_server_verifyDefines whether the server certificate verification should be ignored.
redispatch_attempt_countWhether to use another backend server on each attempt.
max_retriesNumber of retries when a backend server connection failed.
max_connectionsMaximum number of connections allowed per backend server.
timeout_queueMaximum time for a request to be left pending in queue when max_connections is reached. (in seconds)
send_proxy_v2Deprecated in favor of proxy_protocol field.