ELB_API_20251118_Version

Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com>
Co-authored-by: zhoumeng <zhoumeng35@huawei.com>
Co-committed-by: zhoumeng <zhoumeng35@huawei.com>
This commit is contained in:
2025-12-04 21:11:56 +00:00
committed by zuul
parent 3bac3b88e8
commit 79a6901263
34 changed files with 4066 additions and 963 deletions

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -101,8 +101,9 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.3 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the body of the certificate required by HTTPS listeners. The value must be PEM encoded.</p>
<p>Maximum 65,536 character length is allowed, supports certificate chains with a maximum of 11 layers (including certificates and certificate chains).</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the body of the certificate required by HTTPS listeners.</p>
<p>The value must be PEM encoded, and can contain a maximum of 65,536 characters.</p>
<p>It supports certificate chains with a maximum of 11 layers (including certificates and certificate chains).</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.1 "><p>description</p>
@ -126,7 +127,7 @@
<p>Note the following when using domain names:</p>
<ul><li><p>The value can contain 0 to 10,000 characters and consists of multiple common domain names or wildcard domain names separated by commas. A maximum of 100 domain names are allowed.</p>
</li><li><p>A common domain name consists of several labels separated by periods (.). Each label can contain a maximum of 63 characters, including letters, digits, and hyphens (-), and must start and end with a letter or digit. Example: www.test.com</p>
</li><li><p>A wildcard domain name is a domain name starts with an asterisk (*). Example: *.test.com</p>
</li><li><p>A wildcard domain name is a domain name starting with an asterisk (*). Example: *.test.com</p>
</li><li><p>This parameter will take effect only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.</p>
</li><li><p>SNI certificates of a shared load balancer's listener can have up to 30 domain names.</p>
@ -263,7 +264,7 @@
<p>Note the following when using domain names:</p>
<ul><li><p>The value can contain 0 to 10,000 characters and consists of multiple common domain names or wildcard domain names separated by commas. A maximum of 100 domain names are allowed.</p>
</li><li><p>A common domain name consists of several labels separated by periods (.). Each label can contain a maximum of 63 characters, including letters, digits, and hyphens (-), and must start and end with a letter or digit. Example: www.test.com</p>
</li><li><p>A wildcard domain name is a domain name starts with an asterisk (*). Example: *.test.com</p>
</li><li><p>A wildcard domain name is a domain name starting with an asterisk (*). Example: *.test.com</p>
</li><li><p>This parameter will take effect only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.</p>
</li><li><p>SNI certificates of a shared load balancer's listener can have up to 30 domain names.</p>
@ -338,7 +339,7 @@
</div>
</div>
<div class="section"><h4 class="sectiontitle">Example Requests</h4><p>Creating a server certificate</p>
<pre class="screen">POST https://{elb_endponit}/v3/{project_id}/elb/certificates
<pre class="screen">POST https://{ELB_Endpoint}/v3/{project_id}/elb/certificates
{
"certificate" : {

File diff suppressed because it is too large Load Diff

View File

@ -135,6 +135,7 @@
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.3 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the ID of the enterprise project that the IP address group belongs to.</p>
<p>This parameter is unsupported. Please do not use it.</p>
</td>
</tr>
</tbody>

View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Adding a Forwarding Policy</h1>
<div id="body1708331107508"><div class="section"><h4 class="sectiontitle">Function</h4><p>This API is used to add a forwarding policy to a listener.</p>
</div>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>Forwarding policies can be added to only to HTTP or HTTPS listeners.</p>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>Forwarding policies can be added only to HTTP or HTTPS listeners.</p>
</div>
<div class="section" id="CreateL7Policy__atuogenerate_1"><h4 class="sectiontitle">URI</h4><p>POST /v3/{project_id}/elb/l7policies</p>
@ -99,9 +99,9 @@
</li><li><p><strong>REDIRECT_TO_URL</strong>: Requests will be redirected to another URL.</p>
</li><li><p><strong>FIXED_RESPONSE</strong>: A fixed response body will be returned.</p>
</li></ul>
<p><strong>REDIRECT_TO_LISTENER</strong> has the highest priority. If requests are to be redirected to an HTTPS listener, other forwarding policies of the listener will become invalid.</p>
<p>Note:</p>
<ul><li><p>If <strong>action</strong> is set to <strong>REDIRECT_TO_POOL</strong>, the listener's protocol must be HTTP or HTTPS.</p>
<ul><li><p><strong>REDIRECT_TO_LISTENER</strong> has the highest priority. If requests are to be redirected to an HTTPS listener, other forwarding policies of the listener will become invalid.</p>
</li><li><p>If <strong>action</strong> is set to <strong>REDIRECT_TO_POOL</strong>, the listener's protocol must be HTTP or HTTPS.</p>
</li><li><p>If <strong>action</strong> is set to <strong>REDIRECT_TO_LISTENER</strong>, the listener's protocol must be HTTP.</p>
</li></ul>
<p>Minimum: <strong>1</strong></p>

View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Adding a Forwarding Rule</h1>
<div id="body1708331107508"><div class="section"><h4 class="sectiontitle">Function</h4><p>This API is used to add a forwarding rule.</p>
</div>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>If the action of <strong>l7policy</strong> is set to <strong>Redirect to another listener</strong>, <strong>17rule</strong> cannot be created.</p>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>The forwarding rule cannot be created when <strong>action</strong> is set to <strong>REDIRECT_TO_LISTENER</strong>.</p>
</div>
<div class="section" id="CreateL7Rule__atuogenerate_1"><h4 class="sectiontitle">URI</h4><p>POST /v3/{project_id}/elb/l7policies/{l7policy_id}/rules</p>

File diff suppressed because it is too large Load Diff

View File

@ -14,7 +14,7 @@
</div>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>There are some constraints when you create a dedicated load balancer:</p>
<ul><li><p><strong>vpc_id</strong>, <strong>vip_subnet_cidr_id</strong>, and <strong>ipv6_vip_virsubnet_id</strong> cannot be left blank at the same time.</p>
</li><li><p><strong>ip_target_enable</strong> specifies whether to enable <strong>IP as a Backend Server</strong>. If you enable this function for a dedicated load balancer, you can associate servers in a VPC connected through a VPC peering connection, in a VPC connected through a cloud connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using server IP addresses.</p>
</li><li><p><strong>ip_target_enable</strong> specifies whether to enable <strong>IP as a Backend</strong>. If you enable this function for a dedicated load balancer, you can associate servers in a VPC connected through a VPC peering connection, in a VPC connected through a cloud connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using server IP addresses.</p>
</li><li><p><strong>admin_state_up</strong> must be set to <strong>true</strong>.</p>
</li><li><p><strong>provider</strong> must be set to <strong>vlb</strong>.</p>
</li><li><p><strong>elb_virsubnet_ids</strong> indicates the subnets that support IPv4/IPv6 dual stack or only IPv4 subnets. If only IPv4 subnets are supported, <strong>ipv6_vip_virsubnet_id</strong> must be left blank.</p>
@ -337,11 +337,11 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.4.2.5.1.3 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies whether to enable <strong>IP as a Backend Server</strong>.</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies whether to enable <strong>IP as a Backend</strong>.</p>
<p>If you enable this function, you can add servers in a peer VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</p>
<p>This function is supported only by dedicated load balancers.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend Server</strong>) or <strong>false</strong> (disable <strong>IP as a Backend Server</strong>).</p>
<p>The value can only be update to <strong>true</strong>.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend</strong>) or <strong>false</strong> (disable <strong>IP as a Backend</strong>).</p>
<p>The value can only be updated to <strong>true</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.4.2.5.1.1 "><p>deletion_protection_enable</p>
@ -801,14 +801,14 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>updated_at</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>guaranteed</p>
@ -959,11 +959,11 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend Server</strong>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend</strong>.</p>
<p>If you enable this function, you can add servers in a peer VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</p>
<p>This function is supported only by dedicated load balancers.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend Server</strong>) or <strong>false</strong> (disable <strong>IP as a Backend Server</strong>).</p>
<p>The value can only be update to <strong>true</strong>.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend</strong>) or <strong>false</strong> (disable <strong>IP as a Backend</strong>).</p>
<p>The value can only be updated to <strong>true</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>frozen_scene</p>
@ -1000,7 +1000,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the information about elastic scaling. If elastic scaling is enabled, the load balancer specifications can be automatically adjusted based on incoming traffic.</p>
<p>Note:</p>
<ul><li><p>This parameter is only available for users on the whitelist.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 7.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 7.</p>
</li></ul>
</td>
</tr>
@ -1523,7 +1523,7 @@
</div>
</div>
<div class="section"><h4 class="sectiontitle">Example Requests</h4><ul><li><p>Example 1: Creating a load balancer with a private IPv4 address</p>
<pre class="screen">POST https://{ELB_Endponit}/v3/060576782980d5762f9ec014dd2f1148/elb/loadbalancers
<pre class="screen">POST https://{ELB_Endpoint}/v3/060576782980d5762f9ec014dd2f1148/elb/loadbalancers
{
"loadbalancer" : {
@ -1535,7 +1535,7 @@
}
}</pre>
</li><li><p>Example 2: Creating a load balancer with an IPv4 EIP</p>
<pre class="screen">POST https://{ELB_Endponit}/v3/060576782980d5762f9ec014dd2f1148/elb/loadbalancers
<pre class="screen">POST https://{ELB_Endpoint}/v3/060576782980d5762f9ec014dd2f1148/elb/loadbalancers
{
"loadbalancer" : {

View File

@ -5,7 +5,7 @@
</div>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>When you add backend servers, note the following:</p>
<ul><li><p>Two backend servers in the same backend server group must have different IP addresses and ports.</p>
</li><li><p>If no subnets are specified during cloud server creation, IP as Backend servers can be added. In this case, <strong>address</strong> must be set to an IPv4 address, the protocol of the backend server group must be TCP, HTTP, or HTTPS, and <strong>IP as a Backend Server</strong> must have been enabled for the load balancer.</p>
</li><li><p>If no subnets are specified during cloud server creation, IP as backend servers can be added. In this case, <strong>address</strong> must be set to an IPv4 address, the protocol of the backend server group must be TCP, HTTP, or HTTPS, and <strong>IP as a Backend</strong> must have been enabled for the load balancer.</p>
</li><li><p>If a subnet is specified during cloud server creation, the subnet must be in the same VPC where the load balancer resides.</p>
</li><li><p>If the backend server group supports IPv4/IPv6 dual stack, <strong>address</strong> can be an IPv4 address or an IPv6 address. If the backend server group supports only IPv4, <strong>address</strong> can only be an IPv4 address.</p>
</li></ul>
@ -108,7 +108,7 @@
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.4.2.5.1.3 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the private IP address bound to the backend server.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend Server</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
</li><li><p>If <strong>subnet_cidr_id</strong> is not left blank, the IP address can be IPv4 or IPv6. It must be in the subnet specified by <strong>subnet_cidr_id</strong> and can only be bound to the primary NIC of the backend server.</p>
</li></ul>
<p>Minimum: <strong>1</strong></p>
@ -167,7 +167,7 @@
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the ID of the IPv4 or IPv6 subnet where the backend server resides.</p>
<p>Note:</p>
<ul><li><p>The IPv4 or IPv6 subnet must be in the same VPC as the subnet of the load balancer.</p>
</li><li><p>If this parameter is not passed, <strong>IP as a Backend Server</strong> has been enabled for the load balancer. In this case, IP as Backend servers must use private IPv4 addresses, and the protocol of the backend server group must be TCP, HTTP, or HTTPS.</p>
</li><li><p>If this parameter is not passed, <strong>IP as a Backend</strong> has been enabled for the load balancer. In this case, IP as backend servers must use private IPv4 addresses, and the protocol of the backend server group must be TCP, HTTP, or HTTPS.</p>
</li></ul>
<p>Minimum: <strong>1</strong></p>
<p>Maximum: <strong>36</strong></p>
@ -311,7 +311,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the private IP address bound to the backend server.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend Server</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
</li><li><p>If <strong>subnet_cidr_id</strong> is not left blank, the IP address can be IPv4 or IPv6. It must be in the subnet specified by <strong>subnet_cidr_id</strong> and can only be bound to the primary NIC of the backend server.</p>
</li></ul>
</td>
@ -496,7 +496,7 @@
"address" : "120.10.10.16"
}
}</pre>
</li><li><p>Example 2: Adding a server of <strong>IP as a Backend Server</strong></p>
</li><li><p>Example 2: Adding an IP as a backend server</p>
<pre class="screen">POST https://{ELB_Endpoint}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/pools/36ce7086-a496-4666-9064-5ba0e6840c75/members
{

View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Creating a Backend Server Group</h1>
<div id="body1708331107508"><div class="section"><h4 class="sectiontitle">Function</h4><p>This API is used to create a backend server group.</p>
</div>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>If <strong>session-persistence</strong> is specified, <strong>cookie_name</strong> is available only when <strong>type</strong> is set to <strong>APP_COOKIE</strong>.</p>
<div class="section"><h4 class="sectiontitle">Constraints</h4><p>If <strong>session_persistence</strong> is specified, <strong>cookie_name</strong> is available only when <strong>type</strong> is set to <strong>APP_COOKIE</strong>.</p>
<p>If <strong>listener_id</strong> is specified, the listener must have no backend server group associated.</p>
</div>
<div class="section" id="CreatePool__atuogenerate_1"><h4 class="sectiontitle">URI</h4><p>POST /v3/{project_id}/elb/pools</p>
@ -233,7 +233,7 @@
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the ID of the VPC where the backend server group works.</p>
<p>Note:</p>
<ul><li><p>The backend server group must be associated with the VPC.</p>
</li><li><p>Only backend servers in the VPC or IP as Backend servers can be added.</p>
</li><li><p>Only backend servers in the VPC or IP as backend servers can be added.</p>
</li><li><p><strong>type</strong> must be set to <strong>instance</strong>.</p>
</li></ul>
<p>If <strong>vpc_id</strong> is not specified:</p>
@ -251,12 +251,12 @@
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>""</strong>: Any type of backend servers can be added.</p>
</li></ul>
<p>Note:</p>
<ul><li><p>If this parameter is not passed, any type of backend servers can be added. <strong>type</strong> will be returned as an empty string.</p>
</li><li><p>Specify one of <strong>listener_id</strong>, <strong>loadbalancer_id</strong>, or <strong>type</strong>. Shared load balancers can only can added to the backend server group with <strong>loadbalancer_id</strong> or <strong>listener_id</strong> specified.</p>
</li><li><p>Specify one of <strong>listener_id</strong>, <strong>loadbalancer_id</strong>, or <strong>type</strong>. Shared load balancers can only be associated with backend server groups with <strong>loadbalancer_id</strong> or <strong>listener_id</strong> specified.</p>
</li></ul>
<p>Minimum: <strong>0</strong></p>
<p>Maximum: <strong>36</strong></p>
@ -505,7 +505,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the protocol used by the backend server group to receive requests. The value can be <strong>TCP</strong>, <strong>UDP</strong>, <strong>HTTP</strong>, <strong>HTTPS</strong>, or <strong>QUIC</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong> or <strong>QUIC</strong>.</p>
</li><li><p>If the listener's protocol is <strong>TCP</strong>, the protocol of the backend server group must be <strong>TCP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTP</strong>, the protocol of the backend server group must be <strong>HTTP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTPS</strong>, the protocol of the backend server group can be <strong>HTTP</strong> or <strong>HTTPS</strong>.</p>
@ -526,7 +526,9 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the IP address version supported by the backend server group.</p>
<p>IPv6 is unsupported. Only <strong>v4</strong> will be returned.</p>
<ul><li><p>Shared load balancers: The value is fixed at <strong>v4</strong>.</p>
</li><li><p>Dedicated load balancers: The value can be <strong>dualstack</strong> or <strong>v4</strong>. If the protocol of the backend server group is TCP or UDP, the value is <strong>dualstack</strong>. If the protocol of the backend server group is HTTP or HTTPS, the value is <strong>v4</strong>.</p>
</li></ul>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>slow_start</p>
@ -578,7 +580,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>""</strong>: Any type of backend servers can be added.</p>
</li></ul>
</td>

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -198,7 +198,7 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.3 "><p>Array of strings</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the ID of the backend server group to which the backend sever belongs.</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the ID of the backend server group to which the backend server belongs.</p>
<p>Multiple IDs can be queried in the format of <em>pool_id=xxx&amp;pool_id=xxx</em>.</p>
</td>
</tr>
@ -396,7 +396,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.5.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.5.2.4.1.3 "><p>Specifies the private IP address bound to the backend server.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend Server</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
</li><li><p>If <strong>subnet_cidr_id</strong> is not left blank, the IP address can be IPv4 or IPv6. It must be in the subnet specified by <strong>subnet_cidr_id</strong> and can only be bound to the primary NIC of the backend server.</p>
</li></ul>
</td>

View File

@ -282,7 +282,7 @@
<p>Note the following when using domain names:</p>
<ul><li><p>The value can contain 0 to 10,000 characters and consists of multiple common domain names or wildcard domain names separated by commas. A maximum of 100 domain names are allowed.</p>
</li><li><p>A common domain name consists of several labels separated by periods (.). Each label can contain a maximum of 63 characters, including letters, digits, and hyphens (-), and must start and end with a letter or digit. Example: www.test.com</p>
</li><li><p>A wildcard domain name is a domain name starts with an asterisk (*). Example: *.test.com</p>
</li><li><p>A wildcard domain name is a domain name starting with an asterisk (*). Example: *.test.com</p>
</li><li><p>This parameter will take effect only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.</p>
</li><li><p>SNI certificates of a shared load balancer's listener can have up to 30 domain names.</p>

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -26,7 +26,7 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.3.2.5.1.3 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.3.2.5.1.4 "><p>This parameter has the same meaning as <strong>eips</strong>.</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.3.2.5.1.4 "><p>Specifies the ID of the project where the load balancer is used.</p>
<p>Minimum: <strong>1</strong></p>
<p>Maximum: <strong>255</strong></p>
</td>
@ -592,14 +592,14 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>updated_at</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>guaranteed</p>
@ -750,11 +750,11 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend Server</strong>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend</strong>.</p>
<p>If you enable this function, you can add servers in a peer VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</p>
<p>This function is supported only by dedicated load balancers.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend Server</strong>) or <strong>false</strong> (disable <strong>IP as a Backend Server</strong>).</p>
<p>The value can only be update to <strong>true</strong>.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend</strong>) or <strong>false</strong> (disable <strong>IP as a Backend</strong>).</p>
<p>The value can only be updated to <strong>true</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>frozen_scene</p>
@ -791,7 +791,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the information about elastic scaling. If elastic scaling is enabled, the load balancer specifications can be automatically adjusted based on incoming traffic.</p>
<p>Note:</p>
<ul><li><p>This parameter is only available for users on the whitelist.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 7.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 7.</p>
</li></ul>
</td>
</tr>

