Connect Splunk Observability Cloud with AWS-managed Metric Streams

Connect to AWS from the AWS console using Metric Streams.

Amazon CloudWatch supports a quick setup experience for AWS Partner destinations in the CloudWatch Metric Streams console. With this simplified getting-started experience, you can create a Metric Stream to Splunk Observability Cloud in a single step.

Before you start

Before you proceed, check AWS authentication, permissions, and supported regions and Connect AWS to Splunk Observability Cloud for information on data collection intervals and costs. When setting up your configuration in the AWS console, keep in mind that Splunk Observability Cloud supports only OpenTelemetry 0.7 and 1.0.

For alternative connection methods, see the following topics:

Note: You can only have 1 integration using Metric Streams externally managed from AWS at a time for each AWS account. All Metric Streams you created in different AWS regions are sent to this integration. Editing included regions affects metadata and might impact how corresponding metric streams are located and displayed in Splunk Observability Cloud features such as dashboards.

Start the connection to AWS in the Splunk console guided setup

To access the guided setup for the AWS integration, perform the following steps:

  1. Log in to Splunk Observability Cloud.

  2. Open the Amazon Web Services guided setup. Optionally, you can navigate to the guided setup on your own:

    • On the navigation menu, select Data Management.

    • Select the tile for Amazon Web Services in the Available integrations tab.

    • You can also go to the Deployed integrations tab and select Add Integration.

Next, follow the steps provided in the guided setup:

Define your AWS connection

In this step, choose the following connection options:

In the CloudWatch Metrics option, select Streaming (AWS-managed) as the ingestion method, and proceed to the AWS console to complete the connection.

Note: To collect logs, see Send AWS logs to Splunk Platform.

Prepare your AWS account

On this screen, Splunk Observability Cloud gives you the following information:

To complete this step, switch to your AWS Console to prepare for authentication and create the Metric Stream to send your data to Splunk Observability Cloud. See Connect to Splunk Observability Cloud from the AWS console.

Establish the connection

Finally, proceed with the last steps:

  1. Complete your authentication configuration as prompted.

  2. Select your data sources:

    • AWS Regions.

    • Built-in and custom services.

Note: Select All built-in services to import all data from built-in CloudWatch namespaces and ensure that built-in dashboards display automatically.

Connect to Splunk Observability Cloud from the AWS console

Before you proceed to create your Metric Streams connection between your AWS and your Splunk Observability Cloud accounts in the AWS console, follow the steps in Start the connection to AWS in the Splunk console guided setup to ensure you have an active AWS integration in your associated Splunk Observability Cloud account.

Note: Make sure you selected Streaming (AWS-managed) as the ingestion method in the integration.
To connect Splunk Observability Cloud from the AWS console, follow these steps:

  1. In the AWS console, go to CloudWatch > Metrics > Streams and select Create metric stream.

  2. Next, select Quick AWS Partner setup as the destination.

  3. In the drop-down menu, select Splunk Observability Cloud. The following form appears:

    Quick Partner Setup for Splunk Observability Cloud in CloudWatch metric stream console
  4. In the Configure the AWS Partner destination menu, enter the Splunk Observability Cloud Ingest endpoint. To find your endpoint, select Profile > Organizations > Real-time Data Ingest Endpointin the Splunk Observability Cloud console. To complete your path, add /v1/cloudwatch_metric_stream to the end of your ingest endpoint URL. For example, https://ingest.us0.observability.splunkcloud.com/v1/cloudwatch_metric_stream.
    Note: You can use the legacy or new API and service endpoint URLs as of March 24, 2026. The legacy endpoints have the domain signalfx, and the new endpoints have the domain observability.splunkcloud. Thus, you can use the legacy ingest endpoint ingest.realm.signalfx.com or the new ingest endpoint ingest.realm.observability.splunkcloud.com. See Splunk Observability Cloud domain change for more information.

  5. Fill in the access token by copying one of the access tokens with INGEST authorization scope from Settings > Access Tokens in the Splunk Observability Cloud console.

  6. You can leave the rest of the form as default, or customize the configuration, such as filtering based on namespaces.

Integrate from the AWS console using the Splunk API

If you want to integrate from the AWS console using the Splunk Observability Cloud API, see Configure Metric Streams from the AWS console.

See also the Integrations API reference on the Splunk Developer Portal.

Next steps

After you connect Splunk Observability Cloud with AWS, you can use Splunk Observability Cloud to track a series of metrics and analyze your AWS data in real time.