AssociateAclsWithListener - Global Accelerator - Alibaba Cloud Documentation Center

Associates access control lists (ACLs) with a listener.

Operation description

Description

AssociateAclsWithListener is an asynchronous operation. After you send a request, the system returns a request ID, but the operation is still being performed in the system background. You can call the DescribeListener operation to query the state of the listener with which you attempt to associate an ACL.
- If the listener is in the updating state, it indicates that the ACL is being associated. In this case, you can perform only query operations.
- If the listener is in the active state, it indicates that the ACL is associated.
The AssociateAclsWithListener operation cannot be called repeatedly for the same Global Accelerator (GA) instance within a specific period of time.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
ga:AssociateAclsWithListener	Write	Listener acs:ga:{#regionId}:{#accountId}:listener/{#ListenerId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region ID of the Global Accelerator (GA) instance. Set the value to cn-hangzhou.	cn-hangzhou
AclIds	array	Yes	The ID of the ACL. You can associate up to two ACL IDs.
	string	Yes	The ID of the ACL. You can associate up to two ACL IDs.	nacl-hp34s2h0xx1ht4nwo****
ListenerId	string	Yes	The listener ID. Only intelligent routing listeners support ACLs.	lsr-bp1bpn0kn908w4nbw****
AclType	string	Yes	The type of the ACL. Valid values: white: Only requests from the IP addresses or CIDR blocks in the ACL are forwarded. Whitelists are suitable for scenarios in which you want to allow access from specific IP addresses to an application. If a whitelist is improperly configured, risks may arise. After a whitelist is configured for a listener, only requests from the IP addresses that are added to the whitelist are distributed by the listener. If a whitelist is enabled but no IP address is added to the whitelist, the listener forwards all requests. black: All requests from the IP addresses or CIDR blocks in the ACL are rejected. Blacklists are suitable for scenarios in which you want to deny access from specific IP addresses to an application. If the blacklist is enabled but no IP addresses are added to the ACL, the listener forwards all requests.	White
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.	02fb3da4****
DryRun	boolean	No	Specifies whether to only precheck the request. Default value: false. Valid values: true: prechecks the request without performing the operation. The system checks the required parameters, request syntax, and limits. If the request fails the precheck, an error message is returned. If the request passes the precheck, the `DryRunOperation` error code is returned. false: sends the request. If the request passes the precheck, a 2xx HTTP status code is returned and the operation is performed.	false

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The ID of the request.	64ADAB1E-0B7F-4FD8-A404-3BECC0E9CCFF
AclIds	array	The ID of the ACL.
	string	The ID of the ACL.	nacl-hp34s2h0xx1ht4nwo****
ListenerId	string	The ID of the listener.	lsr-bp1bpn0kn908w4nbw****

Examples

Sample success responses

JSONformat

{
  "RequestId": "64ADAB1E-0B7F-4FD8-A404-3BECC0E9CCFF",
  "AclIds": [
    "nacl-hp34s2h0xx1ht4nwo****"
  ],
  "ListenerId": "lsr-bp1bpn0kn908w4nbw****"
}

Error codes

HTTP status code	Error code	Error message	Description
400	NotExist.Listener	listener %s is not exist	The listener %s does not exist.
400	NotActive.Listener	listener %s is not active	The listener %s is unavailable.
400	NotExist.Accelerator	accelerator %s is not exist	The GA instance %s does not exist.
400	StateError.Accelerator	accelerator state %s is illegal	The GA instance is in an invalid state %s.
400	NotExist.Acl	acl %s is not exist	The ACL %s does not exist.
400	StateError.Acl	acl state %s is illegal	The status of the ACL %s is invalid.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2021-04-27	Add Operation	see changesets