backend_sets
Creates, updates, deletes, gets or lists a backend_sets resource.
Overview​
| Name | backend_sets |
| Type | Resource |
| Id | oci.load_balancer.backend_sets |
Fields​
The following fields are returned by SELECT queries:
- get
- list
The backend set information is being retrieved.
| Name | Datatype | Description |
|---|---|---|
name | string | A friendly name for the backend set. It must be unique and it cannot be changed. Valid backend set names include only alphanumeric characters, dashes, and underscores. Backend set names cannot contain spaces. Avoid entering confidential information. Example: example_backend_set |
backendMaxConnections | integer (int32) | The maximum number of simultaneous connections the load balancer can make to any backend in the backend set unless the backend has its own maxConnections setting. If this is not set or set to 0 then the number of simultaneous connections the load balancer can make to any backend in the backend set unless the backend has its own maxConnections setting is unlimited. Example: 300 |
backends | array | |
healthChecker | object | The health check policy configuration. For more information, see [Editing Health Check Policies](/Content/Balance/Tasks/editinghealthcheck.htm). (x-example: {<br /> "protocol": "HTTP",<br /> "isForcePlainText": false,<br /> "urlPath": "/healthcheck",<br /> "port": 8080,<br /> "returnCode": 200,<br /> "retries": 3,<br /> "timeoutInMillis": 3000,<br /> "intervalInMillis": 10000,<br /> "responseBodyRegex": "^((?!false).|\s)*$"<br />}<br />) |
policy | string | The load balancer policy for the backend set. To get a list of available policies, use the [ListPolicies](#/en/loadbalancer/20170115/LoadBalancerPolicy/ListPolicies) operation. Example: LEAST_CONNECTIONS |
sessionPersistenceConfiguration | object | The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness). Session persistence enables the Load Balancing service to direct any number of requests that originate from a single logical client to a single backend web server. For more information, see [Session Persistence](/Content/Balance/Reference/sessionpersistence.htm). To disable application cookie stickiness on a running load balancer, use the [UpdateBackendSet](#/en/loadbalancer/20170115/BackendSet/UpdateBackendSet) operation and specify null for the SessionPersistenceConfigurationDetails object. Example: SessionPersistenceConfigurationDetails: null Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API. (x-example: {<br /> "cookieName": "example_cookie",<br /> "disableFallback": false<br />}<br />) |
sslConfiguration | object | A listener's SSL handling configuration. To use SSL, a listener must be associated with a [certificate bundle](#/en/loadbalancer/20170115/Certificate/). Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API. (x-example: [<br /> {<br /> "protocols": ["TLSv1.1", "TLSv1.2"],<br /> "cipherSuiteName" : "example_cipher_suite",<br /> "serverOrderPreference" : "ENABLED",<br /> "certificateName": "example_certificate_bundle",<br /> "verifyPeerCertificate": true<br /> "verifyDepth": 3,<br /> },<br /> {<br /> "certificateIds": [ "example_certificate_id" ],<br /> "trustedCertificateAuthorityIds": [ "example_certificate_authority_id", "example_certificate_bundle_id"]<br /> "verifyPeerCertificate": true<br /> "verifyDepth": 3,<br /> }<br />]<br />) |
The configuration of a load balancer backend set.<br />For more information on backend set configuration, see<br />[Managing Backend Sets](/Content/Balance/Tasks/managingbackendsets.htm).<br /><br />Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API.<br />
| Name | Datatype | Description |
|---|---|---|
name | string | A friendly name for the backend set. It must be unique and it cannot be changed. Valid backend set names include only alphanumeric characters, dashes, and underscores. Backend set names cannot contain spaces. Avoid entering confidential information. Example: example_backend_set |
backendMaxConnections | integer (int32) | The maximum number of simultaneous connections the load balancer can make to any backend in the backend set unless the backend has its own maxConnections setting. If this is not set or set to 0 then the number of simultaneous connections the load balancer can make to any backend in the backend set unless the backend has its own maxConnections setting is unlimited. Example: 300 |
backends | array | |
healthChecker | object | The health check policy configuration. For more information, see [Editing Health Check Policies](/Content/Balance/Tasks/editinghealthcheck.htm). (x-example: {<br /> "protocol": "HTTP",<br /> "isForcePlainText": false,<br /> "urlPath": "/healthcheck",<br /> "port": 8080,<br /> "returnCode": 200,<br /> "retries": 3,<br /> "timeoutInMillis": 3000,<br /> "intervalInMillis": 10000,<br /> "responseBodyRegex": "^((?!false).|\s)*$"<br />}<br />) |
policy | string | The load balancer policy for the backend set. To get a list of available policies, use the [ListPolicies](#/en/loadbalancer/20170115/LoadBalancerPolicy/ListPolicies) operation. Example: LEAST_CONNECTIONS |
sessionPersistenceConfiguration | object | The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness). Session persistence enables the Load Balancing service to direct any number of requests that originate from a single logical client to a single backend web server. For more information, see [Session Persistence](/Content/Balance/Reference/sessionpersistence.htm). To disable application cookie stickiness on a running load balancer, use the [UpdateBackendSet](#/en/loadbalancer/20170115/BackendSet/UpdateBackendSet) operation and specify null for the SessionPersistenceConfigurationDetails object. Example: SessionPersistenceConfigurationDetails: null Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API. (x-example: {<br /> "cookieName": "example_cookie",<br /> "disableFallback": false<br />}<br />) |
sslConfiguration | object | A listener's SSL handling configuration. To use SSL, a listener must be associated with a [certificate bundle](#/en/loadbalancer/20170115/Certificate/). Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API. (x-example: [<br /> {<br /> "protocols": ["TLSv1.1", "TLSv1.2"],<br /> "cipherSuiteName" : "example_cipher_suite",<br /> "serverOrderPreference" : "ENABLED",<br /> "certificateName": "example_certificate_bundle",<br /> "verifyPeerCertificate": true<br /> "verifyDepth": 3,<br /> },<br /> {<br /> "certificateIds": [ "example_certificate_id" ],<br /> "trustedCertificateAuthorityIds": [ "example_certificate_authority_id", "example_certificate_bundle_id"]<br /> "verifyPeerCertificate": true<br /> "verifyDepth": 3,<br /> }<br />]<br />) |
Methods​
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
get | select | loadBalancerId, backendSetName, region | opc-request-id | Gets the specified backend set's configuration information. |
list | select | loadBalancerId, region | opc-request-id | Lists all backend sets associated with a given load balancer. |
create | insert | loadBalancerId, region, healthChecker, name, policy | opc-request-id, opc-retry-token | Adds a backend set to a load balancer. |
update | update | loadBalancerId, backendSetName, region, policy, backends, healthChecker | opc-request-id, opc-retry-token | Updates a backend set. |
delete | delete | loadBalancerId, backendSetName, region | opc-request-id | Deletes the specified backend set. Note that deleting a backend set removes its backend servers from the load balancer.<br /><br />Before you can delete a backend set, you must remove it from any active listeners.<br /> |
Parameters​
Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
| Name | Datatype | Description |
|---|---|---|
backendSetName | string | The name of the backend set to delete. Example: example_backend_set |
loadBalancerId | string | The [OCID](/Content/General/Concepts/identifiers.htm) of the load balancer associated with the backend set. |
region | string | OCI region identifier (e.g. us-ashburn-1, ap-sydney-1); resolves from OCI_REGION when not supplied in the query. (default: us-ashburn-1, x-stackQL-envVar: OCI_REGION) |
opc-request-id | string | The unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. |
opc-retry-token | string | A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (e.g., if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected). |
SELECT examples​
- get
- list
Gets the specified backend set's configuration information.
SELECT
name,
backendMaxConnections,
backends,
healthChecker,
policy,
sessionPersistenceConfiguration,
sslConfiguration
FROM oci.load_balancer.backend_sets
WHERE loadBalancerId = '{{ loadBalancerId }}' -- required
AND backendSetName = '{{ backendSetName }}' -- required
AND region = '{{ region }}' -- required
AND opc-request-id = '{{ opc-request-id }}'
;
Lists all backend sets associated with a given load balancer.
SELECT
name,
backendMaxConnections,
backends,
healthChecker,
policy,
sessionPersistenceConfiguration,
sslConfiguration
FROM oci.load_balancer.backend_sets
WHERE loadBalancerId = '{{ loadBalancerId }}' -- required
AND region = '{{ region }}' -- required
AND opc-request-id = '{{ opc-request-id }}'
;
INSERT examples​
- create
- Manifest
Adds a backend set to a load balancer.
INSERT INTO oci.load_balancer.backend_sets (
backendMaxConnections,
backends,
healthChecker,
name,
policy,
sessionPersistenceConfiguration,
sslConfiguration,
loadBalancerId,
region,
opc-request-id,
opc-retry-token
)
SELECT
{{ backendMaxConnections }},
'{{ backends }}',
'{{ healthChecker }}' /* required */,
'{{ name }}' /* required */,
'{{ policy }}' /* required */,
'{{ sessionPersistenceConfiguration }}',
'{{ sslConfiguration }}',
'{{ loadBalancerId }}',
'{{ region }}',
'{{ opc-request-id }}',
'{{ opc-retry-token }}'
;
# Description fields are for documentation purposes
- name: backend_sets
props:
- name: loadBalancerId
value: "{{ loadBalancerId }}"
description: Required parameter for the backend_sets resource.
- name: region
value: "{{ region }}"
description: Required parameter for the backend_sets resource.
- name: backendMaxConnections
value: {{ backendMaxConnections }}
description: |
The maximum number of simultaneous connections the load balancer can make to any backend
in the backend set unless the backend has its own maxConnections setting. If this is not
set or set to 0 then the number of simultaneous connections the load balancer can make
to any backend in the backend set unless the backend has its own maxConnections setting
is unlimited.
If setting backendMaxConnections to some value other than 0 then that value must be greater
or equal to 256.
Example: `300`
- name: backends
value:
- backup: {{ backup }}
drain: {{ drain }}
ipAddress: "{{ ipAddress }}"
maxConnections: {{ maxConnections }}
offline: {{ offline }}
port: {{ port }}
weight: {{ weight }}
- name: healthChecker
description: |
The health check policy's configuration details.
value:
intervalInMillis: {{ intervalInMillis }}
isForcePlainText: {{ isForcePlainText }}
port: {{ port }}
protocol: "{{ protocol }}"
responseBodyRegex: "{{ responseBodyRegex }}"
retries: {{ retries }}
returnCode: {{ returnCode }}
timeoutInMillis: {{ timeoutInMillis }}
urlPath: "{{ urlPath }}"
- name: name
value: "{{ name }}"
description: |
A friendly name for the backend set. It must be unique and it cannot be changed.
Valid backend set names include only alphanumeric characters, dashes, and underscores. Backend set names cannot
contain spaces. Avoid entering confidential information.
Example: `example_backend_set`
- name: policy
value: "{{ policy }}"
description: |
The load balancer policy for the backend set. To get a list of available policies, use the
[ListPolicies](#/en/loadbalancer/20170115/LoadBalancerPolicy/ListPolicies) operation.
Example: `LEAST_CONNECTIONS`
- name: sessionPersistenceConfiguration
description: |
The configuration details for implementing session persistence based on a user-specified cookie name (application
cookie stickiness).
Session persistence enables the Load Balancing service to direct any number of requests that originate from a single
logical client to a single backend web server. For more information, see
[Session Persistence](/Content/Balance/Reference/sessionpersistence.htm).
To disable application cookie stickiness on a running load balancer, use the
[UpdateBackendSet](#/en/loadbalancer/20170115/BackendSet/UpdateBackendSet) operation and specify `null` for the
`SessionPersistenceConfigurationDetails` object.
Example: `SessionPersistenceConfigurationDetails: null`
**Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
value:
cookieName: "{{ cookieName }}"
disableFallback: {{ disableFallback }}
- name: sslConfiguration
description: |
The load balancer's SSL handling configuration details.
**Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
value:
certificateIds:
- "{{ certificateIds }}"
certificateName: "{{ certificateName }}"
cipherSuiteName: "{{ cipherSuiteName }}"
protocols:
- "{{ protocols }}"
serverOrderPreference: "{{ serverOrderPreference }}"
trustedCertificateAuthorityIds:
- "{{ trustedCertificateAuthorityIds }}"
verifyDepth: {{ verifyDepth }}
verifyPeerCertificate: {{ verifyPeerCertificate }}
- name: opc-request-id
value: "{{ opc-request-id }}"
description: The unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
description: The unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
- name: opc-retry-token
value: "{{ opc-retry-token }}"
description: A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (e.g., if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
description: A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (e.g., if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
UPDATE examples​
- update
Updates a backend set.
UPDATE oci.load_balancer.backend_sets
SET
backendMaxConnections = {{ backendMaxConnections }},
backends = '{{ backends }}',
healthChecker = '{{ healthChecker }}',
policy = '{{ policy }}',
sessionPersistenceConfiguration = '{{ sessionPersistenceConfiguration }}',
sslConfiguration = '{{ sslConfiguration }}'
WHERE
loadBalancerId = '{{ loadBalancerId }}' --required
AND backendSetName = '{{ backendSetName }}' --required
AND region = '{{ region }}' --required
AND policy = '{{ policy }}' --required
AND backends = '{{ backends }}' --required
AND healthChecker = '{{ healthChecker }}' --required
AND opc-request-id = '{{ opc-request-id}}'
AND opc-retry-token = '{{ opc-retry-token}}';
DELETE examples​
- delete
Deletes the specified backend set. Note that deleting a backend set removes its backend servers from the load balancer.<br /><br />Before you can delete a backend set, you must remove it from any active listeners.<br />
DELETE FROM oci.load_balancer.backend_sets
WHERE loadBalancerId = '{{ loadBalancerId }}' --required
AND backendSetName = '{{ backendSetName }}' --required
AND region = '{{ region }}' --required
AND opc-request-id = '{{ opc-request-id }}'
;