View File

@ -209,7 +209,7 @@
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.3 "><p>Array of strings</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the type of the backend server. Values:</p>
<ul><li><p><strong>ip</strong>: IP as Backend servers</p>
<ul><li><p><strong>ip</strong>: IP as backend servers</p>
</li><li><p><strong>instance</strong>: ECSs used as backend servers</p>
</li></ul>
<p>Multiple values can be queried in the format of <em>member_type=xxx&amp;member_type=xxx</em>.</p>
@ -222,7 +222,7 @@
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.3 "><p>Array of strings</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the ID of the instance associated with the backend server. If this parameter is left blank, the backend server is not an ECS. It may be an IP address.</p>
<p>Multiple instance id can be queried in the format of <em>instance_id=xxx&amp;instance_id=xxx</em>.</p>
<p>Multiple instance IDs can be queried in the format of <em>instance_id=xxx&amp;instance_id=xxx</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.1 "><p>availability_zone</p>
@ -415,7 +415,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.5.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.5.2.4.1.3 "><p>Specifies the private IP address bound to the backend server.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend Server</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
</li><li><p>If <strong>subnet_cidr_id</strong> is not left blank, the IP address can be IPv4 or IPv6. It must be in the subnet specified by <strong>subnet_cidr_id</strong> and can only be bound to the primary NIC of the backend server.</p>
</li></ul>
</td>

