Datadog Duplicate Hosts After AWS Integration

How to fix it

Try these in order — the most common fix is first.

1. 1. Set explicit hostname

   Copy steps
   1. Set hostname in datadog.yaml to match the cloud instance ID or name
   2. Restart the Agent and wait up to two hours
   Did this fix it? Yes No

2. 2. Find duplicates

   Copy steps
   1. Infrastructure > Infrastructure List
   2. Filter by the Agent app field or search the hostname
   Did this fix it? Yes No

3. 3. Align OpenTelemetry hostnames

   1. Use the same host attribute in OTLP exports and the Agent
   Did this fix it? Yes No

Symptoms

Two entries for one host in Infrastructure List, inflated host count and bill.

Why it happens

• Agent and AWS EC2 integration failing to map to the same host
• Hostname differs between OTLP and Agent

This guide also covers

• datadog duplicate hosts
• datadog duplicate host names aws

Other Datadog errors

• How to Cancel Datadog Subscription
• Datadog Agent Not Reporting Metrics or Host Missing
• Datadog Logs Not Showing in Log Explorer
• Datadog APM Traces Not Showing Up
• Datadog Agent High CPU or Memory Usage
• Datadog Monitor No Data Alerts Not Working
• Why Is My Datadog Bill So High: Custom Metrics
• Datadog Agent 403 API Key Invalid in Kubernetes