- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
With the release of Agent v7.64.0, the Datadog Agent defaults to using IMDSv2 for enhanced security and consistency in retrieving AWS metadata.
If your host has already configured the ec2_prefer_imdsv2
flag to true
, you should not notice any changes as IMDSv2 is already enabled.
If you upgrade to Agent v7.64.0 without any custom configuration changes, you may see a change to how hostnames appear in Datadog. In particular, Datadog ensures that displayed hostnames refer to instance IDs. This change only impacts how hostnames are displayed. Metric tagging continues to use your original hostnames. Monitoring, alerting, and dashboards should not be affected.
The hostname chosen to associate tags with metrics is named the canonical hostname. This hostname is the unique ID used to identify your host. Even if your hostname changes after upgrading to v7.64.0+, the canonical hostname of your host does not change, and you can continue to refer to the previous hostname.
Hosts updated from a version preceding v7.64.0 to a later release may exhibit an average reporting delay of approximately five minutes.
If any issues arise after updating a host, you can revert to the previous behavior by setting ec2_imdsv2_transition_payload_enabled
to false
in your host configuration. You can also contact Support.