View File

@ -266,7 +266,7 @@
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>""</strong>: Any type of backend servers can be added.</p>
</li></ul>
</td>
@ -474,7 +474,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.5.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.5.2.4.1.3 "><p>Specifies the protocol used by the backend server group to receive requests. The value can be <strong>TCP</strong>, <strong>UDP</strong>, <strong>HTTP</strong>, <strong>HTTPS</strong>, or <strong>QUIC</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong> or <strong>QUIC</strong>.</p>
</li><li><p>If the listener's protocol is <strong>TCP</strong>, the protocol of the backend server group must be <strong>TCP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTP</strong>, the protocol of the backend server group must be <strong>HTTP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTPS</strong>, the protocol of the backend server group can be <strong>HTTP</strong> or <strong>HTTPS</strong>.</p>
@ -495,7 +495,9 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.5.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.5.2.4.1.3 "><p>Specifies the IP address version supported by the backend server group.</p>
<p>IPv6 is unsupported. Only <strong>v4</strong> will be returned.</p>
<ul><li><p>Shared load balancers: The value is fixed at <strong>v4</strong>.</p>
</li><li><p>Dedicated load balancers: The value can be <strong>dualstack</strong> or <strong>v4</strong>. If the protocol of the backend server group is TCP or UDP, the value is <strong>dualstack</strong>. If the protocol of the backend server group is HTTP or HTTPS, the value is <strong>v4</strong>.</p>
</li></ul>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.5.2.4.1.1 "><p>slow_start</p>
@ -547,7 +549,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.5.2.4.1.3 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>""</strong>: Any type of backend servers can be added.</p>
</li></ul>
</td>

