Elastic Load Balance (ELB)

The Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

This section describes the elements used by Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an SCP.
The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions, and you must specify all resources ("*") in your SCP statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your policy statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resource types defined by ELB, see Resources.
The Condition Key column contains keys that you can specify in the Condition element of an SCP statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by ELB, see Conditions.

The following table lists the actions that you can define in SCP statements for ELB.

**Table 1** Actions supported by ELB
Action	Description	Access Level	*Resource Type (: Required)**	Condition Key
elb:flavors:show	Grants permission to query a given flavor.	read	flavor *	-
elb:flavors:list	Grants permission to query flavors.	list	flavor *	-
elb:quotas:list	Grants permission to query quotas.	list	-	-
elb:quotas:show	Grants permission to query the maximum number of resources of a specified type that can be created.	read	-	-
elb:availability-zones:list	Grants permission to query AZs.	list	availabilityZone *	-
elb:availability-zones:list	Grants permission to query AZs.	list	-	g:EnterpriseProjectId
elb:loadbalancers:list	Grants permission to query load balancers.	list	loadbalancer *	-
elb:loadbalancers:list	Grants permission to query load balancers.	list	-	g:EnterpriseProjectId
elb:loadbalancers:show	Grants permission to query the details of a load balancer.	read	loadbalancer *	g:ResourceTag/<tag-key> g:EnterpriseProjectId
elb:loadbalancers:create	Grants permission to create a load balancer.	write	loadbalancer *	-
			subnet	-
			-	g:RequestTag/<tag-key> g:TagKeys g:EnterpriseProjectId elb:AssociatePublicips
elb:loadbalancers:update	Grants permission to modify a load balancer.	write	subnet	-
elb:loadbalancers:update	Grants permission to modify a load balancer.	write	loadbalancer *	g:ResourceTag/<tag-key> g:EnterpriseProjectId elb:AssociatePublicips
elb:loadbalancers:delete	Grants permission to delete a load balancer.	write	loadbalancer *	g:ResourceTag/<tag-key> g:EnterpriseProjectId
elb:listeners:create	Grants permission to add a listener.	write	listener *	g:EnterpriseProjectId
			loadbalancer *	g:ResourceTag/<tag-key> g:EnterpriseProjectId
			-	g:RequestTag/<tag-key> g:TagKeys
elb:listeners:update	Grants permission to modify a listener.	write	listener *	g:ResourceTag/<tag-key> g:EnterpriseProjectId
elb:listeners:list	Grants permission to query listeners.	list	listener *	-
elb:listeners:list	Grants permission to query listeners.	list	-	g:EnterpriseProjectId
elb:listeners:show	Grants permission to query the details of a listener.	read	listener *	g:ResourceTag/<tag-key> g:EnterpriseProjectId
elb:listeners:delete	Grants permission to delete a listener.	write	listener *	g:ResourceTag/<tag-key> g:EnterpriseProjectId
elb:certificates:list	Grants permission to query certificates.	list	certificate *	-
elb:certificates:list	Grants permission to query certificates.	list	-	g:EnterpriseProjectId
elb:certificates:show	Grants permission to query the details of a certificate.	read	certificate *	-
elb:certificates:create	Grants permission to add a certificate.	write	certificate *	-
elb:certificates:create	Grants permission to add a certificate.	write	-	g:EnterpriseProjectId
elb:certificates:update	Grants permission to modify a certificate.	write	certificate *	-
elb:certificates:delete	Grants permission to delete a certificate.	write	certificate *	-
elb:certificates:setPrivateKeyEcho	Grants permission to enable or disable the private key feature.	write	-	-
elb:certificates:getPrivateKeyEcho	Grants permission to query whether the private key feature is enabled.	write	-	-
elb:agreements:list	Grants permission to query signing records.	list	agreement *	-
elb:agreements:show	Grants permission to obtain signing information details.	read	agreement *	-
elb:agreements:create	Grants permission to create signing records.	write	agreement *	-
elb:agreements:update	Grants permission to modify signing records.	write	agreement *	-
elb:healthmonitors:create	Grants permission to configure a health check.	write	healthmonitor *	g:EnterpriseProjectId
elb:healthmonitors:create	Grants permission to configure a health check.	write	pool *	g:EnterpriseProjectId
elb:healthmonitors:update	Grants permission to modify a health check.	write	healthmonitor *	g:EnterpriseProjectId
elb:healthmonitors:delete	Grants permission to delete a health check.	write	healthmonitor *	g:EnterpriseProjectId
elb:healthmonitors:show	Grants permission to query health check details.	read	healthmonitor *	g:EnterpriseProjectId
elb:healthmonitors:list	Grants permission to query health checks.	list	healthmonitor *	-
elb:healthmonitors:list	Grants permission to query health checks.	list	-	g:EnterpriseProjectId
elb:ipgroups:list	Grants permission to query IP address groups.	list	ipgroup *	-
elb:ipgroups:list	Grants permission to query IP address groups.	list	-	g:EnterpriseProjectId
elb:ipgroups:show	Grants permission to query the details of an IP address group.	read	ipgroup *	-
elb:ipgroups:create	Grants permission to create an IP address group.	write	ipgroup *	-
elb:ipgroups:create	Grants permission to create an IP address group.	write	-	g:EnterpriseProjectId
elb:ipgroups:update	Grants permission to modify an IP address group.	write	ipgroup *	-
elb:ipgroups:delete	Grants permission to delete an IP address group.	write	ipgroup *	-
elb:l7policies:create	Grants permission to add a forwarding policy to HTTP or HTTPS listeners.	write	listener *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
			l7policy *	g:EnterpriseProjectId
			pool	g:EnterpriseProjectId
