UpdateLoadBalancer_边缘安全加速_API文档

插件下载了解更多
VS Code 插件
安装插件之前,确保已安装 VS Code安装插件之前,确保已安装 VS Code
Alibaba Cloud Developer Toolkit is a collection of extensions that can help access Alibaba Cloud services in Visual Studio Code.
JetBrains 插件
安装插件之前,确保已安装 JetBrains IDE安装插件之前,确保已安装 JetBrains IDE
The Alibaba Cloud Developer Toolkit for JetBrains makes it easier to access Alibaba Cloud services.

接口说明

通过此接口,您可以修改负载均衡器的多项配置,包括但不限于负载均衡器的名称、是否开启加速、会话保持策略、以及与流量路由相关的各种高级设置。

注意 某些参数的更改可能会影响现有服务的稳定性,请谨慎操作。

流控信息

当前云产品API请求速率暂未透出。

授权信息

如下是此API对应的授权信息,用于RAM权限策略语句的Action元素中,为RAM用户或RAM角色授予调用此API的权限。请通过 RAM 访问控制设置,使用方法可参考访问控制帮助文档

具体说明如下:展开详情

操作访问级别资源类型条件关键字关联操作
esa:UpdateLoadBalancer
Update
Site
acs:esa:{#regionId}:{#accountId}:site/{#SiteId}

请求参数

字段名称字段详情
Enabledboolean

负载均衡器是否启用。展开详情

示例值:true枚举值:truefalse
SiteIdinteger<int64>

站点 ID,可通过调用 ListSites 接口获取。

注意 该字段类型为 Long,在序列化/反序列化的过程中可能导致精度丢失,请注意数值不得大于 9007199254740991。
示例值:1159101787****参考取值来源:
    ListSites
    CreateSite
AdaptiveRoutingobject

跨地址池回源配置。

DefaultPoolsarray<integer<int64>>

默认地址池 ID 列表。

FallbackPoolinteger<int64>

兜底地址池 ID,当所有其他池不可用时,流量将被导向此处。

注意 该字段类型为 Long,在序列化/反序列化的过程中可能导致精度丢失,请注意数值不得大于 9007199254740991。
示例值:96228666776****
RandomSteeringobject

加权轮询配置,用于控制不同地址池的流量分配权重。

Rulesarray<object>

规则配置列表,用于定义特定条件下的行为覆盖。

SessionAffinitystring

会话保持,取值:展开详情

示例值:ip枚举值:
SteeringPolicystring

负载均衡策略。

示例值:order
Descriptionstring

负载均衡器的详细描述信息,便于管理和识别。

示例值:负载均衡器描述
Ttlinteger<int32>

TTL 值,DNS 记录的生存时间,默认为 30,取值范围:10-600。

示例值:300
Monitorobject

监视器配置,用于健康检查。

Idinteger<int64>

负载均衡器 ID,可通过调用 ListLoadBalancers 接口获取。

注意 该字段类型为 Long,在序列化/反序列化的过程中可能导致精度丢失,请注意数值不得大于 9007199254740991。
示例值:95913670174****
RegionPoolsany

一级 region 对应的地址池。

示例值:{ "ENAM": [ 12345678**** ], "WNAM": [ 23456789****, 23456789**** ] }
SubRegionPoolsany

二级 region 对应的地址池,多个二级 region 共用一批地址池时,可以多个二级 region,使用逗号拼接作为 key。

示例值:{"AL,MO": [92298024898****],"CN-SH,CN-SX,CN-SC":[92304347804****,92843536908****]}

返回参数

字段名称字段详情
RequestIdstring

请求 ID。

示例值:EEEBE525-F576-1196-8DAF-2D70CA3F4D2F

返回示例

错误码

全局错误码
HTTP 状态码错误码错误信息操作
400
InvalidParameter
The specified parameter is invalid.诊断
400
LoadBalancerQuotaCheckFailed
Load balancer enable quota check failed.诊断
400
LoadBalancerNumberExceedQuotaLimit
The number of load balancers you have added has reached the limit of the plan quota. Please delete the unused load balancers or upgrade the plan and try again.诊断
400
LoadBalancerRuleQuotaCheckFailed
Your current plan does not support configuring load balancer custom rules, or the load balancer rules you have added exceed the plan quota limit. Please upgrade the plan or delete the rules that are no longer in use and try again.诊断
400
LoadBalancerPolicyCheckFailed
Your current plan does not support the load balancer scheduling policy. Upgrade the plan and try again.诊断
400
LoadBalancerHealthDetectionQuotaCheckFailed
Your current plan does not allow you to configure the load balancer's health detection. Upgrade the plan and try again.诊断
400
LoadBalancerHealthDetectionIntervalCheckFailed
The configured load balancer health detection interval exceeds the quota range allowed by the plan. Please revise the interval within the range or upgrade the plan and try again.诊断
400
InternalException
Failed to call the service. Try again later or contact technical support.诊断
400
Instance.NotOnline
Your plan is unavailable due to an overdue payment. Complete the payment first.诊断
400
MonitorExpectedBodyInvalid
Invalid response body. Specify a response body that does not exceed 102,400 characters in length in your custom rule.诊断
400
MonitorExpectedCodesInvalid
Invalid expected status code for the probe.Make sure that you specify no more than 10 status codes in the probe settings, and each status code must be 3 to 4 characters in length.Examples: 200, 301, 3xx, 8000, and 88xx.诊断
400
MonitorHeaderInvalid
Invalid request header for the probe. You can add up to 10 request headers, each with 1 to 9 values. The combined length of all headers and values cannot exceed 6,000 characters. You cannot configure the User-Agent header.诊断
400
MonitorMethodNotSupport
Invalid HTTP method for the probe request. Valid values are GET and HEAD.诊断
400
MonitorPathNotSupport
Invalid probe URL path.If you set the probe protocol to HTTP or HTTPS, make sure you specify a probe URL path that does not exceed 1,024 characters in length.诊断
400
MonitorPortNotSupport
Invalid probe port. Specify a valid port from 1 to 65535 for the probe request. Then, try again.诊断
400
MonitorRetriesInvalid
Invalid number of probe retries. Specify an integer from 0 to 5. Then, try again.诊断
400
MonitorTimeoutInvalid
Invalid timeout for the probe. Valid values are 1 to 10.诊断
400
MonitorTypeNotSupport
Invalid protocol. Valid values are off, HTTP, HTTPS, TCP, UDP, ICMP Ping, and SMTP.诊断
400
OriginPoolNotExist
The specified origin pool does not exist or does not belong to your account or website. Check and try again.诊断
400
LoadBalancerNameConflict
The load balancer name or the hostname for the origin pool already exists. Try again with a unique name.诊断
400
LockFailed
The system is handling requests you previously submitted. Try again later.诊断
400
SourceCircleExist
The host record of the resource to be operated on is already the source station of another resource, or the source station of the current resource has been added as a host record. To avoid loopback, modify the host record or source station and retry.诊断
400
LoadBalancerNotExist
The specified load balancer name is invalid or load balancing is not enabled for your website.Make sure that you specify a valid load balancer name and load balancing is enabled. Then, try again.诊断
403
QuotaExceeded
The quota is exceeded.诊断
404
SiteNotFound
The website does not exist or does not belong to you.诊断

变更历史

变更时间变更内容概要操作
2025-02-13
删除请求参数SessionAffinityAttributes
新增请求参数Enabled
2025-02-07
新增OpenAPI,修改已有负载均衡器信息

相关示例