View File

@ -129,7 +129,7 @@
<p>Note the following when using domain names:</p>
<ul><li><p>The value can contain 0 to 10,000 characters and consists of multiple common domain names or wildcard domain names separated by commas. A maximum of 100 domain names are allowed.</p>
</li><li><p>A common domain name consists of several labels separated by periods (.). Each label can contain a maximum of 63 characters, including letters, digits, and hyphens (-), and must start and end with a letter or digit. Example: www.test.com</p>
</li><li><p>A wildcard domain name is a domain name starts with an asterisk (*). Example: *.test.com</p>
</li><li><p>A wildcard domain name is a domain name starting with an asterisk (*). Example: *.test.com</p>
</li><li><p>This parameter will take effect only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.</p>
</li><li><p>SNI certificates of a shared load balancer's listener can have up to 30 domain names.</p>

View File

@ -123,7 +123,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the domain name that HTTP requests are sent to during the health check.</p>
<p>The value can contain only digits, letters, hyphens (-), and periods (.) and must start with a digit or letter.</p>
<p>The value is left blank by default, indicating that the virtual IP address of the load balancer is used as the destination address of HTTP requests.</p>
<p>This parameter is available only when <strong>type</strong> is set to <strong>HTTP</strong>.</p>
<p>This parameter is available when <strong>type</strong> is set to <strong>HTTP</strong> or <strong>HTTPS</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>expected_codes</p>
@ -254,6 +254,67 @@
<p>This is a new field in this version, and it will not be returned for resources associated with existing dedicated load balancers and for resources associated with existing and new shared load balancers.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>http_version</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the HTTP version used for health checks.</p>
<p>The value can be <strong>HTTP/1.0</strong> or <strong>HTTP/1.1</strong>. By default, this parameter is left blank, indicating that no HTTP version is specified.</p>
<p>Note: This parameter is available only when <strong>type</strong> is set to <strong>HTTP</strong> or <strong>HTTPS</strong>.</p>
<p>This parameter is unsupported. Please do not use it.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>content_check_enable</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies whether to enable health check content verification.</p>
<p>The value can be:</p>
<ul><li><p><strong>true</strong>: Health check content verification will be enabled.</p>
</li><li><p><strong>false</strong> (default): Health check content verification will be disabled.</p>
</li></ul>
<p>Note: This parameter can be enabled only when <strong>type</strong> is set to <strong>TCP</strong> or <strong>UDP_CONNECT</strong>.</p>
<p>This parameter is unsupported. Please do not use it.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>send_content</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the health check content to be sent. ELB sends the configured content and waits for a response from the backend server. If the backend server returns a content that is the same as that defined by <strong>receive_content</strong>, the backend server is considered healthy.</p>
<p>The value can contain:</p>
<ul><li><p>1 to 64 characters if <strong>content_format</strong> is set to <strong>TEXT</strong>. It supports letters, digits, and the following special characters: "!#$%&amp;'()*+,/:;&lt;=&gt;?@[]^-_`{|}~.</p>
</li><li><p>2 to 64 characters if <strong>content_format</strong> is set to <strong>HEX</strong>. The value must have an even number of characters and can contain only hexadecimal characters (09 and AF).</p>
</li></ul>
<p>Note: This parameter only works when <strong>type</strong> is set to <strong>TCP</strong> or <strong>UDP_CONNECT</strong> and <strong>content_check_enable</strong> is set to <strong>true</strong>.</p>
<p>This parameter is unsupported. Please do not use it.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>receive_content</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the health check response content you expect from the backend server. If the backend server returns a content that is the same as that defined by <strong>receive_content</strong>, the backend server is considered healthy.</p>
<p>The value can contain:</p>
<ul><li><p>1 to 64 characters if <strong>content_format</strong> is set to <strong>TEXT</strong>. It supports letters, digits, and the following special characters: "!#$%&amp;'()*+,/:;&lt;=&gt;?@[]^-_`{|}~.</p>
</li><li><p>2 to 64 characters if <strong>content_format</strong> is set to <strong>HEX</strong>. The value must have an even number of characters and can contain only hexadecimal characters (09 and AF).</p>
</li></ul>
<p>Note: This parameter only works when <strong>type</strong> is set to <strong>TCP</strong> or <strong>UDP_CONNECT</strong> and <strong>content_check_enable</strong> is set to <strong>true</strong>.</p>
<p>This parameter is unsupported. Please do not use it.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>content_format</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the health check content format.</p>
<p>The value can be:</p>
<ul><li><p><strong>TEXT</strong>: The content can contain only letters, digits, and the following special characters: "!#$%&amp;'()*+,/:;&lt;=&gt;?@[]^-_`{|}~.</p>
</li><li><p><strong>HEX</strong>: The content can contain only hexadecimal characters (09 and AF).</p>
</li></ul>
<p>This parameter is unsupported. Please do not use it.</p>
</td>
</tr>
</tbody>
</table>
</div>
@ -298,7 +359,14 @@
"type" : "HTTP",
"expected_codes" : "200",
"url_path" : "/",
"http_method" : "GET"
"http_method" : "GET",
"content_check_enable" : false,
"http_version" : null,
"send_content" : null,
"receive_content" : null,
"content_format" : "TEXT",
"created_at" : "2024-08-08T09:00:34Z",
"updated_at" : "2024-08-08T09:00:34Z"
},
"request_id" : "3702e8f0-f5f0-4d35-9097-fc7160005fae"
}</pre>

