oci.LoadBalancer.BackendSet

(Updatable) The health check policy's configuration details.

The OCID of the load balancer on which to add a backend set.

(Updatable) The load balancer policy for the backend set. To get a list of available policies, use the ListPolicies operation. Example: LEAST_CONNECTIONS

(Updatable) The configuration details for implementing load balancer cookie session persistence (LB cookie stickiness).

A friendly name for the backend set. It must be unique and it cannot be changed.

(Updatable) The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness).

(Updatable) The load balancer's SSL handling configuration details.

(Updatable) The health check policy's configuration details.

The OCID of the load balancer on which to add a backend set.

(Updatable) The load balancer policy for the backend set. To get a list of available policies, use the ListPolicies operation. Example: LEAST_CONNECTIONS

(Updatable) The configuration details for implementing load balancer cookie session persistence (LB cookie stickiness).

A friendly name for the backend set. It must be unique and it cannot be changed.

(Updatable) The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness).

(Updatable) The load balancer's SSL handling configuration details.

(Updatable) The health check policy's configuration details.

The OCID of the load balancer on which to add a backend set.

(Updatable) The load balancer policy for the backend set. To get a list of available policies, use the ListPolicies operation. Example: LEAST_CONNECTIONS

(Updatable) The configuration details for implementing load balancer cookie session persistence (LB cookie stickiness).

A friendly name for the backend set. It must be unique and it cannot be changed.

(Updatable) The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness).

(Updatable) The load balancer's SSL handling configuration details.

(Updatable) The health check policy's configuration details.

The OCID of the load balancer on which to add a backend set.

(Updatable) The load balancer policy for the backend set. To get a list of available policies, use the ListPolicies operation. Example: LEAST_CONNECTIONS

(Updatable) The configuration details for implementing load balancer cookie session persistence (LB cookie stickiness).

A friendly name for the backend set. It must be unique and it cannot be changed.

(Updatable) The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness).

(Updatable) The load balancer's SSL handling configuration details.

(Updatable) The health check policy's configuration details.

The OCID of the load balancer on which to add a backend set.

(Updatable) The load balancer policy for the backend set. To get a list of available policies, use the ListPolicies operation. Example: LEAST_CONNECTIONS

(Updatable) The configuration details for implementing load balancer cookie session persistence (LB cookie stickiness).

A friendly name for the backend set. It must be unique and it cannot be changed.

(Updatable) The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness).

(Updatable) The load balancer's SSL handling configuration details.

(Updatable) The health check policy's configuration details.

The OCID of the load balancer on which to add a backend set.

(Updatable) The load balancer policy for the backend set. To get a list of available policies, use the ListPolicies operation. Example: LEAST_CONNECTIONS

(Updatable) The configuration details for implementing load balancer cookie session persistence (LB cookie stickiness).

A friendly name for the backend set. It must be unique and it cannot be changed.

(Updatable) The configuration details for implementing session persistence based on a user-specified cookie name (application cookie stickiness).

(Updatable) The load balancer's SSL handling configuration details.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The IP address of the backend server. Example: 10.0.0.3

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

Whether the load balancer should treat this server as a backup unit. If true, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy.

Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: false

A friendly name for the backend set. It must be unique and it cannot be changed.

Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false

The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see How Load Balancing Policies Work. Example: 3

The IP address of the backend server. Example: 10.0.0.3

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

Whether the load balancer should treat this server as a backup unit. If true, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy.

Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: false

A friendly name for the backend set. It must be unique and it cannot be changed.

Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false

The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see How Load Balancing Policies Work. Example: 3

The IP address of the backend server. Example: 10.0.0.3

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

Whether the load balancer should treat this server as a backup unit. If true, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy.

Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: false

A friendly name for the backend set. It must be unique and it cannot be changed.

Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false

The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see How Load Balancing Policies Work. Example: 3

The IP address of the backend server. Example: 10.0.0.3

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

Whether the load balancer should treat this server as a backup unit. If true, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy.

Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: false

A friendly name for the backend set. It must be unique and it cannot be changed.

Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false

The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see How Load Balancing Policies Work. Example: 3

The IP address of the backend server. Example: 10.0.0.3

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

Whether the load balancer should treat this server as a backup unit. If true, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy.

Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: false

A friendly name for the backend set. It must be unique and it cannot be changed.

Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false

The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see How Load Balancing Policies Work. Example: 3

The IP address of the backend server. Example: 10.0.0.3

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

Whether the load balancer should treat this server as a backup unit. If true, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy.

Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: false

A friendly name for the backend set. It must be unique and it cannot be changed.

Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false