elb:l7policies:update	Grants permission to modify a forwarding policy.	write	l7policy *	g:EnterpriseProjectId
			listener	g:EnterpriseProjectId g:ResourceTag/<tag-key>
			pool	g:EnterpriseProjectId
elb:l7policies:delete	Grants permission to delete a forwarding policy.	write	l7policy *	g:EnterpriseProjectId
elb:l7policies:show	Grants permission to query the details of a forwarding policy.	read	l7policy *	g:EnterpriseProjectId
elb:l7policies:list	Grants permission to query forwarding policies.	list	l7policy *	-
elb:l7policies:list	Grants permission to query forwarding policies.	list	-	g:EnterpriseProjectId
elb:l7rules:create	Grants permission to add a forwarding rule.	write	l7rule *	g:EnterpriseProjectId
elb:l7rules:create	Grants permission to add a forwarding rule.	write	l7policy *	g:EnterpriseProjectId
elb:l7rules:update	Grants permission to modify a forwarding rule.	write	l7rule *	g:EnterpriseProjectId
elb:l7rules:list	Grants permission to query forwarding rules.	list	l7policy *	-
			l7rule *	-
			-	g:EnterpriseProjectId
elb:l7rules:show	Grants permission to query the details of a forwarding rule.	read	l7rule *	g:EnterpriseProjectId
elb:l7rules:delete	Grants permission to delete a forwarding rule.	write	l7rule *	g:EnterpriseProjectId
elb:logtanks:list	Grants permission to query logs.	list	logtank *	-
elb:logtanks:list	Grants permission to query logs.	list	-	g:EnterpriseProjectId
elb:logtanks:show	Grants permission to query the details of a log.	read	logtank *	g:EnterpriseProjectId
elb:logtanks:create	Grants permission to create a log.	write	logtank *	g:EnterpriseProjectId
elb:logtanks:create	Grants permission to create a log.	write	loadbalancer *	g:EnterpriseProjectId g:ResourceTag/<tag-key>
elb:logtanks:update	Grants permission to modify a log.	write	logtank *	g:EnterpriseProjectId
elb:logtanks:delete	Grants permission to delete a log.	write	logtank *	g:EnterpriseProjectId
elb:pools:list	Grants permission to query backend server groups.	list	pool *	-
elb:pools:list	Grants permission to query backend server groups.	list	-	g:EnterpriseProjectId
elb:pools:show	Grants permission to query the details of a backend server group.	read	pool *	g:EnterpriseProjectId
elb:pools:create	Grants permission to create a backend server group.	write	loadbalancer	g:EnterpriseProjectId g:ResourceTag/<tag-key>
			listener	g:EnterpriseProjectId g:ResourceTag/<tag-key>
			pool *	g:EnterpriseProjectId
elb:pools:update	Grants permission to modify a backend server group.	write	pool *	g:EnterpriseProjectId
elb:pools:delete	Grants permission to delete a backend server group.	write	pool *	g:EnterpriseProjectId
elb:members:list	Grants permission to query backend servers.	list	pool	-
			member *	-
			-	g:EnterpriseProjectId
elb:members:show	Grants permission to query the details of a backend server.	read	member *	g:EnterpriseProjectId
elb:members:create	Grants permission to add a backend server.	write	member *	g:EnterpriseProjectId
			pool *	g:EnterpriseProjectId
			subnet	-
elb:members:update	Grants permission to modify the configurations of a backend server.	write	member *	g:EnterpriseProjectId
elb:members:delete	Grants permission to remove a backend server.	write	member *	g:EnterpriseProjectId
elb:security-policies:list	Grants permission to query security policies.	list	securityPolicy *	-
elb:security-policies:list	Grants permission to query security policies.	list	-	g:EnterpriseProjectId
elb:security-policies:show	Grants permission to query the details of a security policy.	read	securityPolicy *	-
elb:security-policies:create	Grants permission to create a security policy.	write	securityPolicy *	-
elb:security-policies:create	Grants permission to create a security policy.	write	-	g:EnterpriseProjectId
elb:security-policies:update	Grants permission to modify a security policy.	write	securityPolicy *	-
elb:security-policies:delete	Grants permission to delete a security policy.	write	securityPolicy *	-

Each ELB API usually supports one or more actions. Table 2 lists the supported actions and dependencies.

**Table 2** Actions and dependencies supported by ELB APIs
API	Action	Dependencies
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/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	-
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/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	-

Resources

A resource type indicates the resources that an SCP applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the SCP statements using that action, and the SCP applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the SCP applies to all resources. You can also set condition keys in an SCP to define resource types.

The following table lists the resource types that you can define in SCP statements for ELB.

**Table 3** Resource types supported by ELB
Resource Type	URN
pool	elb:<region>:<account-id>:pool:<pool-id>
agreement	elb:<region>:<account-id>:agreement:<agreement-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>

Conditions

A Condition element lets you specify conditions for when an SCP is in effect. It contains condition keys and operators.

A key in the Condition element of a statement can be a global condition key or a service-specific condition key.
- Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
- Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, elb:) apply only to operations of ELB. For details, see Table 4.
- The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
A condition operator, condition key, and a condition value together constitute a complete condition statement. An SCP can be applied only when its request conditions are met. For details about the supported operators, see operators.

The following table lists the condition keys that you can define in SCPs for ELB. You can include these condition keys to specify conditions for when your SCP is in effect.

**Table 4** Service-specific condition keys supported by ELB
Service-specific Condition Key	Type	Single-valued/Multivalued	Description
elb:AssociatePublicips	boolean	Single valued	Filters access by whether an EIP is bound during load balancer creation or modification. If you want to control the public network access of a load balancer, you need to use the actions supported by EIP.