Table: aws_cost_by_record_type_daily - Query AWS Cost and Usage Report using SQL
The AWS Cost and Usage Report is a comprehensive resource that provides detailed information about your AWS costs. It allows you to view your AWS usage and costs for each service category used by your accounts and by specific cost allocation tags. By querying this report, you can gain insights into your AWS spending and optimize your resource utilization.
Table Usage Guide
The aws_cost_by_record_type_daily
table in Steampipe provides you with information about AWS costs incurred per record type on a daily basis. This table allows you as a financial analyst, DevOps engineer, or other professional to query cost-specific details, including the linked account, service, usage type, and operation. You can utilize this table to gather insights on cost distribution, such as costs associated with different services, usage types, and operations. The schema outlines the various attributes of the cost record, including the record id, record type, billing period start date, and cost.
Amazon Cost Explorer helps you visualize, understand, and manage your AWS costs and usage. The aws_cost_by_record_type_daily
table provides a simplified view of cost for your account (or all linked accounts when run against the organization master) as per record types (fees, usage, costs, tax refunds, and credits), summarized by day, for the last year.
Important Notes
- The pricing for the Cost Explorer API is per API request - Each request you make will incur a cost of $0.01.
Examples
Basic info
Determine the areas in which your AWS account incurs costs on a daily basis. This query helps you understand your spending patterns by breaking down costs into different categories, allowing you to manage your AWS resources more efficiently.
select linked_account_id, record_type, period_start, blended_cost_amount :: numeric :: money, unblended_cost_amount :: numeric :: money, amortized_cost_amount :: numeric :: money, net_unblended_cost_amount :: numeric :: money, net_amortized_cost_amount :: numeric :: moneyfrom aws_cost_by_record_type_dailyorder by linked_account_id, period_start;
select linked_account_id, record_type, period_start, CAST(blended_cost_amount AS REAL) AS blended_cost_amount, CAST(unblended_cost_amount AS REAL) AS unblended_cost_amount, CAST(amortized_cost_amount AS REAL) AS amortized_cost_amount, CAST(net_unblended_cost_amount AS REAL) AS net_unblended_cost_amount, CAST(net_amortized_cost_amount AS REAL) AS net_amortized_cost_amountfrom aws_cost_by_record_type_dailyorder by linked_account_id, period_start;
Min, Max, and average daily unblended_cost_amount by account and record type
Determine the areas in which you have minimum, maximum, and average daily costs associated with different accounts and record types. This can help you identify potential cost-saving opportunities and better manage your resources.
select linked_account_id, record_type, min(unblended_cost_amount) :: numeric :: money as min, max(unblended_cost_amount) :: numeric :: money as max, avg(unblended_cost_amount) :: numeric :: money as averagefrom aws_cost_by_record_type_dailygroup by linked_account_id, record_typeorder by linked_account_id;
select linked_account_id, record_type, min(unblended_cost_amount) as min, max(unblended_cost_amount) as max, avg(unblended_cost_amount) as averagefrom aws_cost_by_record_type_dailygroup by linked_account_id, record_typeorder by linked_account_id;
Ranked - Top 10 Most expensive days (unblended_cost_amount) by account and record type
Determine the days with the highest expenses, grouped by account and record type. This query can help in cost optimization by identifying the top 10 most expensive days, allowing for better budget management and resource allocation.
with ranked_costs as ( select linked_account_id, record_type, period_start, unblended_cost_amount :: numeric :: money, rank() over( partition by linked_account_id, record_type order by unblended_cost_amount desc ) from aws_cost_by_record_type_daily)select *from ranked_costswhere rank <= 10;
Error: SQLite does not support the rank window function.
Schema for aws_cost_by_record_type_daily
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
account_id | text | =, !=, ~~, ~~*, !~~, !~~* | The AWS Account ID in which the resource is located. |
amortized_cost_amount | double precision | This cost metric reflects the effective cost of the upfront and monthly reservation fees spread across the billing period. By default, Cost Explorer shows the fees for Reserved Instances as a spike on the day that you're charged, but if you choose to show costs as amortized costs, the costs are amortized over the billing period. This means that the costs are broken out into the effective daily rate. AWS estimates your amortized costs by combining your unblended costs with the amortized portion of your upfront and recurring reservation fees. | |
amortized_cost_unit | text | Unit type for amortized costs. | |
blended_cost_amount | double precision | This cost metric reflects the average cost of usage across the consolidated billing family. If you use the consolidated billing feature in AWS Organizations, you can view costs using blended rates. | |
blended_cost_unit | text | Unit type for blended costs. | |
estimated | boolean | Whether the result is estimated. | |
linked_account_id | text | The linked AWS Account ID. | |
net_amortized_cost_amount | double precision | This cost metric amortizes the upfront and monthly reservation fees while including discounts such as RI volume discounts. | |
net_amortized_cost_unit | text | Unit type for net amortized costs. | |
net_unblended_cost_amount | double precision | This cost metric reflects the unblended cost after discounts. | |
net_unblended_cost_unit | text | Unit type for net unblended costs. | |
normalized_usage_amount | double precision | The amount of usage that you incurred, in normalized units, for size-flexible RIs. The NormalizedUsageAmount is equal to UsageAmount multiplied by NormalizationFactor. | |
normalized_usage_unit | text | Unit type for normalized usage. | |
partition | text | The AWS partition in which the resource is located (aws, aws-cn, or aws-us-gov). | |
period_end | timestamp with time zone | End timestamp for this cost metric. | |
period_start | timestamp with time zone | Start timestamp for this cost metric. | |
record_type | text | The different types of charges such as RI fees, usage, costs, tax refunds, and credits. | |
region | text | The AWS Region in which the resource is located. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
unblended_cost_amount | double precision | Unblended costs represent your usage costs on the day they are charged to you. In finance terms, they represent your costs on a cash basis of accounting. | |
unblended_cost_unit | text | Unit type for unblended costs. | |
usage_quantity_amount | double precision | The amount of usage that you incurred. NOTE: If you return the UsageQuantity metric, the service aggregates all usage numbers without taking into account the units. For example, if you aggregate usageQuantity across all of Amazon EC2, the results aren't meaningful because Amazon EC2 compute hours and data transfer are measured in different units (for example, hours vs. GB). | |
usage_quantity_unit | text | Unit type for usage quantity. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- aws
You can pass the configuration to the command with the --config
argument:
steampipe_export_aws --config '<your_config>' aws_cost_by_record_type_daily