弹性负载均衡 ELB
云服务在IAM预置了常用授权项，称为系统身份策略。如果IAM系统身份策略无法满足授权要求，管理员可以根据各服务支持的授权项，创建IAM自定义身份策略来进行精细的访问控制，IAM自定义身份策略是对系统身份策略的扩展和补充。
除IAM服务外，Organizations服务中的服务控制策略（Service Control Policy，以下简称SCP）也可以使用这些授权项元素设置访问控制策略。
SCP不直接进行授权，只划定权限边界。将SCP绑定到组织单元或者成员账号时，并没有直接对组织单元或成员账号授予操作权限，而是规定了成员账号或组织单元包含的成员账号的授权范围。IAM身份策略授予权限的有效性受SCP限制，只有在SCP允许范围内的权限才能生效。
IAM服务与Organizations服务在使用这些元素进行访问控制时，存在着一些区别，详情请参见：IAM服务与Organizations服务权限访问控制的区别。
本章节介绍IAM服务身份策略授权场景中自定义身份策略和组织服务中SCP使用的元素，这些元素包含了操作（Action）、资源（Resource）和条件（Condition）。
操作（Action）
操作（Action）即为身份策略中支持的授权项。
- “访问级别”列描述如何对操作进行分类（List、Read和Write等）。此分类可帮助您了解在身份策略中相应操作对应的访问级别。
- “资源类型”列指每个操作是否支持资源级权限。
- 资源类型支持通配符号*表示所有。如果此列没有值（-），则必须在身份策略语句的Resource元素中指定所有资源类型（“*”）。
- 如果该列包含资源类型，则必须在具有该操作的语句中指定该资源的URN。
- 资源类型列中必需资源在表中用星号（*）标识，表示使用此操作必须指定该资源类型。
关于ELB定义的资源类型的详细信息请参见资源类型（Resource）。
- “条件键”列包括了可以在身份策略语句的Condition元素中支持指定的键值。
- 如果该授权项资源类型列存在值，则表示条件键仅对列举的资源类型生效。
- 如果该授权项资源类型列没有值（-），则表示条件键对整个授权项生效。
- 如果此列条件键没有值（-），表示此操作不支持指定条件键。
关于ELB定义的条件键的详细信息请参见条件（Condition）。
- “别名”列包括了可以在身份策略中配置的策略授权项。通过这些授权项，可以控制支持策略授权的API访问。详细信息请参见身份策略兼容性说明。
您可以在身份策略语句的Action元素中指定以下ELB的相关操作。
|
授权项 |
描述 |
访问级别 |
资源类型（*为必须） |
条件键 |
别名 |
|---|---|---|---|---|---|
|
elb:flavors:show |
授予查询指定规格的详情。 |
Read |
flavor * |
- |
elb:flavors:get |
|
elb:flavors:list |
授予查询规格详情列表的权限。 |
List |
flavor * |
- |
- |
|
elb:quotas:list |
授予查询配额列表的权限。 |
List |
- |
- |
- |
|
elb:quotas:show |
授予查询可以创建指定类型资源的最大数量的权限。 |
Read |
- |
- |
elb:quotas:get |
|
elb:availability-zones:list |
授予查询可用区列表的权限。 |
List |
availabilityZone * |
- |
- |
|
- |
|||||
|
elb:loadbalancers:list |
授予查询负载均衡器实例列表。 |
List |
loadbalancer * |
- |
- |
|
- |
|||||
|
elb:loadbalancers:show |
授予获取负载均衡器实例详情的权限。 |
Read |
loadbalancer * |
elb:loadbalancers:get |
|
|
elb:loadbalancers:create |
授予创建负载均衡器实例的权限。 |
Write |
loadbalancer * |
- |
- |
|
subnet |
- |
||||
|
- |
|||||
|
elb:loadbalancers:update |
授予更新负载均衡器实例的权限。 |
Write |
subnet |
- |
elb:loadbalancers:put |
|
loadbalancer * |
|||||
|
- |
|||||
|
elb:loadbalancers:delete |
授予删除负载均衡器实例的权限。 |
Write |
loadbalancer * |
- |
|
|
elb:listeners:create |
授予创建监听器的权限。 |
Write |
listener * |
- |
|
|
loadbalancer * |
|||||
|
- |
|||||
|
elb:listeners:update |
授予修改监听器的权限。 |
Write |
listener * |
elb:listeners:put |
|
|
elb:listeners:list |
授予查询监听器列表的权限。 |
List |
listener * |
- |
- |
|
- |
|||||
|
elb:listeners:show |
授予获取监听器详情的权限。 |
Read |
listener * |
elb:listeners:get |
|
|
elb:listeners:delete |
授予删除监听器的权限。 |
Write |
listener * |
- |
|
|
elb:certificates:list |
授予查询证书列表的权限。 |
List |
certificate * |
- |
- |
|
- |
|||||
|
elb:certificates:show |
授予获取证书详情的权限。 |
Read |
certificate * |
- |
elb:certificates:get |
|
elb:certificates:create |
授予创建证书的权限。 |
Write |
certificate * |
- |
- |
|
- |
|||||
|
elb:certificates:update |
授予修改证书的权限。 |
Write |
certificate * |
- |
elb:certificates:put |
|
elb:certificates:delete |
授予删除证书的权限。 |
Write |
certificate * |
- |
- |
|
elb:certificates:setPrivateKeyEcho |
授予设置证书私钥回显开关的权限。 |
Write |
- |
- |
- |
|
elb:certificates:getPrivateKeyEcho |
授予查询证书私钥回显开关的权限。 |
Write |
- |
- |
- |
|
elb:healthmonitors:create |
授予创建健康检查的权限。 |
Write |
healthmonitor * |
- |
|
|
pool * |
|||||
|
elb:healthmonitors:update |
授予修改健康检查的权限。 |
Write |
healthmonitor * |
elb:healthmonitors:put |
|
|
elb:healthmonitors:delete |
授予删除健康检查的权限。 |
Write |
healthmonitor * |
- |
|
|
elb:healthmonitors:show |
授予获取健康检查详情的权限。 |
Read |
healthmonitor * |
elb:healthmonitors:get |
|
|
elb:healthmonitors:list |
授予查询健康检查列表的权限。 |
List |
healthmonitor * |
- |
- |
|
- |
|||||
|
elb:ipgroups:list |
授予查询IP地址组列表的权限。 |
List |
ipgroup * |
- |
- |
|
- |
|||||
|
elb:ipgroups:show |
授予获取IP地址组详情的权限。 |
Read |
ipgroup * |
- |
elb:ipgroups:get |
|
elb:ipgroups:create |
授予创建IP地址组的权限。 |
Write |
ipgroup * |
- |
- |
|
- |
|||||
|
elb:ipgroups:update |
授予修改IP地址组的权限。 |
Write |
ipgroup * |
- |
elb:ipgroups:put |
|
elb:ipgroups:delete |
授予删除IP地址组的权限。 |
Write |
ipgroup * |
- |
- |
|
elb:ipgroups:showRelatedListeners |
授予获取IP地址组关联的监听器的权限。 |
Read |
ipgroup * |
- |
elb:ipgroups:related-listeners |
|
elb:l7policies:create |
授予创建7层转发策略的权限。 |
Write |
listener * |
- |
|
|
l7policy * |
|||||
|
pool |
|||||
|
elb:l7policies:update |
授予修改7层转发策略的权限。 |
Write |
l7policy * |
elb:l7policies:put |
|
|
listener |
|||||
|
pool |
|||||
|
elb:l7policies:delete |
授予删除7层转发策略的权限。 |
Write |
l7policy * |
- |
|
|
elb:l7policies:show |
授予获取转发策略详情的权限。 |
Read |
l7policy * |
elb:l7policies:get |
|
|
elb:l7policies:list |
授予查询转发策略的权限。 |
List |
l7policy * |
- |
- |
|
- |
|||||
|
elb:l7rules:create |
授予创建7层转发规则的权限。 |
Write |
l7rule * |
- |
|
|
l7policy * |
|||||
|
elb:l7rules:update |
授予修改7层转发规则的权限。 |
Write |
l7rule * |
elb:l7rules:put |
|
|
elb:l7rules:list |
授予查询转发规则的权限。 |
List |
l7policy * |
- |
- |
|
l7rule * |
- |
||||
|
- |
|||||
|
elb:l7rules:show |
授予获取7层转发规则详情的权限。 |
Read |
l7rule * |
elb:l7rules:get |
|
|
elb:l7rules:delete |
授予删除7层转发规则的权限。 |
Write |
l7rule * |
- |
|
|
elb:logtanks:list |
授予查询云日志列表的权限。 |
List |
logtank * |
- |
- |
|
- |
|||||
|
elb:logtanks:show |
授予获取云日志详情的权限。 |
Read |
logtank * |
elb:logtanks:get |
|
|
elb:logtanks:create |
授予创建云日志的权限。 |
Write |
logtank * |
- |
|
|
loadbalancer * |
|||||
|
elb:logtanks:update |
授予修改云日志的权限。 |
Write |
logtank * |
elb:logtanks:put |
|
|
elb:logtanks:delete |
授予删除云日志的权限。 |
Write |
logtank * |
- |
|
|
elb:pools:list |
授予查询后端服务器组列表的权限。 |
List |
pool * |
- |
- |
|
- |
|||||
|
elb:pools:show |
授予获取后端服务器组详情的权限。 |
Read |
pool * |
elb:pools:get |
|
|
elb:pools:create |
授予创建后端服务器组的权限。 |
Write |
loadbalancer |
- |
|
|
listener |
|||||
|
pool * |
|||||
|
elb:pools:update |
授予修改后端服务器组的权限。 |
Write |
pool * |
elb:pools:put |
|
|
elb:pools:delete |
授予删除后端服务器组的权限。 |
Write |
pool * |
- |
|
|
elb:members:list |
授予查询后端服务器列表的权限。 |
List |
pool |
- |
- |
|
member * |
- |
||||
|
- |
|||||
|
elb:members:show |
授予获取后端服务器详情的权限。 |
Read |
member * |
elb:members:get |
|
|
elb:members:create |
授予创建后端服务器的权限。 |
Write |
member * |
- |
|
|
pool * |
|||||
|
subnet |
- |
||||
|
elb:members:update |
授予修改后端服务器的权限。 |
Write |
member * |
elb:members:put |
|
|
elb:members:delete |
授予删除后端服务器的权限。 |
Write |
member * |
- |
|
|
elb:security-policies:list |
授予查询安全策略的权限。 |
List |
securityPolicy * |
- |
- |
|
- |
|||||
|
elb:security-policies:show |
授予获取安全策略详情的权限。 |
Read |
securityPolicy * |
- |
elb:security-policies:get |
|
elb:security-policies:create |
授予创建安全策略的权限。 |
Write |
securityPolicy * |
- |
- |
|
- |
|||||
|
elb:security-policies:update |
授予修改安全策略的权限。 |
Write |
securityPolicy * |
- |
elb:security-policies:put |
|
elb:security-policies:delete |
授予删除安全策略的权限。 |
Write |
securityPolicy * |
- |
- |
|
elb:loadbalancers:export |
授予导出负载均衡器的权限。 |
Read |
loadbalancer * |
- |
|
|
elb:listeners:export |
授予导出监听器的权限。 |
Read |
listener * |
- |
ELB的API通常对应着一个或多个授权项。表2展示了API与授权项的关系，以及该API需要依赖的授权项。
|
API |
对应的授权项 |
依赖的授权项 |
|---|---|---|
|
GET /v3/{project_id}/elb/flavors |
elb:flavors:list |
- |
|
GET /v3/{project_id}/elb/flavors/{flavor_id} |
elb:flavors:show |
- |
|
GET /v3/{project_id}/elb/quotas/details |
elb:quotas:list |
- |
|
GET /v3/{project_id}/elb/quotas |
elb:quotas:show |
- |
|
POST /v3/{project_id}/elb/loadbalancers |
elb:loadbalancers:create |
- |
|
DELETE /v3/{project_id}/elb/loadbalancers/{loadbalancer_id} |
elb:loadbalancers:delete |
- |
|
DELETE /v3/{project_id}/elb/loadbalancers/{loadbalancer_id}/force-elb |
elb:loadbalancers:delete |
- |
|
GET /v3/{project_id}/elb/loadbalancers |
elb:loadbalancers:list |
- |
|
GET /v3/{project_id}/elb/loadbalancers/{loadbalancer_id} |
elb:loadbalancers:show |
- |
|
GET /v3/{project_id}/elb/loadbalancers/{loadbalancer_id}/statuses |
elb:loadbalancers:show |
- |
|
PUT /v3/{project_id}/elb/loadbalancers/{loadbalancer_id} |
elb:loadbalancers:update |
- |
|
POST /v3/{project_id}/elb/loadbalancers/{loadbalancer_id}/availability-zone/batch-remove |
elb:loadbalancers:update |
- |
|
POST /v3/{project_id}/elb/loadbalancers/{loadbalancer_id}/availability-zone/batch-add |
elb:loadbalancers:update |
- |
|
POST /v3/{project_id}/elb/loadbalancers/change-charge-mode |
elb:loadbalancers:create |
- |
|
POST /v3/{project_id}/elb/ipgroups |
elb:ipgroups:create |
- |
|
DELETE /v3/{project_id}/elb/ipgroups/{ipgroup_id} |
elb:ipgroups:delete |
- |
|
GET /v3/{project_id}/elb/ipgroups |
elb:ipgroups:list |
- |
|
GET /v3/{project_id}/elb/ipgroups/{ipgroup_id} |
elb:ipgroups:show |
- |
|
PUT /v3/{project_id}/elb/ipgroups/{ipgroup_id} |
elb:ipgroups:update |
- |
|
POST /v3/{project_id}/elb/ipgroups/{ipgroup_id}/iplist/create-or-update |
elb:ipgroups:update |
- |
|
POST /v3/{project_id}/elb/ipgroups/{ipgroup_id}/iplist/batch-delete |
elb:ipgroups:update |
- |
|
GET /v3/{project_id}/elb/ipgroups/{ipgroup_id}/related-listeners |
elb:ipgroups:showRelatedListeners |
- |
|
POST /v3/{project_id}/elb/security-policies |
elb:security-policies:create |
- |
|
DELETE /v3/{project_id}/elb/security-policies/{security_policy_id} |
elb:security-policies:delete |
- |
|
GET /v3/{project_id}/elb/security-policies |
elb:security-policies:list |
- |
|
GET /v3/{project_id}/elb/system-security-policies |
elb:security-policies:list |
- |
|
GET /v3/{project_id}/elb/security-policies/{security_policy_id} |
elb:security-policies:show |
- |
|
PUT /v3/{project_id}/elb/security-policies/{security_policy_id} |
elb:security-policies:update |
- |
|
POST /v3/{project_id}/elb/pools/{pool_id}/members |
elb:members:create |
- |
|
DELETE /v3/{project_id}/elb/pools/{pool_id}/members/{member_id} |
elb:members:delete |
- |
|
GET /v3/{project_id}/elb/pools/{pool_id}/members |
elb:members:list |
- |
|
GET /v3/{project_id}/elb/pools/{pool_id}/members/{member_id} |
elb:members:show |
- |
|
PUT /v3/{project_id}/elb/pools/{pool_id}/members/{member_id} |
elb:members:update |
- |
|
POST /v3/{project_id}/elb/pools/{pool_id}/members/batch-update |
elb:members:update |
- |
|
GET /v3/{project_id}/elb/members |
elb:members:list |
- |
|
POST /v3/{project_id}/elb/pools/{pool_id}/members/batch-add |
elb:members:create |
- |
|
POST /v3/{project_id}/elb/pools/{pool_id}/members/batch-delete |
elb:members:delete |
- |
|
POST /v3/{project_id}/elb/pools |
elb:pools:create |
- |
|
DELETE /v3/{project_id}/elb/pools/{pool_id} |
elb:pools:delete |
- |
|
GET /v3/{project_id}/elb/pools |
elb:pools:list |
- |
|
GET /v3/{project_id}/elb/pools/{pool_id} |
elb:pools:show |
- |
|
PUT /v3/{project_id}/elb/pools/{pool_id} |
elb:pools:update |
- |
|
POST /v3/{project_id}/elb/master-slave-pools |
elb:pools:create |
- |
|
GET /v3/{project_id}/elb/master-slave-pools |
elb:pools:list |
- |
|
GET /v3/{project_id}/elb/master-slave-pools/{pool_id} |
elb:pools:show |
- |
|
DELETE /v3/{project_id}/elb/master-slave-pools/{pool_id} |
elb:pools:delete |
- |
|
POST /v3/{project_id}/elb/listeners |
elb:listeners:create |
- |
|
DELETE /v3/{project_id}/elb/listeners/{listener_id} |
elb:listeners:delete |
- |
|
DELETE /v3/{project_id}/elb/listeners/{listener_id}/force |
elb:listeners:delete |
- |
|
GET /v3/{project_id}/elb/listeners |
elb:listeners:list |
- |
|
GET /v3/{project_id}/elb/listeners/{listener_id} |
elb:listeners:show |
- |
|
PUT /v3/{project_id}/elb/listeners/{listener_id} |
elb:listeners:update |
- |
|
POST /v3/{project_id}/elb/healthmonitors |
elb:healthmonitors:create |
- |
|
DELETE /v3/{project_id}/elb/healthmonitors/{healthmonitor_id} |
elb:healthmonitors:delete |
- |
|
GET /v3/{project_id}/elb/healthmonitors |
elb:healthmonitors:list |
- |
|
GET /v3/{project_id}/elb/healthmonitors/{healthmonitor_id} |
elb:healthmonitors:show |
- |
|
PUT /v3/{project_id}/elb/healthmonitors/{healthmonitor_id} |
elb:healthmonitors:update |
- |
|
GET /v3/{project_id}/elb/availability-zones |
elb:availability-zones:list |
- |
|
GET /v3/{project_id}/elb/preoccupy-ip-num |
elb:loadbalancers:show |
- |
|
POST /v3/{project_id}/elb/logtanks |
elb:logtanks:create |
- |
|
DELETE /v3/{project_id}/elb/logtanks/{logtank_id} |
elb:logtanks:delete |
- |
|
GET /v3/{project_id}/elb/logtanks |
elb:logtanks:list |
- |
|
GET /v3/{project_id}/elb/logtanks/{logtank_id} |
elb:logtanks:show |
- |
|
PUT /v3/{project_id}/elb/logtanks/{logtank_id} |
elb:logtanks:update |
- |
|
POST /v3/{project_id}/elb/certificates |
elb:certificates:create |
- |
|
DELETE /v3/{project_id}/elb/certificates/{certificate_id} |
elb:certificates:delete |
- |
|
GET /v3/{project_id}/elb/certificates |
elb:certificates:list |
- |
|
GET /v3/{project_id}/elb/certificates/{certificate_id} |
elb:certificates:show |
- |
|
PUT /v3/{project_id}/elb/certificates/{certificate_id} |
elb:certificates:update |
- |
|
POST /v3/{project_id}/elb/certificates/settings/private-key-echo |
elb:certificates:setPrivateKeyEcho |
- |
|
GET /v3/{project_id}/elb/certificates/settings/private-key-echo |
elb:certificates:getPrivateKeyEcho |
- |
|
POST /v3/{project_id}/elb/l7policies |
elb:l7policies:create |
- |
|
DELETE /v3/{project_id}/elb/l7policies/{l7policy_id} |
elb:l7policies:delete |
- |
|
GET /v3/{project_id}/elb/l7policies |
elb:l7policies:list |
- |
|
GET /v3/{project_id}/elb/l7policies/{l7policy_id} |
elb:l7policies:show |
- |
|
PUT /v3/{project_id}/elb/l7policies/{l7policy_id} |
elb:l7policies:update |
- |
|
POST /v3/{project_id}/elb/l7policies/batch-update-priority |
elb:l7policies:update |
- |
|
POST /v3/{project_id}/elb/l7policies/{l7policy_id}/rules |
elb:l7rules:create |
- |
|
DELETE /v3/{project_id}/elb/l7policies/{l7policy_id}/rules/{l7rule_id} |
elb:l7rules:delete |
- |
|
GET /v3/{project_id}/elb/l7policies/{l7policy_id}/rules |
elb:l7rules:list |
- |
|
GET /v3/{project_id}/elb/l7policies/{l7policy_id}/rules/{l7rule_id} |
elb:l7rules:show |
- |
|
PUT /v3/{project_id}/elb/l7policies/{l7policy_id}/rules/{l7rule_id} |
elb:l7rules:update |
- |
资源类型（Resource）
资源类型（Resource）表示身份策略所作用的资源。如表3中的某些操作指定了可以在该操作指定的资源类型，则必须在具有该操作的身份策略语句中指定该资源的URN，身份策略仅作用于此资源；如未指定，Resource默认为“*”，则身份策略将应用到所有资源。您也可以在身份策略中设置条件，从而指定资源类型。
ELB定义了以下可以在自定义身份策略的Resource元素中使用的资源类型。
|
资源类型 |
URN |
|---|---|
|
pool |
elb:<region>:<account-id>:pool:<pool-id> |
|
loadbalancer |
elb:<region>:<account-id>:loadbalancer:<loadbalancer-id> |
|
certificate |
elb:<region>:<account-id>:certificate:<certificate-id> |
|
healthmonitor |
elb:<region>:<account-id>:healthmonitor:<healthmonitor-id> |
|
ipgroup |
elb:<region>:<account-id>:ipgroup:<ipgroup-id> |
|
securityPolicy |
elb:<region>:<account-id>:securityPolicy:<security-policy-id> |
|
logtank |
elb:<region>:<account-id>:logtank:<logtank-id> |
|
availabilityZone |
elb:<region>:<account-id>:availabilityZone:<availability-zone-id> |
|
member |
elb:<region>:<account-id>:member:<pool-id>/<member-id> |
|
l7policy |
elb:<region>:<account-id>:l7policy:<l7policy-id> |
|
l7rule |
elb:<region>:<account-id>:l7rule:<l7policy-id>/<l7rule-id> |
|
flavor |
elb:<region>:<account-id>:flavor:<flavor-id> |
|
subnet |
vpc:<region>:<account-id>:subnet:<subnet-id> |
|
listener |
elb:<region>:<account-id>:listener:<listener-id> |
条件（Condition）
条件键概述
条件（Condition）是身份策略生效的特定条件，包括条件键和运算符。
- 条件键表示身份策略语句的Condition元素中的键值。根据适用范围，分为全局级条件键和服务级条件键。
- 全局级条件键（前缀为g:）适用于所有操作，在鉴权过程中，云服务不需要提供用户身份信息，系统将自动获取并鉴权。详情请参见：全局条件键。
- 服务级条件键（前缀通常为服务缩写，如elb:）仅适用于对应服务的操作，详情请参见表4。
- 单值/多值表示API调用时请求中与条件关联的值数。单值条件键在API调用时的请求中最多包含一个值，多值条件键在API调用时请求可以包含多个值。例如：g:SourceVpce是单值条件键，表示仅允许通过某个VPC终端节点发起请求访问某资源，一个请求最多包含一个VPC终端节点ID值。g:TagKeys是多值条件键，表示请求中携带的所有标签的key组成的列表，当用户在调用API请求时传入标签可以传入多个值。
- 运算符与条件键、条件值一起构成完整的条件判断语句，当请求信息满足该条件时，身份策略才能生效。支持的运算符请参见：运算符。
ELB支持的服务级条件键
ELB定义了以下可以在自定义身份策略的Condition元素中使用的条件键，您可以使用这些条件键进一步细化身份策略语句应用的条件。