File diff suppressed because it is too large Load Diff

View File

@ -205,14 +205,14 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>updated_at</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>guaranteed</p>
@ -363,11 +363,11 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend Server</strong>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend</strong>.</p>
<p>If you enable this function, you can add servers in a peer VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</p>
<p>This function is supported only by dedicated load balancers.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend Server</strong>) or <strong>false</strong> (disable <strong>IP as a Backend Server</strong>).</p>
<p>The value can only be update to <strong>true</strong>.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend</strong>) or <strong>false</strong> (disable <strong>IP as a Backend</strong>).</p>
<p>The value can only be updated to <strong>true</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>frozen_scene</p>
@ -404,7 +404,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the information about elastic scaling. If elastic scaling is enabled, the load balancer specifications can be automatically adjusted based on incoming traffic.</p>
<p>Note:</p>
<ul><li><p>This parameter is only available for users on the whitelist.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 7.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 7.</p>
</li></ul>
</td>
</tr>

View File

@ -181,7 +181,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the private IP address bound to the backend server.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend Server</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
</li><li><p>If <strong>subnet_cidr_id</strong> is not left blank, the IP address can be IPv4 or IPv6. It must be in the subnet specified by <strong>subnet_cidr_id</strong> and can only be bound to the primary NIC of the backend server.</p>
</li></ul>
</td>

