Notes from the team building C3X. Cost estimation for Terraform, the economics of cloud infrastructure, and how to ship FinOps tooling without a SaaS gate.
dbt Core is free and open source but you run and orchestrate it yourself. dbt Cloud is a paid managed service with scheduling, IDE, and collaboration. The cost comparison is subscription fees versus your own compute and engineering time. Here is how to choose.
AWS Direct Connect gives a dedicated private link with lower, predictable data-transfer rates but port and setup costs. A Site-to-Site VPN is cheap to start but runs over the internet at standard egress rates. Here is the cost comparison.
Amazon DocumentDB bills for instance hours, storage consumed, I/O operations, and backups, with a separate compute-and-storage model. Understanding each meter, and how I/O can dominate, is key to controlling DocumentDB cost. Here is the breakdown.
The VPC itself is free, and so are subnets, route tables, security groups, and internet gateways. The costs come from what you attach: NAT gateways, VPC endpoints, data transfer, and traffic through certain components. Here is exactly what you pay for.
AWS IAM itself is completely free: users, roles, groups, and policies cost nothing. The confusion comes from adjacent paid services like IAM Identity Center add-ons, Secrets Manager, and certain identity features. Here is what is free and what is not.
Terraform the open-source tool is free to download and use. HashiCorp offers paid HCP Terraform (formerly Terraform Cloud) tiers for teams. And separately, the infrastructure Terraform provisions costs money. Here is what is free and what is not.
DynamoDB cost hinges on capacity mode: on-demand bills per request with no planning, provisioned bills for reserved throughput you must size. Picking the right mode, and sizing provisioned capacity, is the core cost decision. Here is how.
Amazon EventBridge charges mostly per event published, with extras for schema discovery, replay, and cross-Region routing. The default event bus receiving AWS service events is free. Here is how EventBridge pricing works and how to keep it cheap.
Good FinOps measures efficiency, not just total spend. The KPIs that matter, unit cost, commitment coverage and utilization, waste percentage, forecast accuracy, and allocation coverage, each point to a specific action. Here is how to choose and use them.
The first AWS bill is confusing: dozens of line items, unfamiliar units, and charges for things you did not know were metered. Here is how to read it, which line items matter, and how to avoid the common first-bill surprises.
Cloud cost forecasting predicts future spend so you can budget, plan, and catch drift early. Good forecasts combine historical trends, known changes, and unit-based modeling. Here is how to forecast cloud costs accurately and what makes forecasts go wrong.
Amazon FSx offers four managed file systems (Windows, Lustre, NetApp ONTAP, OpenZFS), each priced differently for capacity, throughput, and IOPS. Costs vary widely by type and deployment. Here is how FSx pricing works and how to choose the cheapest fit.
Google Cloud billing reports break spend down by project, service, SKU, and label, with filters and grouping to find what drives cost. Here is how to read GCP billing reports, use SKUs and labels, and export to BigQuery for deeper analysis.
Google Cloud committed use discounts (CUDs) cut compute and other costs by roughly 20 to 57 percent in exchange for a one or three year commitment. Resource-based and spend-based CUDs work differently. Here is how CUDs work and when they save the most.
Google Cloud has two free offerings: a 90-day, roughly 300 dollar credit for new accounts, and an always-free tier with monthly allowances for specific services. Here is what is truly free, where the limits are, and how charges begin.
Google Cloud prices the same resources differently by Region, sometimes by 20 percent or more, and egress between Regions and to the internet varies too. Here is how GCP Region pricing works and how to pick Regions that balance cost, latency, and compliance.
Google Cloud Storage has four classes trading storage price against retrieval cost and minimum durations. Standard is cheapest to access, Archive cheapest to store. Here is how the classes are priced and how to pick the right one for each data set.
GitHub Actions bills by the minute for hosted runners, with multipliers for larger and non-Linux runners and per-GB charges for storage and data transfer. Here is how Actions minutes are priced, what the multipliers mean, and how to cut CI costs.
S3 Glacier Flexible Retrieval, Glacier Instant Retrieval, and Glacier Deep Archive trade storage price against retrieval speed and cost. Deep Archive is the cheapest storage at around a dollar per TB per month. Here is how the cold tiers compare and when to use each.
Provisioned concurrency keeps Lambda instances warm to eliminate cold starts, but you pay for that capacity around the clock whether it runs or not. Here is how the pricing works and when it is worth it.
Lambda charges per request and per GB-second and scales to zero; Fargate charges per vCPU and GB by the second for continuously running tasks. The cheaper option depends entirely on your traffic pattern. Here is how to choose.
Lift and shift moves workloads to the cloud as-is for speed, but often carries over-provisioned cost; refactoring for cloud-native services costs more up front but runs cheaper. Here is how to weigh the two.
Large language model APIs bill per token, split between cheaper input tokens and pricier output tokens, and the counts add up fast with long prompts and context. Here is how token pricing works and how to control it.
Logs are cheap to write and expensive to keep forever. A retention strategy that tiers, expires, and archives logs by value cuts storage and ingestion cost without losing what you actually need. Here is how to build one.