Cost Archiver
Finout provides a simple way to manage long-term storage of cost data.
You can configure Finout to archive data in an AWS S3 bucket that you own. This allows you to store cloud spending data from your company’s various cost centers in one structured, easily accessible format.
Setting Up Cost Archiver
To output the cost data, Finout requires write permissions to an S3 bucket. To do this, create a new bucket or a new folder within the existing S3 bucket that’s used for your AWS CUR files.
Bucket permissions
If there are currently no policies applied to the bucket, please use the following policy:
If there are already statements
in the bucket’s policy, please add the following to the statements array:
If you wish to limit the write permissions to a specific folder within the bucket, please update the resource
portion as follows:
Archived cost data
Cost data will be updated once a day in the following structure: bucket/archiver_name/v1/yyyymmdd.json.gz
Cost data can be added retroactively by request, and there is no limitation regarding the archived data size.
Cost data structure
Field name
type
Description
time
Date (YYYY-MM-DDT00:00:00.000Z)
ㅤ
service
String
The type of service the cost is related to, for example, “EC2” (in AWS) or “Compute Engine” (in GCP).
region
String
The region the cost is associated with.
cost_center_type
String
AWS / GCP / K8s / Snowflake
costs
dict<string, double>
All the following costs: amortized_cost, net_amortized_cost, blended_cost, unblended_cost, net_unblended_cost, uncovered_cost, reservation_cost, savings_plan_cost, spot_cost
metadata
dict<string, string>
All metadata relevant to this cost line.
Still need help? Please feel free to reach out to our team at support@finout.io.
Last updated