View File

@ -183,7 +183,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the protocol used by the backend server group to receive requests. The value can be <strong>TCP</strong>, <strong>UDP</strong>, <strong>HTTP</strong>, <strong>HTTPS</strong>, or <strong>QUIC</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong> or <strong>QUIC</strong>.</p>
</li><li><p>If the listener's protocol is <strong>TCP</strong>, the protocol of the backend server group must be <strong>TCP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTP</strong>, the protocol of the backend server group must be <strong>HTTP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTPS</strong>, the protocol of the backend server group can be <strong>HTTP</strong> or <strong>HTTPS</strong>.</p>
@ -204,7 +204,9 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the IP address version supported by the backend server group.</p>
<p>IPv6 is unsupported. Only <strong>v4</strong> will be returned.</p>
<ul><li><p>Shared load balancers: The value is fixed at <strong>v4</strong>.</p>
</li><li><p>Dedicated load balancers: The value can be <strong>dualstack</strong> or <strong>v4</strong>. If the protocol of the backend server group is TCP or UDP, the value is <strong>dualstack</strong>. If the protocol of the backend server group is HTTP or HTTPS, the value is <strong>v4</strong>.</p>
</li></ul>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>slow_start</p>
@ -256,7 +258,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>""</strong>: Any type of backend servers can be added.</p>
</li></ul>
</td>

View File

