---
name: cloud-logs-instance-provision
title: Provisioning an instance
description: You can provision an instance of the IBM Cloud Logs service through the IBM Cloud catalog, and programmatically by using a terraform script or the Resource Controller API.
last-updated: 2026-03-25
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-logs?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Provisioning an instance
{: #instance-provision}

You can provision an instance of the IBM Cloud Logs service through the IBM Cloud catalog, and programmatically by using a terraform script or the Resource Controller API.
{: shortdesc}

IBM Cloud Logs integrates with IBM Cloud Object Storage for long term storage of the data and for collection of metrics, and with IBM Cloud Event Notifications for triggering of alerts. Authorization between services is done by configuring IAM service to service authorizations in the account.

You can run Cloud Logs without a data bucket or a metrics bucket. However, features like TCO Optimizer to manage data thorugh different data pipelines at different costs, long term data querying or metrics related features would not be available.

There are limits for each provisioned instance. For more information, see [Limits per instance](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-limits&interface=ui&format=markdown#limits-per-instance).
{: note}


## Naming requirements when provisioning an IBM Cloud Logs instance
{: #limits-instance-name}

When provisioning an IBM Cloud Logs instance, the service instance name is limited to 1-256 characters in length and can only include the following characters:

* Letters (`A`-`Z`, `a`-`z`)
* Numbers (`0`-`9`)
* Period (`.`)
* Underscore (`_`)
* Hypen (`-`)
* Colon (`:`)
* Space (` `)


## Provisioning an instance through the Observability dashboard
{: #instance-provision-ui}
{: ui}

To provision an instance from the Observability dashboard in the IBM Cloud, complete the following steps:

1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login){: external}.

	After you log in, the IBM Cloud UI opens.

2. Click the **Menu** icon ![Navigation Menu icon](/icons/icon_hamburger.svg "Menu") > **Observability** to access the *Observability* dashboard.

3. Click **Logging** > **Instances**. You might need to click the **Cloud Logs** tab to see your IBM Cloud Logs instances.

4. Click **Create**.

5. Select the required service for your instance.

6. Select the [location](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-regions&interface=ui&format=markdown) where you plan to provision the instance.

7. Enter a name for the service instance.

8. Select a resource group.

    By default, the **default** resource group is set.

    **Note:** If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.

9. Select the `Standard` service plan.

    By default, the Standard plan is set.

   For more information about service plans, see [Service plans and pricing](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-service_plans&format=markdown).

10. Choose a retention plan. Valid values are `7 days`, `14 days`, `30 days`, `60 days` or `90 days`.

11. Click **Create**.

After you provision an instance, the UI opens.



## Provisioning an instance through the catalog
{: #instance-provision-catalog}
{: ui}

To provision an instance of IBM Cloud Logs through the IBM Cloud catalog, complete the following steps:

1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login){: external}.

	After you log in, the IBM Cloud UI opens.

2. Click **Catalog**. The list of the services that are available in IBM Cloud opens.

3. To filter the list of services that is displayed, select the **Logging and Monitoring** category.

4. Click the **IBM Cloud Logs** tile.

5. Select the [location](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-regions&format=markdown) where you plan to provision the instance.

6. Enter a name for the service instance.

7. Select a resource group.

    By default, the **Default** resource group is set.

    **Note:** If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.

8. Select the `Standard` service plan.

    By default, the standard plan is set. For more information about service plans, see [Service plans and pricing](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-service_plans&format=markdown).

9. Choose a retention plan. Valid values are `7 days`, `14 days`, `30 days`, `60 days` or `90 days`.

10. Click **Create**.

After you provision an instance, the UI opens.




## Provisioning an instance through the CLI
{: #instance-provision-cli}
{: cli}

To provision an instance of IBM Cloud Logs through the command line, complete the following steps:

1. [Pre-requisite] Installation of the IBM Cloud CLI.

   For more information, see [Installing the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli&format=markdown).

   If the CLI is installed, continue with the next step.

2. Log in to the region in the IBM Cloud where you want to provision the instance. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cli&format=markdown#ibmcloud_login)

3. Set the resource group where you want to provision the instance. Run the following command: [ibmcloud target](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cli&format=markdown#ibmcloud_target)

    By default, the `default` resource group is set.

4. Create the instance. Run the [ibmcloud resource service-instance-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resource&format=markdown#ibmcloud_resource_service_instance_create) command:

    ```text
    ibmcloud resource service-instance-create NAME logs SERVICE_PLAN_NAME LOCATION -p '{"private_endpoints_only": PRIVATE_ENDPOINT}'
    ```
    {: codeblock}

    Where

    `NAME` is the name of the instance

    `SERVICE_PLAN_NAME` is the type of plan. Valid value is *standard*.

    `LOCATION` is the region where the logging instance is created. To get the latest list of locations that are available for the IBM Cloud Logs service, see [Locations](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-regions&format=markdown).

    * `PRIVATE_ENDPOINT` is either `true` or `false`.  If `true` only [private endpoints](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-endpoints_api&format=markdown) can be used to access the instance.

       Unless otherwise specified when provisioning an instance, the default is for the instance to be accessible by both public and private endpoints.
       {: note}

    For example, to provision an instance with the standard plan that can be accessed only by private endpoints, run the following command:

    ```text
    ibmcloud resource service-instance-create my-instance logs standard us-south -p '{"private_endpoints_only": true}'
    ```
    {: codeblock}



## Next steps
{: #instance-provision-next}

IBM Cloud Logs integrates withIBM Cloud Object Storage for long term storage of the data and for collection of metrics, and with IBM Cloud Event Notifications for triggering of alerts. Authorization between services is done by configuring IAM service to service (S2S) authorizations in the account.

After you provision the instance, complete the following steps:

1. Attach a data bucket and a metrics bucket to store data for long term storage and for search. For more information, see [Configuring buckets](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-about-bucket&format=markdown).

2. Configure an outbound integration to an IBM Cloud Event Notifications instance to send notifications to destinations of your choice such as email, or slack. For more information, see [Configuring an outbound integration to connect IBM Cloud Logs with IBM Cloud Event Notifications](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-event-notifications-configure&format=markdown) and [Working with notification channels](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-destinations&format=markdown).

3. Configure one or more log sources. Choose any of the following options:

    - Configure the logging agent. This agent is responsible for collecting and forwarding logs to your instance. For more information, see [The logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-agent-about&format=markdown).

    - Configure IBM Cloud Activity Tracker Event Routing to route auditing events, both [global](https://cloud.ibm.com/docs/atracker?topic=atracker-event_types&format=markdown#event_types_global) and [location-based](https://cloud.ibm.com/docs/atracker?topic=atracker-event_types&format=markdown#event_types_location) event data, in your IBM Cloud to the IBM Cloud Logs instance. For more information, see [Getting started with IBM Cloud Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started&format=markdown).

    - Configure IBM® Cloud Logs Routing to route platform logs from your IBM Cloud account to the IBM Cloud Logs instance. For more information, see [Getting started with IBM® Cloud Logs Routing](https://cloud.ibm.com/docs/logs-router?topic=logs-router-getting-started&format=markdown).