Use AttachLogStoreToEndpointGroup to associate a Logstore with an endpoint group - Global Accelerator - Alibaba Cloud - Global Accelerator

Associates a Simple Log Service (SLS) Logstore with an endpoint group.

Operation description

AttachLogStoreToEndpointGroup is an asynchronous operation. After you send a request, the system returns a request ID, but the association between the SLS Logstore and the endpoint group is not yet complete. The association node continues to run in the background. You can invoke DescribeEndpointGroup to query the status of the endpoint group:
- If the endpoint group is in the updating state, the SLS Logstore is being associated with the endpoint group. In this state, you can only execute query operations.
- If the endpoint group is in the active state, the SLS Logstore is associated with the endpoint group.
AttachLogStoreToEndpointGroup does not support concurrent association of SLS Logstores with endpoint groups within the same Alibaba Cloud Global Accelerator (GA) instance.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

ga:AttachLogStoreToEndpointGroup

update

*EndpointGroup

acs:ga:{#regionId}:{#accountId}:endpointgroup/{#endPointGroupId}

*Accelerator

acs:ga:{#regionId}:{#accountId}:ga/{#acceleratorId}

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region ID of the Alibaba Cloud Global Accelerator (GA) instance. Set the value to cn-hangzhou.	cn-hangzhou
SlsProjectName	string	Yes	The name of the SLS project.	pn-01
SlsLogStoreName	string	Yes	The name of the SLS Logstore.	lsn-01
AcceleratorId	string	Yes	The instance ID of the Alibaba Cloud Global Accelerator (GA) instance.	ga-bp1odcab8tmno0hdq****
ListenerId	string	Yes	The instance ID of the listener.	lsr-bp1bpn0kn908w4nbw****
SlsRegionId	string	Yes	The region ID of the SLS service.	cn-hangzhou
EndpointGroupIds	array	Yes	The list of endpoint group IDs.
	string	Yes	The list of endpoint group IDs.	['epg-bp1dmlohjjz4kqaun**','epg-bp1v1u72cx35ogofe**', ...]
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 client token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the RequestId of the API request as the ClientToken. The RequestId may be different for each API request.	123e4567-e89b-12d3-a456-426655440000
AccessLogRecordCustomizedHeaderList	array	No
	string	No
AccessLogRecordCustomizedHeadersEnabled	boolean	No

Response elements

Element	Type	Description	Example
	object	The response parameters.
RequestId	string	The request ID.	6FEA0CF3-D3B9-43E5-A304-D217037876A8

Examples

Success response

JSON format

{
  "RequestId": "6FEA0CF3-D3B9-43E5-A304-D217037876A8"
}

Error codes

HTTP status code	Error code	Error message	Description
400	StateError.Accelerator	The state of the accelerated instance is invalid.	The status of the GA instance is invalid.
400	NotExist.Accelerator	The accelerated instance does not exist.	The GA instance does not exist.
400	NotSupportAccessLog.Accelerator	Currently Accelerator does not support access log feature
400	NotExist.EndPointGroup	endpoint group %s is not exist	The endpoint group %s does not exist.
400	StateError.EndPointGroup	endpoint group state %s is illegal	The endpoint group is in an invalid state.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.