@ -102,8 +102,9 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.4.2.5.1.3 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the private key of the certificate. The value must be PEM encoded.</p>
<p>Maximum 65,536 character length is allowed, supports certificate chains with a maximum of 11 layers (including certificates and certificate chains).</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the body of the certificate.</p>
<p>The value must be PEM encoded, and can contain a maximum of 65,536 characters.</p>
<p>It supports certificate chains with a maximum of 11 layers (including certificates and certificate chains).</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.4.2.5.1.1 "><p>description</p>
@ -134,7 +135,7 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.4.2.5.1.3 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the private key of the server certificate. The value must be PEM encoded. Maximum 8,192 character length is allowed.</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the private key of the server certificate. The value must be PEM encoded. A maximum of 8,192 characters is allowed.</p>
<ul><li><p>This parameter is valid and mandatory only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>This parameter will not take effect and an error will be returned if <strong>type</strong> is set to <strong>client</strong>.</p>
</li></ul>
@ -150,7 +151,7 @@
<p>Note the following when using domain names:</p>
<ul><li><p>The value can contain 0 to 10,000 characters and consists of multiple common domain names or wildcard domain names separated by commas. A maximum of 100 domain names are allowed.</p>
</li><li><p>A common domain name consists of several labels separated by periods (.). Each label can contain a maximum of 63 characters, including letters, digits, and hyphens (-), and must start and end with a letter or digit. Example: www.test.com</p>
</li><li><p>A wildcard domain name is a domain name starts with an asterisk (*). Example: *.test.com</p>
</li><li><p>A wildcard domain name is a domain name starting with an asterisk (*). Example: *.test.com</p>
</li><li><p>This parameter will take effect only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.</p>
</li><li><p>SNI certificates of a shared load balancer's listener can have up to 30 domain names.</p>
@ -231,7 +232,7 @@
<p>Note the following when using domain names:</p>
<ul><li><p>The value can contain 0 to 10,000 characters and consists of multiple common domain names or wildcard domain names separated by commas. A maximum of 100 domain names are allowed.</p>
</li><li><p>A common domain name consists of several labels separated by periods (.). Each label can contain a maximum of 63 characters, including letters, digits, and hyphens (-), and must start and end with a letter or digit. Example: www.test.com</p>
</li><li><p>A wildcard domain name is a domain name starts with an asterisk (*). Example: *.test.com</p>
</li><li><p>A wildcard domain name is a domain name starting with an asterisk (*). Example: *.test.com</p>
</li><li><p>This parameter will take effect only when <strong>type</strong> is set to <strong>server</strong>.</p>
</li><li><p>SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.</p>
</li><li><p>SNI certificates of a shared load balancer's listener can have up to 30 domain names.</p>
@ -305,7 +306,7 @@
</table>
</div>
</div>
<div class="section"><h4 class="sectiontitle">Example Requests</h4><pre class="screen">PUT https://{ELB_Endponit}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/certificates/233a325e5e3e4ce8beeb320aa714cc12
<div class="section"><h4 class="sectiontitle">Example Requests</h4><pre class="screen">PUT https://{ELB_Endpoint}/v3/99a3fff0d03c428eac3678da6a7d0f24/elb/certificates/233a325e5e3e4ce8beeb320aa714cc12
{
"certificate" : {

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -228,11 +228,11 @@
</td>
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.3 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies whether to enable <strong>IP as a Backend Server</strong>.</p>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies whether to enable <strong>IP as a Backend</strong>.</p>
<p>If you enable this function, you can add servers in a peer VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</p>
<p>This function is supported only by dedicated load balancers.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend Server</strong>) or <strong>false</strong> (disable <strong>IP as a Backend Server</strong>).</p>
<p>The value can only be update to <strong>true</strong>.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend</strong>) or <strong>false</strong> (disable <strong>IP as a Backend</strong>).</p>
<p>The value can only be updated to <strong>true</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.1 "><p>elb_virsubnet_ids</p>
@ -243,7 +243,7 @@
</td>
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.3.4.2.5.1.4 "><p>Specifies the IDs of subnets on the downstream plane. You can query parameter <strong>neutron_network_id</strong> in the response by calling the API (GET https://{VPC_Endpoint}/v1/{project_id}/subnets).</p>
<ul><li><p>If the IDs of the subnets required by the load balancer are specified in <strong>elb_virsubnet_ids</strong>, the subnets will still be bound to the load balancer.</p>
</li><li><p>If the IDs of the subnets required by the load balancer are not specified in <strong>elb_virsubnet_ids</strong>, the subnets will be unbound from the load balancers. Do not unbound the subnets that have been used by the load balancer. Otherwise, an error will be returned.</p>
</li><li><p>If the IDs of the subnets required by the load balancer are not specified in <strong>elb_virsubnet_ids</strong>, the subnets will be unbound from the load balancers. Do not unbind the subnets that have been used by the load balancer. Otherwise, an error will be returned.</p>
</li><li><p>If the IDs of the subnets are specified in <strong>elb_virsubnet_ids</strong>, but not on the downstream plane, a new load balancer will be bound to the downstream plane.</p>
</li></ul>
<p>Note:</p>
@ -482,14 +482,14 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was created, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>updated_at</p>
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd''T''HH:mm:ss''Z''</em>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the time when the load balancer was updated, in the format of <em>yyyy-MM-dd'T'HH:mm:ss'Z'</em>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>guaranteed</p>
@ -640,11 +640,11 @@
</td>
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.2 "><p>Boolean</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend Server</strong>.</p>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies whether to enable <strong>IP as a Backend</strong>.</p>
<p>If you enable this function, you can add servers in a peer VPC connected through a VPC peering connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using their IP addresses.</p>
<p>This function is supported only by dedicated load balancers.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend Server</strong>) or <strong>false</strong> (disable <strong>IP as a Backend Server</strong>).</p>
<p>The value can only be update to <strong>true</strong>.</p>
<p>The value can be <strong>true</strong> (enable <strong>IP as a Backend</strong>) or <strong>false</strong> (disable <strong>IP as a Backend</strong>).</p>
<p>The value can only be updated to <strong>true</strong>.</p>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.4.4.2.4.1.1 "><p>frozen_scene</p>
@ -681,7 +681,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.4.2.4.1.3 "><p>Specifies the information about elastic scaling. If elastic scaling is enabled, the load balancer specifications can be automatically adjusted based on incoming traffic.</p>
<p>Note:</p>
<ul><li><p>This parameter is only available for users on the whitelist.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximmum elastic flavor at Layer 7.</p>
</li><li><p>If elastic scaling is enabled, <strong>l4_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 4. <strong>l7_flavor_id</strong> indicates the ID of the maximum elastic flavor at Layer 7.</p>
</li></ul>
</td>
</tr>

View File

@ -269,7 +269,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the private IP address bound to the backend server.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend Server</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
<ul><li><p>If <strong>subnet_cidr_id</strong> is left blank, <strong>IP as a Backend</strong> is enabled. In this case, the IP address must be an IPv4 address.</p>
</li><li><p>If <strong>subnet_cidr_id</strong> is not left blank, the IP address can be IPv4 or IPv6. It must be in the subnet specified by <strong>subnet_cidr_id</strong> and can only be bound to the primary NIC of the backend server.</p>
</li></ul>
</td>

View File