The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see How Load Balancing Policies Work. Example: 3

(Updatable) The protocol the health check must use; either HTTP or TCP. Example: HTTP

(Updatable) The interval between health checks, in milliseconds. Example: 10000

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

(Updatable) A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$

(Updatable) The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. Example: 3

(Updatable) The status code a healthy backend server should return. Example: 200

(Updatable) The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: 3000

(Updatable) The path against which to run the health check. Example: /healthcheck

(Updatable) The protocol the health check must use; either HTTP or TCP. Example: HTTP

(Updatable) The interval between health checks, in milliseconds. Example: 10000

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

(Updatable) A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$

(Updatable) The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. Example: 3

(Updatable) The status code a healthy backend server should return. Example: 200

(Updatable) The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: 3000

(Updatable) The path against which to run the health check. Example: /healthcheck

(Updatable) The protocol the health check must use; either HTTP or TCP. Example: HTTP

(Updatable) The interval between health checks, in milliseconds. Example: 10000

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

(Updatable) A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$

(Updatable) The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. Example: 3

(Updatable) The status code a healthy backend server should return. Example: 200

(Updatable) The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: 3000

(Updatable) The path against which to run the health check. Example: /healthcheck

(Updatable) The protocol the health check must use; either HTTP or TCP. Example: HTTP

(Updatable) The interval between health checks, in milliseconds. Example: 10000

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

(Updatable) A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$

(Updatable) The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. Example: 3

(Updatable) The status code a healthy backend server should return. Example: 200

(Updatable) The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: 3000

(Updatable) The path against which to run the health check. Example: /healthcheck

(Updatable) The protocol the health check must use; either HTTP or TCP. Example: HTTP

(Updatable) The interval between health checks, in milliseconds. Example: 10000

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

(Updatable) A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$

(Updatable) The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. Example: 3

(Updatable) The status code a healthy backend server should return. Example: 200

(Updatable) The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: 3000

(Updatable) The path against which to run the health check. Example: /healthcheck

(Updatable) The protocol the health check must use; either HTTP or TCP. Example: HTTP

(Updatable) The interval between health checks, in milliseconds. Example: 10000

(Updatable) The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the Backend object. Example: 8080

(Updatable) A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$

(Updatable) The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. Example: 3

(Updatable) The status code a healthy backend server should return. Example: 200

(Updatable) The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: 3000

(Updatable) The path against which to run the health check. Example: /healthcheck

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The domain in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a domain attribute with the specified value.

(Updatable) Whether the Set-cookie header should contain the HttpOnly attribute. If true, the Set-cookie header inserted by the load balancer contains the HttpOnly attribute, which limits the scope of the cookie to HTTP requests. This attribute directs the client or browser to omit the cookie when providing access to cookies through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels. Example: true

(Updatable) Whether the Set-cookie header should contain the Secure attribute. If true, the Set-cookie header inserted by the load balancer contains the Secure attribute, which directs the client or browser to send the cookie only using a secure protocol.

(Updatable) The amount of time the cookie remains valid. The Set-cookie header inserted by the load balancer contains a Max-Age attribute with the specified value.

(Updatable) The path in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a Path attribute with the specified value.

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The domain in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a domain attribute with the specified value.

(Updatable) Whether the Set-cookie header should contain the HttpOnly attribute. If true, the Set-cookie header inserted by the load balancer contains the HttpOnly attribute, which limits the scope of the cookie to HTTP requests. This attribute directs the client or browser to omit the cookie when providing access to cookies through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels. Example: true

(Updatable) Whether the Set-cookie header should contain the Secure attribute. If true, the Set-cookie header inserted by the load balancer contains the Secure attribute, which directs the client or browser to send the cookie only using a secure protocol.

(Updatable) The amount of time the cookie remains valid. The Set-cookie header inserted by the load balancer contains a Max-Age attribute with the specified value.

(Updatable) The path in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a Path attribute with the specified value.

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The domain in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a domain attribute with the specified value.

(Updatable) Whether the Set-cookie header should contain the HttpOnly attribute. If true, the Set-cookie header inserted by the load balancer contains the HttpOnly attribute, which limits the scope of the cookie to HTTP requests. This attribute directs the client or browser to omit the cookie when providing access to cookies through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels. Example: true

(Updatable) Whether the Set-cookie header should contain the Secure attribute. If true, the Set-cookie header inserted by the load balancer contains the Secure attribute, which directs the client or browser to send the cookie only using a secure protocol.

(Updatable) The amount of time the cookie remains valid. The Set-cookie header inserted by the load balancer contains a Max-Age attribute with the specified value.

