All Products
Search
Document Center

Global Accelerator:AttachLogStoreToEndpointGroup

Last Updated:Jul 31, 2024

Associates a Log Service Logstore with an endpoint group.

Operation description

  • AttachLogStoreToEndpointGroup is an asynchronous operation. After you send a request, the system returns a request ID, but this operation is still being performed in the system background. You can call the DescribeEndpointGroup operation to query the state of an endpoint group.

    • If the endpoint group is in the updating state, it indicates that a Logstore is being associated with the group. In this case, you can perform only query operations.
    • If the endpoint group is in the active state, it indicates that a Logstore is associated with the group.
  • The AttachLogStoreToEndpointGroup operation cannot be repeatedly called 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.

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.
OperationAccess levelResource typeCondition keyAssociated operation
ga:AttachLogStoreToEndpointGroupupdate
  • EndpointGroup
    acs:ga:{#regionId}:{#accountId}:endpointgroup/{#endPointGroupId}
  • Accelerator
    acs:ga:{#regionId}:{#accountId}:ga/{#acceleratorId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The ID of the region where the GA instance is deployed. Set the value to cn-hangzhou.

cn-hangzhou
SlsProjectNamestringYes

The name of the Log Service project.

pn-01
SlsLogStoreNamestringYes

The name of the Logstore.

lsn-01
AcceleratorIdstringYes

The ID of the GA instance.

ga-bp1odcab8tmno0hdq****
ListenerIdstringYes

The ID of the listener.

lsr-bp1bpn0kn908w4nbw****
SlsRegionIdstringYes

The region ID of the Log Service project.

cn-hangzhou
EndpointGroupIdsarrayYes

The IDs of the endpoint groups.

stringYes

The IDs of the endpoint groups.

['epg-bp1dmlohjjz4kqaun****','epg-bp1v1u72cx35ogofe****', ...]
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request.

You can use the client to generate the value, but you must make sure that it is unique among different requests. ClientToken can contain only ASCII characters.

Note If you do not set this parameter, ClientToken is set to the value of RequestId. The value of RequestId for each API request may be different.
123e4567-e89b-12d3-a456-426655440000

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The ID of the request.

6FEA0CF3-D3B9-43E5-A304-D217037876A8

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status codeError codeError messageDescription
400StateError.AcceleratorThe state of the accelerated instance is invalid.The status of the GA instance is invalid.
400NotExist.AcceleratorThe accelerated instance does not exist.The GA instance does not exist.
400NotSupportAccessLog.AcceleratorCurrently Accelerator does not support access log feature-
400NotExist.EndPointGroupendpoint group %s is not existThe endpoint group %s does not exist.
400StateError.EndPointGroupendpoint group state %s is illegalThe endpoint group is in an invalid state.

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

Change history

Change timeSummary of changesOperation
2021-04-27Add OperationView Change Details