> ## Documentation Index > Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # LaunchDarkly in the European Union (EU) This topic explains how the version of LaunchDarkly that is available on domains residing in the European Union (EU) is different from the version of LaunchDarkly available in the United States. The LaunchDarkly EU instance complies with EU data residency principles, including the protection and confidentiality of EU customer information. To comply with these data principles, the LaunchDarkly EU instance includes additional controls on its infrastructure and security configurations. These controls allow management of customer data flows that are not available in the US instance of LaunchDarkly. The EU instance resides in the AWS Frankfurt (`eu-central-1`) region and operates nearly the same as the US instance of LaunchDarkly. Operational monitoring with Datadog and edge delivery/CDN (Fastly) still operate from regions within the United States. The EU instance only supports net new Enterprise plan accounts and LaunchDarkly trials. ## The EU version of this docs site You can view an EU instance-specific version of this documentation site. The EU version of the docs site is different from the standard version in the following ways: * EU instance URLs display with `.eu` URLs, including within code samples. To learn more, read [EU instance URLs](#eu-instance-urls). * Features and integrations that the EU instance does not support are marked with a warning message. To learn more, read [Supported features](#supported-features). To view the EU instance-specific version of this documentation site, change the site version menu to "EU docs". ## Supported features The EU instance supports the following features: * [AgentControl](/docs/home/agentcontrol) * [The Billing page](/docs/home/account/billing-page) * Core flagging features through the LaunchDarkly application and [API](/docs/api) * [Code references](/docs/home/flags/code-references) * [Experimentation](/docs/home/experimentation), including [Snowflake native Experimentation](/docs/home/warehouse-native/snowflake) * Some [flag imports](/docs/home/flags/import) * [Guarded rollouts](/docs/home/releases/guarded-rollouts) * The [LaunchDarkly Relay Proxy](/docs/sdk/relay-proxy) * [Live events](/docs/home/releases/live-events) * [The local MCP server](/docs/home/getting-started/mcp-local) * [Metrics](/docs/home/metrics) * [Observability](/docs/home/observability) data ingestion, using the OpenTelemetry endpoints and the [observability SDKs](/docs/sdk/observability) * Most [SDKs](/docs/sdk), except for edge SDKs and the Roku SDK * [Single sign-on (SSO)](/docs/home/account/sso), including [SCIM-based user provisioning for Okta SSO](/docs/home/account/okta) * [Streaming data export](/docs/integrations/data-export/streaming) The EU instance does not currently support the following features: * Adaptive triggers for [flags](/docs/home/flags/triggers) or [configs](/docs/home/agentcontrol/triggers) * [Applications and app versions](/docs/home/releases/apps-and-app-versions) * [Debugging guarded rollout errors](/docs/home/releases/errors) * [Edge SDKs](/docs/sdk/edge) * [Inbox notifications for approval requests](/docs/home/releases/approval-reviews#view-approval-requests-from-your-in-app-inbox) * [Launch Insights](/docs/home/getting-started/launch-insights) * [The hosted MCP server](/docs/home/getting-started/mcp-hosted) * [Migration flags](/docs/home/flags/migration) * [The Roku SDK](/docs/sdk/client-side/roku) * [Session replay](/docs/home/observability/session-replay) * The [support chatbot](/docs/home/getting-started/feature-management#additional-resources) * [Vega](/docs/home/getting-started/vega) ### Integrations available in the EU instance Integrations connect LaunchDarkly to other systems and move data between them. Only the following connected systems are currently enabled. The EU instance initially will only support customer requested integrations. Requested integrations are provisioned shortly after each request. The following integrations are enabled: * [AppDynamics](/docs/integrations/appdynamics) * [Chronosphere events](/docs/integrations/chronosphere) * [Crossplane](/docs/integrations/crossplane) * [Custom approvals](/docs/integrations/custom-approvals) * [Datadog flag triggers](/docs/integrations/datadog/triggers) * [Datadog events](/docs/integrations/datadog/events) * [DynamoDB segments integration](/docs/integrations/dynamodb) * [Dynatrace flag triggers](/docs/integrations/dynatrace/triggers) * [Dynatrace events](/docs/integrations/dynatrace/events) * [Elastic (ELK) Stack](/docs/integrations/elastic-stack) * [Github Actions](/docs/integrations/github-actions) * [Honeycomb flag triggers](/docs/integrations/honeycomb/triggers) * [Honeycomb events](/docs/integrations/honeycomb/events) * [IntelliJ IDEA plugin](/docs/home/getting-started/intellij) * [Jira](/docs/integrations/jira) * [Last9](/docs/integrations/last9) * [New Relic](/docs/integrations/new-relic) * [MS Teams incoming webhooks](/docs/integrations/microsoft-teams/webhooks) * [PagerDuty](/docs/integrations/pagerduty-guardian-edition) * [Redis segments integration](/docs/integrations/dynamodb) * [ServiceNow approvals](/docs/integrations/servicenow) * [Slack incoming webhooks](/docs/integrations/slack/webhooks) * [Snowflake Data Export](/docs/integrations/data-export/snowflake) * [Splunk Observability Cloud](/docs/integrations/splunk-observability) * [Splunk](/docs/integrations/splunk) * [Twilio Segment](/docs/integrations/metric-segment) ## EU instance URLs The EU instance, including the LaunchDarkly application, the instance API, and SDK use the base domain `eu.launchdarkly.com` in the URL path. If your network uses application or network layer firewalls, you must update them to allow these URLs. If you do not do this, LaunchDarkly will not function properly. These URLs are: * `https://app.eu.launchdarkly.com` * `https://clientsdk.eu.launchdarkly.com` * `https://clientstream.eu.launchdarkly.com` * `https://events.eu.launchdarkly.com` * `https://sdk.eu.launchdarkly.com` * `https://stream.eu.launchdarkly.com` To learn how to configure your SDK correctly using these endpoints, read [Service endpoint configuration](/docs/sdk/features/service-endpoint-configuration). ### Observability ingestion URLs Observability data ingestion uses the base domain `observability.app.eu.launchdarkly.com`. The observability SDKs and several of the third-party integrations send data using the OpenTelemetry Protocol (OTLP). If you send observability data to the EU instance, either from an observability SDK or from a third-party application, you must also allow the following hosts and ports:
Host:Port Used by
`otel.observability.app.eu.launchdarkly.com:`