(Updatable) The path in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a Path attribute with the specified value.

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The domain in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a domain attribute with the specified value.

(Updatable) Whether the Set-cookie header should contain the HttpOnly attribute. If true, the Set-cookie header inserted by the load balancer contains the HttpOnly attribute, which limits the scope of the cookie to HTTP requests. This attribute directs the client or browser to omit the cookie when providing access to cookies through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels. Example: true

(Updatable) Whether the Set-cookie header should contain the Secure attribute. If true, the Set-cookie header inserted by the load balancer contains the Secure attribute, which directs the client or browser to send the cookie only using a secure protocol.

(Updatable) The amount of time the cookie remains valid. The Set-cookie header inserted by the load balancer contains a Max-Age attribute with the specified value.

(Updatable) The path in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a Path attribute with the specified value.

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The domain in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a domain attribute with the specified value.

(Updatable) Whether the Set-cookie header should contain the HttpOnly attribute. If true, the Set-cookie header inserted by the load balancer contains the HttpOnly attribute, which limits the scope of the cookie to HTTP requests. This attribute directs the client or browser to omit the cookie when providing access to cookies through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels. Example: true

(Updatable) Whether the Set-cookie header should contain the Secure attribute. If true, the Set-cookie header inserted by the load balancer contains the Secure attribute, which directs the client or browser to send the cookie only using a secure protocol.

(Updatable) The amount of time the cookie remains valid. The Set-cookie header inserted by the load balancer contains a Max-Age attribute with the specified value.

(Updatable) The path in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a Path attribute with the specified value.

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The domain in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a domain attribute with the specified value.

(Updatable) Whether the Set-cookie header should contain the HttpOnly attribute. If true, the Set-cookie header inserted by the load balancer contains the HttpOnly attribute, which limits the scope of the cookie to HTTP requests. This attribute directs the client or browser to omit the cookie when providing access to cookies through non-HTTP APIs. For example, it restricts the cookie from JavaScript channels. Example: true

(Updatable) Whether the Set-cookie header should contain the Secure attribute. If true, the Set-cookie header inserted by the load balancer contains the Secure attribute, which directs the client or browser to send the cookie only using a secure protocol.

(Updatable) The amount of time the cookie remains valid. The Set-cookie header inserted by the load balancer contains a Max-Age attribute with the specified value.

(Updatable) The path in which the cookie is valid. The Set-cookie header inserted by the load balancer contains a Path attribute with the specified value.

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: example_cookie

(Updatable) Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: false

(Updatable) Ids for Oracle Cloud Infrastructure certificates service certificates. Currently only a single Id may be passed. Example: [ocid1.certificate.oc1.us-ashburn-1.amaaaaaaav3bgsaa5o2q7rh5nfmkkukfkogasqhk6af2opufhjlqg7m6jqzq]

(Updatable) A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: example_certificate_bundle

(Updatable) The name of the cipher suite to use for HTTPS or SSL connections.

(Updatable) A list of SSL protocols the load balancer must support for HTTPS or SSL connections.

(Updatable) When this attribute is set to ENABLED, the system gives preference to the server ciphers over the client ciphers.

(Updatable) Ids for Oracle Cloud Infrastructure certificates service CA or CA bundles for the load balancer to trust. Example: [ocid1.cabundle.oc1.us-ashburn-1.amaaaaaaav3bgsaagl4zzyqdop5i2vuwoqewdvauuw34llqa74otq2jdsfyq]

(Updatable) The maximum depth for peer certificate chain verification. Example: 3

(Updatable) Whether the load balancer listener should verify peer certificates. Example: true

(Updatable) Ids for Oracle Cloud Infrastructure certificates service certificates. Currently only a single Id may be passed. Example: [ocid1.certificate.oc1.us-ashburn-1.amaaaaaaav3bgsaa5o2q7rh5nfmkkukfkogasqhk6af2opufhjlqg7m6jqzq]

(Updatable) A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: example_certificate_bundle

(Updatable) The name of the cipher suite to use for HTTPS or SSL connections.

(Updatable) A list of SSL protocols the load balancer must support for HTTPS or SSL connections.

(Updatable) When this attribute is set to ENABLED, the system gives preference to the server ciphers over the client ciphers.

(Updatable) Ids for Oracle Cloud Infrastructure certificates service CA or CA bundles for the load balancer to trust. Example: [ocid1.cabundle.oc1.us-ashburn-1.amaaaaaaav3bgsaagl4zzyqdop5i2vuwoqewdvauuw34llqa74otq2jdsfyq]

