QcloudCOSAccessForCLSRole
or QcloudCKAFKAAccessForCLSRole
policy permission to the unique service role CLS_QcsRole
of CLS.Permission | Description | Use Case |
CLS preset policy: QcloudCLSFullAccess | The permission for collaborator or sub-account to operate CLS | The collaborator or sub-account must be authorized to operate CLS and configure shipping tasks |
CAM preset policy: QcloudCamSubaccountsAuthorizeRoleFullAccess | The permission for collaborator or sub-account to authorize the service role | When shipping logs to COS or CKafka, the collaborator or sub-account needs to confirm that the role is authorized with the CLS write permission to COS or CKafka, i.e., grant the service role CLS_QcsRole the policy permission QcloudCOSAccessForCLSRole or QcloudCKAFKAAccessForCLSRole |
COS API permission: GetService (or preset policy: QcloudCOSReadOnlyAccess ) | The permission for collaborator or sub-account to obtain the COS bucket lists | To configure a task for shipping to COS in the CLS console, the collaborator or sub-account needs to obtain the COS bucket list, and then selects the destination bucket |
CKafka API permission: ListInstance , ListTopic (or preset policy: QcloudCkafkaReadOnlyAccess ) | The permission for collaborator or sub-account to obtain CKafka resource list | To configure a task for shipping to CKafka in the CLS console, the collaborator or sub-account needs to obtain the CKafka resource list, and then selects the target CKafka instance topic |
QcloudCLSFullAccess
, QcloudCamSubaccountsAuthorizeRoleFullAccess
, QcloudCOSReadOnlyAccess
, or QcloudCkafkaReadOnlyAccess
, for the collaborator or sub-account.
Was this page helpful?