@ -200,7 +200,7 @@
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.4.4.2.5.1.4 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li></ul>
<p>Note:</p>
<p>This parameter can be updated only when <strong>type</strong> is left blank. And it cannot be updated from a non-empty value to empty value.</p>
@ -433,7 +433,7 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the protocol used by the backend server group to receive requests. The value can be <strong>TCP</strong>, <strong>UDP</strong>, <strong>HTTP</strong>, <strong>HTTPS</strong>, or <strong>QUIC</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong>.</p>
<ul><li><p>If the listener's protocol is <strong>UDP</strong>, the protocol of the backend server group must be <strong>UDP</strong> or <strong>QUIC</strong>.</p>
</li><li><p>If the listener's protocol is <strong>TCP</strong>, the protocol of the backend server group must be <strong>TCP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTP</strong>, the protocol of the backend server group must be <strong>HTTP</strong>.</p>
</li><li><p>If the listener's protocol is <strong>HTTPS</strong>, the protocol of the backend server group can be <strong>HTTP</strong> or <strong>HTTPS</strong>.</p>
@ -454,7 +454,9 @@
<td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.2 "><p>String</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the IP address version supported by the backend server group.</p>
<p>IPv6 is unsupported. Only <strong>v4</strong> will be returned.</p>
<ul><li><p>Shared load balancers: The value is fixed at <strong>v4</strong>.</p>
</li><li><p>Dedicated load balancers: The value can be <strong>dualstack</strong> or <strong>v4</strong>. If the protocol of the backend server group is TCP or UDP, the value is <strong>dualstack</strong>. If the protocol of the backend server group is HTTP or HTTPS, the value is <strong>v4</strong>.</p>
</li></ul>
</td>
</tr>
<tr><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.4.2.4.1.1 "><p>slow_start</p>
@ -506,7 +508,7 @@
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.5.4.2.4.1.3 "><p>Specifies the type of the backend server group.</p>
<p>Values:</p>
<ul><li><p><strong>instance</strong>: Any type of backend servers can be added. <strong>vpc_id</strong> is mandatory.</p>
</li><li><p><strong>ip</strong>: Only IP as Backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>ip</strong>: Only IP as backend servers can be added. <strong>vpc_id</strong> cannot be specified.</p>
</li><li><p><strong>""</strong>: Any type of backend servers can be added.</p>
</li></ul>
</td>

View File

@ -8,20 +8,26 @@
</th>
</tr>
</thead>
<tbody><tr id="elb_xd_0000__row6280153394120"><td class="cellrowborder" valign="top" width="21.17%" headers="mcps1.3.1.1.3.1.1 "><p id="elb_xd_0000__p122801633144115">2025-09-28</p>
<tbody><tr id="elb_xd_0000__row1179675712813"><td class="cellrowborder" valign="top" width="21.17%" headers="mcps1.3.1.1.3.1.1 "><p id="elb_xd_0000__p177969571081">2025-11-18</p>
</td>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p1028083354117">Added the API for deleting a listeners and its associated resources.</p>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p107966574813">Added the following content:</p>
<ul id="elb_xd_0000__ul2096644619113"><li id="elb_xd_0000__li0966646111113">Added parameter <strong id="elb_xd_0000__b1587110411502">http_version</strong>.</li><li id="elb_xd_0000__li387215181312">Added the parameters <strong id="elb_xd_0000__b98834918511">send_content</strong> and <strong id="elb_xd_0000__b4622185165117">receive_content</strong>.</li><li id="elb_xd_0000__li368182051216">Added the support for you to specify the headers to be or not to be recorded in access logs.</li></ul>
</td>
</tr>
<tr id="elb_xd_0000__row6280153394120"><td class="cellrowborder" valign="top" width="21.17%" headers="mcps1.3.1.1.3.1.1 "><p id="elb_xd_0000__p122801633144115">2025-09-28</p>
</td>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p1028083354117">Added the API for deleting a listener and its associated resources.</p>
</td>
</tr>
<tr id="elb_xd_0000__row143711712153415"><td class="cellrowborder" valign="top" width="21.17%" headers="mcps1.3.1.1.3.1.1 "><p id="elb_xd_0000__p1237141210349">2025-09-28</p>
</td>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p113075301342">Modified the following content:</p>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p113075301342">Added the following content:</p>
<p id="elb_xd_0000__p7307630143413">Added the quota management API.</p>
</td>
</tr>
<tr id="elb_xd_0000__row1150714148589"><td class="cellrowborder" valign="top" width="21.17%" headers="mcps1.3.1.1.3.1.1 "><p id="elb_xd_0000__p17508111465812">2025-09-12</p>
</td>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p20508101455820">Modified the following content:</p>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p20508101455820">Added the following content:</p>
<p id="elb_xd_0000__p4604163117584">Added the APIs for cascading deletion.</p>
</td>
</tr>
@ -39,7 +45,7 @@
</tr>
<tr id="elb_xd_0000__row824415415391"><td class="cellrowborder" valign="top" width="21.17%" headers="mcps1.3.1.1.3.1.1 "><p id="elb_xd_0000__p11244154112397">2024-06-07</p>
</td>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p1697712104019">Modified the following content:</p>
<td class="cellrowborder" valign="top" width="78.83%" headers="mcps1.3.1.1.3.1.2 "><p id="elb_xd_0000__p1697712104019">Added the following content:</p>
<p id="elb_xd_0000__p112253011423">Added the APIs for creating, querying, viewing, updating, and deleting logs.</p>
</td>
</tr>