This topic explains how to stream AWS CloudWatch metrics from your AWS account to LaunchDarkly’s observability features. This integration allows you to monitor your AWS infrastructure alongside your feature flag data for unified observability.
The integration uses AWS CloudWatch Metric Streams to send metrics in real-time using the OpenTelemetry format. Data is delivered using Amazon Kinesis Data Firehose to LaunchDarkly’s OpenTelemetry Protocol (OTLP) endpoint.
To use the AWS CloudWatch Metrics integration, you require:
To find and copy your LaunchDarkly client-side ID, follow the instructions under View or copy SDK credentials.
You can deploy the AWS CloudWatch Metrics integration using the AWS CloudFormation console or the AWS CLI.
To deploy using the AWS Console:
metric-stream.yaml.metric-stream.yaml file you saved.launchdarkly-metrics-stream.The stack takes 3-5 minutes to create. After creation completes, metrics begin flowing to LaunchDarkly.
To deploy using the AWS CLI:
Replace YOUR_CLIENT_SIDE_ID with your LaunchDarkly environment’s client-side ID.
The CloudFormation template creates the following AWS resources:
All metrics from all AWS namespaces such as EC2, Lambda, RDS, DynamoDB, and ECS are streamed automatically, providing comprehensive visibility into your AWS infrastructure.
After deployment, metrics appear in the LaunchDarkly observability dashboard within 1-2 minutes.
To view your metrics:
Metrics are tagged with their AWS namespace, region, and resource identifiers for easy filtering.
By default, the integration sends all AWS CloudWatch metrics from all services, providing complete observability coverage. If you need to reduce cost and data volume for specific use cases, you can optionally filter to specific AWS service namespaces.
To filter metrics to specific namespaces:
MetricStream resource.IncludeFilters section, similar to:For a complete list of AWS service namespaces, read AWS services that publish CloudWatch metrics in the AWS documentation.