---
title: Quickstart on Elastic Cloud Serverless
description: Quickstart guide for setting up EDOT on Elastic Cloud Serverless.
url: https://www.elastic.co/elastic/docs-builder/docs/3028/solutions/observability/get-started/opentelemetry/quickstart/serverless
products:
  - Elastic Cloud Serverless
  - Elastic Distribution of OpenTelemetry Collector
  - Elastic Observability
applies_to:
  - Serverless Observability projects: Generally available
  - Elastic Stack: Generally available
  - Elastic Distribution of OpenTelemetry Collector: Generally available
---

# Quickstart on Elastic Cloud Serverless
The [Elastic Cloud Managed OTLP Endpoint](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3028/reference/opentelemetry/motlp) simplifies OpenTelemetry data ingestion. It provides an endpoint for OpenTelemetry SDKs and Collectors to send telemetry data, with Elastic handling scaling, data processing, and storage. The endpoint is exclusively for Elastic Cloud users, initially available in Elastic Cloud Serverless only.
The Elastic Cloud Managed OTLP Endpoint is designed for the following use cases:
- Logs and Infrastructure Monitoring: Logs forwarded in OTLP format and host and Kubernetes metrics in OTLP format.
- APM: Application telemetry in OTLP format.


## Prerequisites

- An Elastic Observability Serverless project.
- An Elastic Distribution of OpenTelemetry or any system that can forward logs, metrics, or traces in OTLP format.

You also need to retrieve your OTLP endpoint address and an API key.
Follow these steps to retrieve the managed OTLP endpoint URL for your Serverless project:
1. In Elastic Cloud Serverless, open your Observability project.
2. Go to **Add data** → **Application** → **OpenTelemetry**.
3. Select **Managed OTLP Endpoint** in the second step.
4. Copy the OTLP endpoint configuration value.
5. Select **Create API Key** to generate an API key.


## Quickstart guides

Select the quickstart guide for your environment from the following list:
- [Kubernetes on serverless](https://www.elastic.co/elastic/docs-builder/docs/3028/solutions/observability/get-started/opentelemetry/quickstart/serverless/k8s)
- [Docker on serverless](https://www.elastic.co/elastic/docs-builder/docs/3028/solutions/observability/get-started/opentelemetry/quickstart/serverless/docker)
- [Hosts or VMs on serverless](https://www.elastic.co/elastic/docs-builder/docs/3028/solutions/observability/get-started/opentelemetry/quickstart/serverless/hosts_vms)


## Differences with Elastic APM Endpoint

The Elastic Cloud Managed OTLP Endpoint ensures that OpenTelemetry data is stored without any schema translation, preserving both OpenTelemetry semantic conventions and resource attributes. It supports ingesting OTLP logs, metrics, and traces in a unified manner, ensuring consistent treatment across all telemetry data.

## Provide feedback

Help improve the Elastic Cloud Managed OTLP Endpoint by sending us feedback in our [discussion forum](https://discuss.elastic.co/c/apm) or [community Slack](https://elasticstack.slack.com/signup).
For EDOT Collector feedback, open an issue in the [elastic-agent repository](https://github.com/elastic/elastic-agent/issues).