(Updatable) The maximum depth for peer certificate chain verification. Example: 3

(Updatable) Whether the load balancer listener should verify peer certificates. Example: true

(Updatable) Ids for Oracle Cloud Infrastructure certificates service certificates. Currently only a single Id may be passed. Example: [ocid1.certificate.oc1.us-ashburn-1.amaaaaaaav3bgsaa5o2q7rh5nfmkkukfkogasqhk6af2opufhjlqg7m6jqzq]

(Updatable) A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: example_certificate_bundle

(Updatable) The name of the cipher suite to use for HTTPS or SSL connections.

(Updatable) A list of SSL protocols the load balancer must support for HTTPS or SSL connections.

(Updatable) When this attribute is set to ENABLED, the system gives preference to the server ciphers over the client ciphers.

(Updatable) Ids for Oracle Cloud Infrastructure certificates service CA or CA bundles for the load balancer to trust. Example: [ocid1.cabundle.oc1.us-ashburn-1.amaaaaaaav3bgsaagl4zzyqdop5i2vuwoqewdvauuw34llqa74otq2jdsfyq]

(Updatable) The maximum depth for peer certificate chain verification. Example: 3

(Updatable) Whether the load balancer listener should verify peer certificates. Example: true

(Updatable) Ids for Oracle Cloud Infrastructure certificates service certificates. Currently only a single Id may be passed. Example: [ocid1.certificate.oc1.us-ashburn-1.amaaaaaaav3bgsaa5o2q7rh5nfmkkukfkogasqhk6af2opufhjlqg7m6jqzq]

(Updatable) A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: example_certificate_bundle

(Updatable) The name of the cipher suite to use for HTTPS or SSL connections.

(Updatable) A list of SSL protocols the load balancer must support for HTTPS or SSL connections.

(Updatable) When this attribute is set to ENABLED, the system gives preference to the server ciphers over the client ciphers.

(Updatable) Ids for Oracle Cloud Infrastructure certificates service CA or CA bundles for the load balancer to trust. Example: [ocid1.cabundle.oc1.us-ashburn-1.amaaaaaaav3bgsaagl4zzyqdop5i2vuwoqewdvauuw34llqa74otq2jdsfyq]

(Updatable) The maximum depth for peer certificate chain verification. Example: 3

(Updatable) Whether the load balancer listener should verify peer certificates. Example: true

(Updatable) Ids for Oracle Cloud Infrastructure certificates service certificates. Currently only a single Id may be passed. Example: [ocid1.certificate.oc1.us-ashburn-1.amaaaaaaav3bgsaa5o2q7rh5nfmkkukfkogasqhk6af2opufhjlqg7m6jqzq]

(Updatable) A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: example_certificate_bundle

(Updatable) The name of the cipher suite to use for HTTPS or SSL connections.

(Updatable) A list of SSL protocols the load balancer must support for HTTPS or SSL connections.

(Updatable) When this attribute is set to ENABLED, the system gives preference to the server ciphers over the client ciphers.

(Updatable) Ids for Oracle Cloud Infrastructure certificates service CA or CA bundles for the load balancer to trust. Example: [ocid1.cabundle.oc1.us-ashburn-1.amaaaaaaav3bgsaagl4zzyqdop5i2vuwoqewdvauuw34llqa74otq2jdsfyq]

(Updatable) The maximum depth for peer certificate chain verification. Example: 3

(Updatable) Whether the load balancer listener should verify peer certificates. Example: true

(Updatable) Ids for Oracle Cloud Infrastructure certificates service certificates. Currently only a single Id may be passed. Example: [ocid1.certificate.oc1.us-ashburn-1.amaaaaaaav3bgsaa5o2q7rh5nfmkkukfkogasqhk6af2opufhjlqg7m6jqzq]

(Updatable) A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: example_certificate_bundle

(Updatable) The name of the cipher suite to use for HTTPS or SSL connections.

(Updatable) A list of SSL protocols the load balancer must support for HTTPS or SSL connections.

(Updatable) When this attribute is set to ENABLED, the system gives preference to the server ciphers over the client ciphers.

(Updatable) Ids for Oracle Cloud Infrastructure certificates service CA or CA bundles for the load balancer to trust. Example: [ocid1.cabundle.oc1.us-ashburn-1.amaaaaaaav3bgsaagl4zzyqdop5i2vuwoqewdvauuw34llqa74otq2jdsfyq]

(Updatable) The maximum depth for peer certificate chain verification. Example: 3

(Updatable) Whether the load balancer listener should verify peer certificates. Example: true