Cloud Cost Management is not supported for this site.
Overview
To use AWS Cloud Cost Management, you must have an AWS account with access to Cost and Usage Reports (CURs), and have the AWS integration installed in Datadog. To set up Cloud Cost Management in Datadog, you need to generate a Cost and Usage report.
Setup
Prerequisite: generate a Cost and Usage Report
Follow AWS instructions for Creating Cost and Usage Reports, and select the following content options for use with Datadog Cloud Cost Management:
Include resource IDs
Split cost allocation data (Enables ECS Cost Allocation. You must also opt in to AWS Split Cost Allocation in Cost Explorer preferences).
“Refresh automatically”
Select the following Delivery options:
Time granularity: Hourly
Report versioning: Create new report version
Compression type: GZIP or Parquet
Format: text/csv or Parquet
Configure the AWS integration
Navigate to Setup & Configuration and select an AWS account from the dropdown menu to pull costs from.
Note: Datadog recommends sending a Cost and Usage Report from an AWS management account for cost visibility into related member accounts. If you send a Cost and Usage report from an AWS member account, ensure that you have selected the following options in your management account’spreferences:
Linked Account Access
Linked Account Refunds and Credits
Linked Account Discounts
This ensures complete cost accuracy by allowing periodic cost calculations against the AWS Cost Explorer.
Locate the Cost and Usage Report
If you have navigated away from the report that you created in the setup prerequisites section, follow AWS documentation to find and view your Cost and Usage Reports details.
To enable Datadog to locate the Cost and Usage Report, complete the fields with their corresponding details:
Region: This is the region your bucket is located. For example, us-east-1.
Bucket Name: This is the name of the s3 bucket that the CUR is saved to.
Report Path Prefix: This is the folder name. If viewing Report path prefix from the AWS details page, this is the first section of the path. For example, if Report path prefix is displayed as cur-report-dir/cost-report, you would enter cur-report-dir.
Report Name: This is the name you entered when you generated the report in the prerequisite section. If viewing the Report path prefix from the AWS details page, this is the second half of the path. For example, if Report path prefix is displayed as cur-report-dir/cost-report, you would enter cost-report.
Note: Datadog only supports CURs generated by AWS. Do not modify or move the files generated by AWS, or attempt to provide access to files generated by a 3rd party.
Configure access to the Cost and Usage Report
Configure AWS to ensure Datadog has permissions to access the CUR and the s3 bucket it is stored in by creating a policy using the following JSON:
Tip: Make note of the name you created for this policy for next steps.
Attach the policy to the Datadog integration role
Attach the new S3 policy to the Datadog integration role.
Navigate to Roles in the AWS IAM console.
Locate the role used by the Datadog integration. By default it is named DatadogIntegrationRole, but the name may vary if your organization has renamed it. Click the role name to open the role summary page.
Click Attach policies.
Enter the name of the S3 bucket policy created above.
Click Attach policy.
Note: Data can take up to 48 to 72 hours after setup to stabilize in Datadog.
Cost types
You can visualize your ingested data using the following cost types:
Cost Type
Description
aws.cost.amortized
Cost based on applied discount rates plus the distribution of pre-payments across usage for the discount term (accrual basis).
aws.cost.unblended
Cost shown as the amount charged at the time of usage (cash basis).
aws.cost.blended
Cost based on the average rate paid for a usage type across an organization’s member accounts.
aws.cost.ondemand
Cost based on the list rate provided by AWS.
Tag enrichment
Datadog adds out-of-the-box tags to the ingested cost data to help you further break down and allocate your costs. These tags are derived from your Cost and Usage Report (CUR).
The following out-of-the-box tags are available for filtering and grouping data:
Tag
Description
aws_product
The AWS service being billed.
aws_product_family
The category for the AWS service being billed (for example, Compute or Storage).
aws_management_account_name
The AWS management account name associated with the item.
aws_management_account_id
The AWS management account ID associated with the item.
aws_member_account_name
The AWS member account name associated with the item.
aws_member_account_id
The AWS member account ID associated with the item.
aws_cost_type
The type of charge covered by this item (for example, Usage, or Tax).
aws_pricing_term
Whether the usage is Reserved, Spot, or On-Demand.
aws_reservation_arn
The ARN of the Reserved Instance that the item benefited from.
aws_savings_plan_arn
The ARN of the Savings Plan the item benefited from.
aws_usage_type
The usage details of the item (for example, BoxUsage:i3.8xlarge).
aws_operation
The operation associated with the item (for example, RunInstances).
aws_region
The region associated with the item.
aws_availability_zone
The availability zone associated with the item.
aws_resource_id
The resource ID associated with the item.
aws_instance_type
The instance types associated with your items.
aws_instance_family
The instance family associated with your item (for example, Storage optimized).
is_aws_ec2_compute
Whether the usage is related to EC2 compute.
is_aws_ec2_compute_on_demand
Whether the usage is on-demand.
is_aws_ec2_compute_reservation
Whether the usage is associated with a Reserved Instance.
is_aws_ec2_capacity_reservation
Whether the usage is associated with a Capacity Reservation.
is_aws_ec2_spot_instance
Whether the usage is associated with a Spot Instance.
is_aws_ec2_savings_plan
Whether the usage is associated with a Savings Plan.
Cost and observability correlation
Viewing costs in context of observability data is important to understand how infrastructure changes impact costs, identify why costs change, and optimize infrastructure for both costs and performance. Datadog updates resource identifying tags on cost data for top AWS products to simplify correlating observability and cost metrics.
For example, to view cost and utilization for each RDS database, you can make a table with aws.cost.amortized, aws.rds.cpuutilization, and aws.rds.freeable_memory (or any other RDS metric) and group by dbinstanceidentifier. Or, to see Lambda usage and costs side by side, you can graph aws.lambda.concurrent_executions and aws.cost.amortized grouped by functionname.
Billing conductor enables you to simplify your bill by customizing the billing rates, distributing credits and fees, and sharing overhead costs at your discretion. You can also select which accounts to include in the CUR.
To create a billing conductor CUR, follow the AWS Cost and Usage Reports user guide. Ensure the CUR meets Datadog’s requirements.
After the billing conductor CUR is created, follow the Cloud Cost Management instructions above to set it up in Datadog.
Further reading
Additional helpful documentation, links, and articles: