All Products
Search

This Product

    Simple Log Service:Preparations and service authorization

    Document Center

    Simple Log Service:Preparations and service authorization

    Last Updated:Oct 20, 2026

    Before you use SessionStore, you must prepare a Simple Log Service (SLS) project, confirm the data source, and configure operation permissions and service access permissions. This topic describes these prerequisites and how to check the authorization.

    Prepare a project and data

    1. Log on to the Simple Log Service console and confirm the destination region and project.

    2. Determine the data format that is used by your application.

      Data format

      Applicable source

      OpenTelemetry Trace

      Execution chains and GenAI data that are reported in the form of OpenTelemetry traces or spans.

      Trace logs that are ingested by using Cloud Monitor 2.0 or Application Real-Time Monitoring Service (ARMS) agents, or trace logs that are ingested by using the OpenTelemetry SDK.

      OpenTelemetry Log Ebpf

      eBPF agent logs that are collected in the corresponding format.

      Logs that are collected by using the input_agentsight plug-in of LoongCollector in Simple Log Service.

      Collect AI Agent observability logs (AgentSight)

      OpenTelemetry Log AI Gateway

      Alibaba Cloud AI Gateway logs

    3. Prepare the data source based on the ingestion mode.

      Ingestion mode

      What to prepare

      Direct write

      Prepare a collection solution that supports the selected format, and make sure that you have the permissions to write data to the destination project and SessionStore.

      Reference

      Make sure that the source Logstore already contains data or will receive data. The source project and the destination project must belong to the same account and reside in the same region.

    Complete the authorization of the default role

    The current process uses the default role AliyunLogETLRole. During creation, you cannot use a custom role or enter an AccessKey pair.

    1. Go to the destination project and open the SessionStore creation page.

    2. View the check result in the service authorization section.

    3. If the system prompts that the authorization is not complete, click Authorize Now. On the RAM page that appears, check the role and the authorization content. Then, ask a user who has the required permissions to complete the authorization.

    4. Return to the original creation page and click Check Again.

    5. After Authorized is displayed, continue to complete the creation.

    Note: After the authorization is complete, you must manually run the check again. Returning to the page does not automatically submit the creation request.

    Subsequent maintenance

    You can view the current status of the default role on the overview page of the SessionStore. If the role is abnormal, reauthorize the role or run the check again as prompted.

    Modifying resource properties such as the data retention period does not fix the role authorization. Conversely, reauthorization does not modify the name, data format, or ingestion mode of the SessionStore.