`443` and `4318` (OTLP over HTTP)
`4317` (OTLP over gRPC)
`24224` (Fluent Forward protocol)		 [Observability SDKs](/docs/sdk/observability)
[OpenTelemetry Collector](/docs/sdk/features/observability-otel-collector)
[Azure Monitor](/docs/home/observability/azure-monitor)
[Fluent Bit](/docs/home/observability/fluentbit)
[AWS FireLens](/docs/home/observability/firelens)
`pub.observability.app.eu.launchdarkly.com:443` [Observability SDKs](/docs/sdk/observability)
[AWS FireLens](/docs/home/observability/firelens)
[Vercel](/docs/home/observability/vercel) log drain
`otlpv1.firehose.observability.app.eu.launchdarkly.com:443` [AWS CloudWatch Metrics](/docs/home/observability/aws-cloudwatch-metrics)
`datadog.observability.app.eu.launchdarkly.com:8126` [Datadog Agent ingestion](/docs/home/observability/datadog-agent)
`syslog.observability.app.eu.launchdarkly.com:34302` [Syslog log drain](/docs/home/observability/syslog)
To learn more about the applications you can configure to send observability data to LaunchDarkly, read [Observability integrations](/docs/home/observability/integrations). ## Initialize an SDK for the EU instance You can initialize an SDK for the EU instance using the initialization options for the SDK. Depending on the SDK, you may need to configure multiple service endpoints in the initialization options. These could include the base and polling endpoint, streaming endpoint, and events endpoint. Server-side SDKs normally require streaming and events settings, not polling. For a list of available service endpoints, read [EU instance URLs](#eu-instance-urls). The details of how to set these options differ between SDKs, as LaunchDarkly respects each language's URI and URL naming conventions and supported services. For this reason, it is critical to reference the documentation for each individual SDK. Configure your SDK: [Service endpoint configuration](/docs/sdk/features/service-endpoint-configuration)