Service endpoint configuration

This topic explains how to configure LaunchDarkly SDKs to connect to alternate service endpoints. Typically this is only required for customers working with the LaunchDarkly federal instance.

Overview

This topic explains how to configure LaunchDarkly SDKs to connect to alternate service endpoints.

Each SDK connects to several LaunchDarkly web services. These include services for getting feature flag data using streaming or polling, and a service for storing analytics events. Optionally, you can configure LaunchDarkly to connect to alternate service endpoints.

Most customers do not need to configure service endpoints. You may need to configure service endpoints in the following situations:

• You are working with the LaunchDarkly federal instance. If you are using the federal instance of LaunchDarkly, you must configure the SDK so that it connects to the federal instance for these services instead.
• You are working with the LaunchDarkly European Union (EU) instance. If you are using the EU instance of LaunchDarkly, you must configure the SDK so that it connects to the federal instance for these services instead. To learn which URLs to use instead, read the EU instance documentation.
• You are using the Relay Proxy in proxy mode. To learn more, read Using proxy mode.
• You are using the LaunchDarkly CLI to run a local dev-server for testing, and you want to access local flag values from there. To learn more, read Using the LaunchDarkly CLI for local testing.

The examples below show how to configure the SDK for each service. In most SDKs, you then need to pass the configuration in as a parameter when you initialize the client. To learn more, read Configuration.

Details about each SDK’s configuration are available in the SDK-specific pages below.

SDK-specific configuration

Use the SDK-specific pages for implementation details and code samples:

• Client-side SDKs
• Server-side SDKs