All Products
Search

This Product

    Simple Log Service:CreateLogStore

    Document Center

    Simple Log Service:CreateLogStore

    Last Updated:Jan 15, 2026

    Creates a Logstore.

    Operation description

    Usage notes

    • The Host in the request syntax consists of the project name and the Simple Log Service endpoint. Specify the project in the Host.

    • Create an AccessKey pair. For more information, see AccessKey pair.

    An AccessKey pair for an Alibaba Cloud account has full access to all API operations, which poses a high security risk. We recommend that you create and use a Resource Access Management (RAM) user to call API operations or perform routine O&M. The RAM user must have the permissions to manage Simple Log Service resources. For more information, see Create and authorize a RAM user.

    • Obtain the project name and the region where the project is located. For more information, see Manage projects.

    • Each project can contain a maximum of 200 Logstores.

    • Logs are deleted after the specified data retention period expires.

    Authorization

    The following table describes the permissions required for this operation. To grant a RAM user or RAM role the permissions to call this operation, add this information to the Action element of a RAM policy.

    ActionResource description in an authorization policy
    log:CreateLogStoreacs:log:{#regionId}:{#accountId}:project/{#ProjectName}/logstore/{#LogstoreName}

    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

    log:CreateLogStore

    create

    *LogStore

    acs:log:{#regionId}:{#accountId}:project/{#project}/logstore/{#logstoreName}
    • log:TLSVersion
    • log:Encrypted
    		 None

    Request syntax

    POST /logstores HTTP/1.1

    Request parameters

    Parameter

    Type

    Required

    Description

    Example
    project

    string

    Yes

    The name of the project.

    ali-test-project
    body

    object

    Yes

    The request parameters.

    logstoreName

    string

    Yes

    The name of the Logstore. The name must meet the following requirements:

    • The name must be unique within a project.

    • It can contain only lowercase letters, digits, hyphens (-), and underscores (_).

    • It must start and end with a lowercase letter or a digit.

    • It must be 2 to 63 characters in length.

    my-logstore
    shardCount

    integer

    Yes

    The number of shards.

    Note

    You cannot change the number of shards with this operation. To change the number of shards, call the `SplitShard` or `MergeShards` operation.

    2
    ttl

    integer

    Yes

    The data retention period, in days. Valid values: 1 to 3650. If you set the value to 3650, data is stored permanently.

    1
    encrypt_conf EncryptConf

    No

    The data structure of the encryption configuration. The parameters include enable, encrypt_type, and user_cmk_info. For more information, see EncryptConf.

    autoSplit

    boolean

    No

    Specifies whether to automatically split shards.

    • true: automatically splits shards.

    • false: does not automatically split shards.

    true
    enable_tracking

    boolean

    No

    Specifies whether to enable web tracking. Default value: false.

    • true: enables web tracking.

    • false: disables web tracking.

    false
    maxSplitShard

    integer

    No

    The maximum number of shards that can be created by an automatic split. The value must be between 1 and 256.

    Note

    This parameter is required if you set the autoSplit parameter to true.

    64
    appendMeta

    boolean

    No

    Specifies whether to record the client's public IP address and the log reception time. The default value is false.

    • true: records the public IP address of the client and the time when logs are received. If this feature is enabled, Simple Log Service automatically adds the public IP address of the log source and the server time of log reception to the tag field of the logs.

    • false: does not record the public IP address of the client or the time when logs are received.

    false
    telemetryType

    string

    No

    The type of observable data. Valid values:

    • None: log data. This is the default value.

    • Metrics: metrics.

    None
    hot_ttl

    integer

    No

    The retention period of data in the hot storage tier of the Logstore, in days. The minimum value is 7. The value cannot be greater than the value of `ttl`. If you set this parameter to -1, data is permanently stored in the hot tier.

    After the hot tier retention period expires, data is moved to the Infrequent Access (IA) storage class. For more information, see Automatic Storage Tiering.

    60
    mode

    string

    No

    The Logstore mode. Simple Log Service provides two modes: Standard and Query.

    • standard: Supports comprehensive data analytics. This mode is suitable for use cases such as real-time monitoring, interactive analysis, and building a complete observability system.

    • query: Supports high-performance queries. The index traffic cost for this mode is about half that of the Standard mode. This mode does not support SQL analysis. It is suitable for use cases that involve large amounts of data, long retention periods, and no log analysis requirements.

    standard
    infrequentAccessTTL

    integer

    No

    The retention period of data in the Infrequent Access (IA) storage class, in days. The value must be 30 or greater.

    30
    processorId

    string

    No

    The ID of the ingest processor.

    processor-nginx-parser-001
    shardingPolicy ShardingPolicy

    No

    The configuration for hash-based writes.

    resourceGroupId

    string

    No

    The ID of the resource group.

    Response elements

    Element

    Type

    Description

    Example

    None defined.

    Examples

    Success response

    JSON format

    {}

    Error codes

    See Error Codes for a complete list.

    Release notes

    See Release Notes for a complete list.