Difference between revisions of "Datadog AWS Integration Billing"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
* https://docs.datadoghq.com/account_management/billing/aws/ | * https://docs.datadoghq.com/account_management/billing/aws/ | ||
| − | If your [[EC2 instances]] are configured to require the use of Instance Metadata Service Version 2 ([[IMDSv2]]), then you must set the parameter <code>[[ec2_prefer_imdsv2]]</code> to true in your [[ | + | If your [[EC2 instances]] are configured to require the use of Instance Metadata Service Version 2 ([[IMDSv2]]), then you must set the parameter <code>[[ec2_prefer_imdsv2]]</code> to true in your [[Datadog agent]] configuration to avoid double-billing. |
== Related == | == Related == | ||
Latest revision as of 12:13, 1 October 2022
If your EC2 instances are configured to require the use of Instance Metadata Service Version 2 (IMDSv2), then you must set the parameter ec2_prefer_imdsv2 to true in your Datadog agent configuration to avoid double-billing.
Related[edit]
See also[edit]
- Datadog, Datadog agent, Forwarder, Spans, DBM, standard attribute list, facets, log explorer, Terraform datadog, Airflow,
dog, agent, DogStatsD, Airflow integration, Datadog pipelines,app.datadoghq.eu, Datadog Cloud SIEM, Cloud Security Management, Datadog AWS Integration, Datadog Monitors,dd-trace-go, DataDog Continuous Profiler, CoScreen, Kubernetes APM, flex logs, Datadog notifications
Advertising:
