AWS Cost Explorer

Get cost and usage data from AWS Cost Explorer

Actions2

Cost and Usage Actions
- Get
Dimension Values Actions
- Get

Overview

This node integrates with AWS Cost Explorer to retrieve cost and usage data. Specifically, the Cost and Usage - Get operation fetches detailed billing information for a specified time range, granularity, and metrics. It is useful for financial analysis, budgeting, and monitoring cloud expenses over time.

Typical use cases include:

Tracking daily or monthly AWS costs to identify spending trends.
Comparing blended vs unblended costs.
Monitoring usage quantities of AWS resources.
Automating cost reports for finance teams.

For example, you can configure the node to get the total unblended cost for January 2023 on a daily basis, helping you spot spikes in spending.

Properties

Name	Meaning
Start Date	The start date for the cost query in `YYYY-MM-DD` format.
End Date	The end date for the cost query in `YYYY-MM-DD` format.
Granularity	The level of detail for the cost data. Options: `Daily`, `Monthly`, `Hourly`.
Metrics	The cost or usage metrics to retrieve. Multiple selections allowed:
	- Blended Cost: Cost that blends linked accounts' usage.
	- Unblended Cost: Raw cost without blending.
	- Usage Quantity: Amount of resource usage (e.g., hours, GB).

Output

The node outputs an array of JSON objects representing the AWS Cost Explorer response for the requested period and metrics. Each object contains detailed cost and usage data structured according to AWS's API schema, including:

Time periods covered.
Granularity of data points.
Metric values such as costs or usage quantities.

No binary data is output by this operation.

Dependencies

Requires valid AWS credentials with permissions to access AWS Cost Explorer.
The node uses the official AWS SDK client for Cost Explorer.
You must configure the node with an API key credential containing AWS Access Key ID, Secret Access Key, and region.

Troubleshooting

Invalid date format: Ensure Start Date and End Date are in YYYY-MM-DD format.
Missing or incorrect AWS credentials: Verify your AWS API key credential is correctly set up with necessary permissions.
API rate limits or throttling: AWS may throttle requests if too many are made; consider adding delays or retries.
Empty or incomplete data: Check that the date range and granularity are valid and that there is cost data available for the selected period.
Error messages from AWS SDK: These will be surfaced as node errors unless "Continue On Fail" is enabled, in which case error details appear in the output JSON.