LaunchDarkly in the European Union (EU)

Overview

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 and Guardian 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.
• Features and integrations that the EU instance does not support are marked with a warning message. To learn more, read 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:

• Core flagging features through the LaunchDarkly application and API
• Code references
• Guarded rollouts
• The LaunchDarkly Relay Proxy
• Live events
• Metrics
• Most SDKs
• Single sign-on (SSO)

The EU instance does not currently support the following features:

• Experimentation
• Data Export to Amazon Kinesis
• All Edge SDKs
• The Roku SDK
• LaunchDarkly inbox notifications for approval requests
• The Billing tab
• Certain areas of the Usage tab which rely on other features that are unavailable in the EU instance. For example, Data Export tables and charts do not appear in the Usage tab.
• The search dialog
• The support chatbot

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:

• Slack
• Datadog events
• Honeycomb events
• ServiceNow approvals
• Dynatrace flag triggers
• Datadog flag triggers
• 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.

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.

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.