oci_load_balancer_load_balancer
This resource provides the Load Balancer resource in Oracle Cloud Infrastructure Load Balancer service.
Creates a new load balancer in the specified compartment. For general information about load balancers, see Overview of the Load Balancing Service.
For the purposes of access control, you must provide the OCID of the compartment where you want the load balancer to reside. Notice that the load balancer doesn’t have to be in the same compartment as the VCN or backend set. If you’re not sure which compartment to use, put the load balancer in the same compartment as the VCN. For information about access control and compartments, see Overview of the IAM Service.
You must specify a display name for the load balancer. It does not have to be unique, and you can change it.
For information about Availability Domains, see
Regions and Availability Domains.
To get a list of Availability Domains, use the ListAvailabilityDomains
operation
in the Identity and Access Management Service API.
All Oracle Cloud Infrastructure resources, including load balancers, get an Oracle-assigned, unique ID called an Oracle Cloud Identifier (OCID). When you create a resource, you can find its OCID in the response. You can also retrieve a resource’s OCID by using a List API operation on that resource type, or by viewing the resource in the Console. Fore more information, see Resource Identifiers.
When you create a load balancer, the system assigns an IP address. To get the IP address, use the GetLoadBalancer operation.
Supported Aliases
oci_load_balancer
Example Usage
resource "oci_load_balancer_load_balancer" "test_load_balancer" {
#Required
compartment_id = var.compartment_id
display_name = var.load_balancer_display_name
shape = var.load_balancer_shape
subnet_ids = var.load_balancer_subnet_ids
#Optional
defined_tags = {"Operations.CostCenter"= "42"}
freeform_tags = {"Department"= "Finance"}
ip_mode = var.load_balancer_ip_mode
is_delete_protection_enabled = var.load_balancer_is_delete_protection_enabled
is_private = var.load_balancer_is_private
is_request_id_enabled = var.load_balancer_is_request_id_enabled
network_security_group_ids = var.load_balancer_network_security_group_ids
request_id_header = var.load_balancer_request_id_header
reserved_ips {
#Optional
id = var.load_balancer_reserved_ips_id
}
shape_details {
#Required
maximum_bandwidth_in_mbps = var.load_balancer_shape_details_maximum_bandwidth_in_mbps
minimum_bandwidth_in_mbps = var.load_balancer_shape_details_minimum_bandwidth_in_mbps
}
}
Argument Reference
The following arguments are supported:
compartment_id
- (Required) (Updatable) The OCID of the compartment in which to create the load balancer.defined_tags
- (Optional) (Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:{"Operations.CostCenter": "42"}
display_name
- (Required) (Updatable) A user-friendly name. It does not have to be unique, and it is changeable. Avoid entering confidential information. Example:example_load_balancer
freeform_tags
- (Optional) (Updatable) Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:{"Department": "Finance"}
ip_mode
- (Optional) IPv6 is currently supported only in the Government Cloud. Whether the load balancer has an IPv4 or IPv6 IP address.If “IPV4”, the service assigns an IPv4 address and the load balancer supports IPv4 traffic.
If “IPV6”, the service assigns an IPv6 address and the load balancer supports IPv6 traffic.
Example: “ipMode”:“IPV6”
is_delete_protection_enabled
- (Optional) (Updatable) Whether or not the load balancer has delete protection enabled.If “true”, the loadbalancer will be protected against deletion if configured to accept traffic.
If “false”, the loadbalancer will not be protected against deletion.
Delete protection will not be enabled unless a value of “true” is provided. Example:
true
is_private
- (Optional) Whether the load balancer has a VCN-local (private) IP address.If “true”, the service assigns a private IP address to the load balancer.
If “false”, the service assigns a public IP address to the load balancer.
A public load balancer is accessible from the internet, depending on your VCN’s security list rules. For more information about public and private load balancers, see How Load Balancing Works.
Example:
true
is_request_id_enabled
- (Optional) (Updatable) Whether or not the load balancer has the Request Id feature enabled for HTTP listeners.If “true”, the load balancer will attach a unique request id header to every request passed through from the load balancer to load balancer backends. This same request id header also will be added to the response the lb received from the backend handling the request before the load balancer returns the response to the requestor. The name of the unique request id header is set the by value of requestIdHeader.
If “false”, the loadbalancer not add this unique request id header to either the request passed through to the load balancer backends nor to the reponse returned to the user.
New load balancers have the Request Id feature disabled unless isRequestIdEnabled is set to true.
Example:
true
network_security_group_ids
- (Optional) (Updatable) An array of NSG OCIDs associated with this load balancer.During the load balancer’s creation, the service adds the new load balancer to the specified NSGs.
The benefits of using NSGs with the load balancer include:
- NSGs define network security rules to govern ingress and egress traffic for the load balancer.
- The network security rules of other resources can reference the NSGs associated with the load balancer to ensure access.
Example:
["ocid1.nsg.oc1.phx.unique_ID"]
request_id_header
- (Optional) (Updatable) If isRequestIdEnabled is true then this field contains the name of the header field that contains the unique request id that is attached to every request from the load balancer to the load balancer backends and to every response from the load balancer.If a request to the load balancer already contains a header with same name as specified in requestIdHeader then the load balancer will not change the value of that field.
If isRequestIdEnabled is false then this field is ignored.
If this field is not set or is set to “” then this field defaults to X-Request-Id
Notes:
- Unless the header name is “” it must start with “X-” prefix.
- Setting the header name to “” will set it to the default: X-Request-Id.
reserved_ips
- (Optional) An array of reserved Ips. Pre-created public IP that will be used as the IP of this load balancer. This reserved IP will not be deleted when load balancer is deleted. This ip should not be already mapped to any other resource.id
- (Optional) Ocid of the Reserved IP/Public Ip created with VCN.Reserved IPs are IPs which already registered using VCN API.
Create a reserved Public IP and then while creating the load balancer pass the ocid of the reserved IP in this field reservedIp to attach the Ip to Load balancer. Load balancer will be configured to listen to traffic on this IP.
Reserved IPs will not be deleted when the Load balancer is deleted. They will be unattached from the Load balancer.
Example: “ocid1.publicip.oc1.phx.unique_ID” Ocid of the pre-created public IP that should be attached to this load balancer. The public IP will be attached to a private IP. Note If public IP resource is present in the config, the terraform plan will throw
After applying this step and refreshing, the plan was not empty
error, andprivate_ip_id
needs to be added as an input argument to the public IP resource block or ignore from its lifecycle as shown in examples to resolve this error.
shape
- (Required) (Updatable) A template that determines the total pre-provisioned bandwidth (ingress plus egress). To get a list of available shapes, use the ListShapes operation. Example:flexible
NOTE: After May 2023, Fixed shapes - 10Mbps, 100Mbps, 400Mbps, 8000Mbps would be deprecated and only shape allowed would beFlexible
*Note: When updating shape for a load balancer, all existing connections to the load balancer will be reset during the update process. Also10Mbps-Micro
shape cannot be updated to any other shape nor can any other shape be updated to10Mbps-Micro
.shape_details
- (Optional) (Updatable) The configuration details to create load balancer using Flexible shape. This is required only if shapeName isFlexible
.maximum_bandwidth_in_mbps
- (Required) (Updatable) Bandwidth in Mbps that determines the maximum bandwidth (ingress plus egress) that the load balancer can achieve. This bandwidth cannot be always guaranteed. For a guaranteed bandwidth use the minimumBandwidthInMbps parameter.The values must be between minimumBandwidthInMbps and 8000 (8Gbps).
Example:
1500
minimum_bandwidth_in_mbps
- (Required) (Updatable) Bandwidth in Mbps that determines the total pre-provisioned bandwidth (ingress plus egress). The values must be between 10 and the maximumBandwidthInMbps. Example:150
ssl_cipher_suites
- (Optional) The configuration details of an SSL cipher suite.The algorithms that compose a cipher suite help you secure Transport Layer Security (TLS) or Secure Socket Layer (SSL) network connections. A cipher suite defines the list of security algorithms your load balancer uses to negotiate with peers while sending and receiving information. The cipher suites you use affect the security level, performance, and compatibility of your data traffic.
Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API.
Oracle created the following predefined cipher suites that you can specify when you define a resource’s SSL configuration. You can create custom cipher suites if the predefined cipher suites do not meet your requirements.
- oci-default-ssl-cipher-suite-v1
“DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA256” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA384” * oci-modern-ssl-cipher-suite-v1
“AES128-GCM-SHA256” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA256” “DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA384” * oci-compatible-ssl-cipher-suite-v1
“AES128-GCM-SHA256” “AES128-SHA” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA” “AES256-SHA256” “DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA” “ECDHE-RSA-AES256-SHA384” * oci-wider-compatible-ssl-cipher-suite-v1
“AES128-GCM-SHA256” “AES128-SHA” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA” “AES256-SHA256” “CAMELLIA128-SHA” “CAMELLIA256-SHA” “DES-CBC3-SHA” “DH-DSS-AES128-GCM-SHA256” “DH-DSS-AES128-SHA” “DH-DSS-AES128-SHA256” “DH-DSS-AES256-GCM-SHA384” “DH-DSS-AES256-SHA” “DH-DSS-AES256-SHA256” “DH-DSS-CAMELLIA128-SHA” “DH-DSS-CAMELLIA256-SHA” “DH-DSS-DES-CBC3-SHAv” “DH-DSS-SEED-SHA” “DH-RSA-AES128-GCM-SHA256” “DH-RSA-AES128-SHA” “DH-RSA-AES128-SHA256” “DH-RSA-AES256-GCM-SHA384” “DH-RSA-AES256-SHA” “DH-RSA-AES256-SHA256” “DH-RSA-CAMELLIA128-SHA” “DH-RSA-CAMELLIA256-SHA” “DH-RSA-DES-CBC3-SHA” “DH-RSA-SEED-SHA” “DHE-DSS-AES128-GCM-SHA256” “DHE-DSS-AES128-SHA” “DHE-DSS-AES128-SHA256” “DHE-DSS-AES256-GCM-SHA384” “DHE-DSS-AES256-SHA” “DHE-DSS-AES256-SHA256” “DHE-DSS-CAMELLIA128-SHA” “DHE-DSS-CAMELLIA256-SHA” “DHE-DSS-DES-CBC3-SHA” “DHE-DSS-SEED-SHA” “DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA” “DHE-RSA-AES256-SHA256” “DHE-RSA-CAMELLIA128-SHA” “DHE-RSA-CAMELLIA256-SHA” “DHE-RSA-DES-CBC3-SHA” “DHE-RSA-SEED-SHA” “ECDH-ECDSA-AES128-GCM-SHA256” “ECDH-ECDSA-AES128-SHA” “ECDH-ECDSA-AES128-SHA256” “ECDH-ECDSA-AES256-GCM-SHA384” “ECDH-ECDSA-AES256-SHA” “ECDH-ECDSA-AES256-SHA384” “ECDH-ECDSA-DES-CBC3-SHA” “ECDH-ECDSA-RC4-SHA” “ECDH-RSA-AES128-GCM-SHA256” “ECDH-RSA-AES128-SHA” “ECDH-RSA-AES128-SHA256” “ECDH-RSA-AES256-GCM-SHA384” “ECDH-RSA-AES256-SHA” “ECDH-RSA-AES256-SHA384” “ECDH-RSA-DES-CBC3-SHA” “ECDH-RSA-RC4-SHA” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-ECDSA-DES-CBC3-SHA” “ECDHE-ECDSA-RC4-SHA” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA” “ECDHE-RSA-AES256-SHA384” “ECDHE-RSA-DES-CBC3-SHA” “ECDHE-RSA-RC4-SHA” “IDEA-CBC-SHA” “KRB5-DES-CBC3-MD5” “KRB5-DES-CBC3-SHA” “KRB5-IDEA-CBC-MD5” “KRB5-IDEA-CBC-SHA” “KRB5-RC4-MD5” “KRB5-RC4-SHA” “PSK-3DES-EDE-CBC-SHA” “PSK-AES128-CBC-SHA” “PSK-AES256-CBC-SHA” “PSK-RC4-SHA” “RC4-MD5” “RC4-SHA” “SEED-SHA” * oci-default-http2-ssl-cipher-suite-v1
“ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES128-GCM-SHA256” * oci-default-http2-tls-13-ssl-cipher-suite-v1
“TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” * oci-default-http2-tls-12-13-ssl-cipher-suite-v1
“ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES128-GCM-SHA256” “TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” * oci-tls-13-recommended-ssl-cipher-suite-v1
“TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” * oci-tls-12-13-wider-ssl-cipher-suite-v1
“TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES256-SHA384” “AES128-GCM-SHA256” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA256” * oci-tls-11-12-13-wider-ssl-cipher-suite-v1 “TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES256-SHA384” “AES128-GCM-SHA256” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA256” “ECDHE-ECDSA-AES128-SHA” “ECDHE-RSA-AES128-SHA” “ECDHE-RSA-AES256-SHA” “ECDHE-ECDSA-AES256-SHA” “AES128-SHA” “AES256-SHA”
name
- (Required) A friendly name for the SSL cipher suite. It must be unique and it cannot be changed.Note: The name of your user-defined cipher suite must not be the same as any of Oracle’s predefined or reserved SSL cipher suite names:
- oci-default-ssl-cipher-suite-v1
- oci-modern-ssl-cipher-suite-v1
- oci-compatible-ssl-cipher-suite-v1
- oci-wider-compatible-ssl-cipher-suite-v1
- oci-customized-ssl-cipher-suite
- oci-default-http2-ssl-cipher-suite-v1
- oci-default-http2-tls-13-ssl-cipher-suite-v1
- oci-default-http2-tls-12-13-ssl-cipher-suite-v1
- oci-tls-13-recommended-ssl-cipher-suite-v1
- oci-tls-12-13-wider-ssl-cipher-suite-v1
- oci-tls-11-12-13-wider-ssl-cipher-suite-v1
example:
example_cipher_suite
subnet_ids
- (Required) An array of subnet OCIDs.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
Attributes Reference
The following attributes are exported:
compartment_id
- The OCID of the compartment containing the load balancer.defined_tags
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:{"Operations.CostCenter": "42"}
display_name
- A user-friendly name. It does not have to be unique, and it is changeable. Example:example_load_balancer
freeform_tags
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:{"Department": "Finance"}
id
- The OCID of the load balancer.ip_address_details
- An array of IP addresses.ip_address
- An IP address. Example:192.168.0.3
is_public
- Whether the IP address is public or private.If “true”, the IP address is public and accessible from the internet.
If “false”, the IP address is private and accessible only from within the associated VCN.
reserved_ip
-id
- Ocid of the Reserved IP/Public Ip created with VCN.Reserved IPs are IPs which already registered using VCN API.
Create a reserved Public IP and then while creating the load balancer pass the ocid of the reserved IP in this field reservedIp to attach the Ip to Load balancer. Load balancer will be configured to listen to traffic on this IP.
Reserved IPs will not be deleted when the Load balancer is deleted. They will be unattached from the Load balancer.
Example: “ocid1.publicip.oc1.phx.unique_ID”
ip_addresses
- An array of IP addresses. Deprecated: use ip_address_details insteadis_delete_protection_enabled
- Whether or not the load balancer has delete protection enabled.If “true”, the loadbalancer will be protected against deletion if configured to accept traffic.
If “false”, the loadbalancer will not be protected against deletion.
Delete protection is not be enabled unless this field is set to “true”. Example:
true
is_private
- Whether the load balancer has a VCN-local (private) IP address.If “true”, the service assigns a private IP address to the load balancer.
If “false”, the service assigns a public IP address to the load balancer.
A public load balancer is accessible from the internet, depending on your VCN’s security list rules. For more information about public and private load balancers, see How Load Balancing Works.
Example:
true
is_request_id_enabled
- Whether or not the load balancer has the Request Id feature enabled for HTTP listeners.If “true”, the load balancer will attach a unique request id header to every request passed through from the load balancer to load balancer backends. This same request id header also will be added to the response the lb received from the backend handling the request before the load balancer returns the response to the requestor. The name of the unique request id header is set the by value of requestIdHeader.
If “false”, the loadbalancer not add this unique request id header to either the request passed through to the load balancer backends nor to the reponse returned to the user.
Example:
true
network_security_group_ids
- An array of NSG OCIDs associated with the load balancer.During the load balancer’s creation, the service adds the new load balancer to the specified NSGs.
The benefits of associating the load balancer with NSGs include:
- NSGs define network security rules to govern ingress and egress traffic for the load balancer.
- The network security rules of other resources can reference the NSGs associated with the load balancer to ensure access.
Example: [“ocid1.nsg.oc1.phx.unique_ID”]
request_id_header
- If isRequestIdEnabled is true then this field contains the name of the header field that contains the unique request id that is attached to every request from the load balancer to the load balancer backends and to every response from the load balancer.If a request to the load balancer already contains a header with same name as specified in requestIdHeader then the load balancer will not change the value of that field.
If this field is set to “” this field defaults to X-Request-Id.
routing_policies
- A named ordered list of routing rules that is applied to a listener.Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API.
condition_language_version
- The version of the language in whichcondition
ofrules
are composed.name
- The unique name for this list of routing rules. Avoid entering confidential information. Example:example_routing_policy
rules
- The ordered list of routing rules.actions
- A list of actions to be applied when conditions of the routing rule are met.backend_set_name
- Name of the backend set the listener will forward the traffic to. Example:backendSetForImages
name
- The name can be one of these values:FORWARD_TO_BACKENDSET
condition
- A routing rule to evaluate defined conditions against the incoming HTTP request and perform an action.name
- A unique name for the routing policy rule. Avoid entering confidential information.
shape
- A template that determines the total pre-provisioned bandwidth (ingress plus egress). To get a list of available shapes, use the ListShapes operation. Example:100Mbps
shape_details
- The configuration details to update load balancer to a different shape.maximum_bandwidth_in_mbps
- Bandwidth in Mbps that determines the maximum bandwidth (ingress plus egress) that the load balancer can achieve. This bandwidth cannot be always guaranteed. For a guaranteed bandwidth use the minimumBandwidthInMbps parameter.The values must be between minimumBandwidthInMbps and 8000 (8Gbps).
Example:
1500
minimum_bandwidth_in_mbps
- Bandwidth in Mbps that determines the total pre-provisioned bandwidth (ingress plus egress). The values must be between 10 and the maximumBandwidthInMbps. Example:150
ssl_cipher_suites
- The configuration details of an SSL cipher suite.The algorithms that compose a cipher suite help you secure Transport Layer Security (TLS) or Secure Socket Layer (SSL) network connections. A cipher suite defines the list of security algorithms your load balancer uses to negotiate with peers while sending and receiving information. The cipher suites you use affect the security level, performance, and compatibility of your data traffic.
Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API.
Oracle created the following predefined cipher suites that you can specify when you define a resource’s SSL configuration. You can create custom cipher suites if the predefined cipher suites do not meet your requirements.
- oci-default-ssl-cipher-suite-v1
“DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA256” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA384” * oci-modern-ssl-cipher-suite-v1
“AES128-GCM-SHA256” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA256” “DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA384” * oci-compatible-ssl-cipher-suite-v1
“AES128-GCM-SHA256” “AES128-SHA” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA” “AES256-SHA256” “DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA” “ECDHE-RSA-AES256-SHA384” * oci-wider-compatible-ssl-cipher-suite-v1
“AES128-GCM-SHA256” “AES128-SHA” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA” “AES256-SHA256” “CAMELLIA128-SHA” “CAMELLIA256-SHA” “DES-CBC3-SHA” “DH-DSS-AES128-GCM-SHA256” “DH-DSS-AES128-SHA” “DH-DSS-AES128-SHA256” “DH-DSS-AES256-GCM-SHA384” “DH-DSS-AES256-SHA” “DH-DSS-AES256-SHA256” “DH-DSS-CAMELLIA128-SHA” “DH-DSS-CAMELLIA256-SHA” “DH-DSS-DES-CBC3-SHAv” “DH-DSS-SEED-SHA” “DH-RSA-AES128-GCM-SHA256” “DH-RSA-AES128-SHA” “DH-RSA-AES128-SHA256” “DH-RSA-AES256-GCM-SHA384” “DH-RSA-AES256-SHA” “DH-RSA-AES256-SHA256” “DH-RSA-CAMELLIA128-SHA” “DH-RSA-CAMELLIA256-SHA” “DH-RSA-DES-CBC3-SHA” “DH-RSA-SEED-SHA” “DHE-DSS-AES128-GCM-SHA256” “DHE-DSS-AES128-SHA” “DHE-DSS-AES128-SHA256” “DHE-DSS-AES256-GCM-SHA384” “DHE-DSS-AES256-SHA” “DHE-DSS-AES256-SHA256” “DHE-DSS-CAMELLIA128-SHA” “DHE-DSS-CAMELLIA256-SHA” “DHE-DSS-DES-CBC3-SHA” “DHE-DSS-SEED-SHA” “DHE-RSA-AES128-GCM-SHA256” “DHE-RSA-AES128-SHA” “DHE-RSA-AES128-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES256-SHA” “DHE-RSA-AES256-SHA256” “DHE-RSA-CAMELLIA128-SHA” “DHE-RSA-CAMELLIA256-SHA” “DHE-RSA-DES-CBC3-SHA” “DHE-RSA-SEED-SHA” “ECDH-ECDSA-AES128-GCM-SHA256” “ECDH-ECDSA-AES128-SHA” “ECDH-ECDSA-AES128-SHA256” “ECDH-ECDSA-AES256-GCM-SHA384” “ECDH-ECDSA-AES256-SHA” “ECDH-ECDSA-AES256-SHA384” “ECDH-ECDSA-DES-CBC3-SHA” “ECDH-ECDSA-RC4-SHA” “ECDH-RSA-AES128-GCM-SHA256” “ECDH-RSA-AES128-SHA” “ECDH-RSA-AES128-SHA256” “ECDH-RSA-AES256-GCM-SHA384” “ECDH-RSA-AES256-SHA” “ECDH-RSA-AES256-SHA384” “ECDH-RSA-DES-CBC3-SHA” “ECDH-RSA-RC4-SHA” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-ECDSA-DES-CBC3-SHA” “ECDHE-ECDSA-RC4-SHA” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-SHA” “ECDHE-RSA-AES128-SHA256” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-SHA” “ECDHE-RSA-AES256-SHA384” “ECDHE-RSA-DES-CBC3-SHA” “ECDHE-RSA-RC4-SHA” “IDEA-CBC-SHA” “KRB5-DES-CBC3-MD5” “KRB5-DES-CBC3-SHA” “KRB5-IDEA-CBC-MD5” “KRB5-IDEA-CBC-SHA” “KRB5-RC4-MD5” “KRB5-RC4-SHA” “PSK-3DES-EDE-CBC-SHA” “PSK-AES128-CBC-SHA” “PSK-AES256-CBC-SHA” “PSK-RC4-SHA” “RC4-MD5” “RC4-SHA” “SEED-SHA” * oci-default-http2-ssl-cipher-suite-v1
“ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES128-GCM-SHA256” * oci-default-http2-tls-13-ssl-cipher-suite-v1
“TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” * oci-default-http2-tls-12-13-ssl-cipher-suite-v1
“ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “DHE-RSA-AES256-GCM-SHA384” “DHE-RSA-AES128-GCM-SHA256” “TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” * oci-tls-13-recommended-ssl-cipher-suite-v1
“TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” * oci-tls-12-13-wider-ssl-cipher-suite-v1
“TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES256-SHA384” “AES128-GCM-SHA256” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA256” * oci-tls-11-12-13-wider-ssl-cipher-suite-v1 “TLS-AES-128-GCM-SHA256” “TLS-AES-256-GCM-SHA384” “TLS-CHACHA20-POLY1305-SHA256” “ECDHE-ECDSA-AES128-GCM-SHA256” “ECDHE-RSA-AES128-GCM-SHA256” “ECDHE-ECDSA-AES128-SHA256” “ECDHE-RSA-AES128-SHA256” “ECDHE-ECDSA-AES256-GCM-SHA384” “ECDHE-RSA-AES256-GCM-SHA384” “ECDHE-ECDSA-AES256-SHA384” “ECDHE-RSA-AES256-SHA384” “AES128-GCM-SHA256” “AES128-SHA256” “AES256-GCM-SHA384” “AES256-SHA256” “ECDHE-ECDSA-AES128-SHA” “ECDHE-RSA-AES128-SHA” “ECDHE-RSA-AES256-SHA” “ECDHE-ECDSA-AES256-SHA” “AES128-SHA” “AES256-SHA” *
name
- A friendly name for the SSL cipher suite. It must be unique and it cannot be changed.**Note:** The name of your user-defined cipher suite must not be the same as any of Oracle's predefined or reserved SSL cipher suite names: * oci-default-ssl-cipher-suite-v1 * oci-modern-ssl-cipher-suite-v1 * oci-compatible-ssl-cipher-suite-v1 * oci-wider-compatible-ssl-cipher-suite-v1 * oci-customized-ssl-cipher-suite * oci-default-http2-ssl-cipher-suite-v1 * oci-default-http2-tls-13-ssl-cipher-suite-v1 * oci-default-http2-tls-12-13-ssl-cipher-suite-v1 * oci-tls-13-recommended-ssl-cipher-suite-v1 * oci-tls-12-13-wider-ssl-cipher-suite-v1 * oci-tls-11-12-13-wider-ssl-cipher-suite-v1 example: `example_cipher_suite`
state
- The current state of the load balancer.subnet_ids
- An array of subnet OCIDs.system_tags
- System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. System tags can be viewed by users, but can only be created by the system. Example:{"orcl-cloud.free-tier-retained": "true"}
time_created
- The date and time the load balancer was created, in the format defined by RFC3339. Example:2016-08-25T21:10:29.600Z
Timeouts
The timeouts
block allows you to specify timeouts for certain operations:
* create
- (Defaults to 20 minutes), when creating the Load Balancer
* update
- (Defaults to 20 minutes), when updating the Load Balancer
* delete
- (Defaults to 20 minutes), when destroying the Load Balancer
Import
LoadBalancers can be imported using the id
, e.g.
$ terraform import oci_load_balancer_load_balancer.test_load_balancer "id"