Cloud Cost Management
Cloud Cost Management provides insights for engineering and finance teams to see how changes to infrastructure can affect costs. It enables you to understand trends, allocate spend across your organization, and identify inefficiencies.
Datadog ingests your cloud cost data and transforms it into queryable metrics. If costs rise, you can correlate the change with usage metrics to determine the root cause.
To use 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 setup Cloud Cost Management in Datadog, you need to generate a Cost and Usage report.
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
- Check the box for “Automatically refresh your Cost & Usage Report when charges are detected for previous months with closed bills.”
Select the following Delivery options:
- Time granularity: Hourly
- Report versioning: Create new report version
- Compression type: GZIP or Parquet
Configure the AWS integration
Select your AWS management account from the dropdown menu, allowing Datadog to display tags associated with this account. If you have multiple similarly-named management accounts, view the tags associated with a selected account to ensure you have selected the specific account you want.
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’s preferences:
- 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,
- 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
- 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
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.
You can visualize your ingested data using the following cost types:
|Cost based on applied discount rates plus the distribution of pre-payments across usage for the discount term (accrual basis).|
|Cost shown as the amount charged at the time of usage (cash basis).|
|Cost based on the average rate paid for a usage type across an organization’s member accounts.|
|Cost based on the list rate provided by AWS.|
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 also available for filtering and grouping data:
|The AWS service being billed.|
|The category for the AWS service being billed (for example, Compute or Storage).|
|The AWS management account name associated with the item.|
|The AWS management account ID associated with the item.|
|The AWS member account name associated with the item.|
|The AWS member account ID associated with the item.|
|The type of charge covered by this item (for example, Usage, or Tax).|
|Whether the usage is Reserved, Spot, or On-Demand.|
|The ARN of the Reserved Instance that the item benefited from.|
|The ARN of the Savings Plan the item benefited from.|
|The usage details of the item (for example, BoxUsage:i3.8xlarge).|
|The operation associated with the item (for example, RunInstances).|
|The region associated with the item.|
|The availability zone associated with the item.|
|The resource ID associated with the item.|
|The instance types associated with your items.|
|The instance family associated with your item (for example, Storage optimized).|
|Whether the usage is related to EC2 compute.|
|Whether the usage is on-demand.|
|Whether the usage is associated with a Reserved Instance.|
|Whether the usage is associated with a Capacity Reservation.|
|Whether the usage is associated with a Spot Instance.|
|Whether the usage is associated with a Savings Plan.|
Tag pipelines (beta)
You can use tag pipelines to create tag rules to help fix missing or incorrect tags on your AWS bill, or to create new, inferred tags that align with business logic.
There are two types of rules supported: Create new tag, and Alias existing tag keys. You can keep your rules organized by leveraging rules-sets, which act as folders for your rules. The rules are executed in order (from top to bottom), to keep the execution order deterministic. You can organize rules and rulesets to ensure the order of execution matches your business logic.
Create new tag - This allows you to create a new tag (key + value) based on the presence of existing tags. For example, you can create a rule to tag all resources that are part of team A, B, or C, and also run a specified application, with a new
Alias existing tag keys - This allows you to use values from an existing tag, to map to a more standardized tag key. For example, if you’re looking to standardize across your organization to use the
application tag key, but several teams have a variation of that tag (like
apps), you can alias
application. Each alias tag rule allows you to alias a maximum of 25 tag keys to a new tag.
The rule stops executing for each resource, once a first match is found. For example, if a resource already has a
web-app tag, then the rule no longer attempts to identify an
Note: A maximum of 100 rules can be created.
Cloud costs in dashboards
Visualizing infrastructure spend alongside related utilization metrics can help you spot potential inefficiencies and savings opportunities. You can add cloud costs to widgets in Datadog dashboards by selecting the Cloud Cost data source.
Additional helpful documentation, links, and articles: