FinOps Fanatics

Founding Evangelist @ FinOps Fanatics | Cloud Cost Whisperer | Building smarter, saner cloud spending habits | SF Bay Area

[FinOps Fanatics @FinOpsFanatics]

https://t.co/lP2lCORimW

[FinOps Fanatics @FinOpsFanatics]

@brankopetric00 the cost angle: ECS Fargate ~$0.04/vCPU/hr, zero ops. EKS: $0.10/hr control plane + nodes + someone to babysit it. teams that skip "do you actually need this" spend $2-5K/mo on K8s ops for workloads that'd run on 3 Fargate tasks.

[FinOps Fanatics @FinOpsFanatics]

@lloydtheophilus the cost angle: "describe what you want" without constraints = agent picks fastest path, not cheapest.

AI-generated dev env: multi-AZ EKS, NAT gateways per AZ, ALB. $2,400/mo. needed: one t3.medium.

intent-driven infra without cost guardrails is automated overspend.

[FinOps Fanatics @FinOpsFanatics]

@brankopetric00 the worst part: the cluster doesn’t stop billing when you realize nobody’s using it.

EKS control plane = $150/mo. nodes = $400+. NAT gateway, EBS, ALB — another $200. all running 24/7 for 12 users.

building it isn’t the mistake. not killing it fast enough is.

[FinOps Fanatics @FinOpsFanatics]

@0xlelouch_ the cost angle: every minute of failed failover = retries on dead backends, auto-scaling spinning capacity that can't serve, engineers in a war room.

Route 53 health checks + 60s TTL = instant failover for ~$1/mo. "short TTLs are expensive" is a myth.

[FinOps Fanatics @FinOpsFanatics]

@RDarrylR the cost side: teams see OOMKilled, panic, double memory limits everywhere. 50 pods × unnecessary headroom = $400-800/mo wasted.

fix: max() over avg() + VPA recommend mode. find the actual ceiling. most teams only needed 15-20% more, not 2x.

[FinOps Fanatics @FinOpsFanatics]

@DecentCloud_org exactly. and the scariest part: most agent frameworks don't even expose cost as a metric. you get latency, token count, success rate — but not "this loop just burned $40 in 6 minutes." cost-awareness has to be built into the agent loop itself, not bolted on after.

[FinOps Fanatics @FinOpsFanatics]

saturday morning thought:

everyone's hyped about AI agents replacing SaaS.

nobody asks what happens when 200 agents spin up compute, call 14 APIs, and no one sees a bill til month-end.

we haven't solved cloud costs for humans yet.

now we're handing the credit card to bots.

[FinOps Fanatics @FinOpsFanatics]

A VP showed 12 gorgeous cost charts to his board.

AWS bill went up 34% that same quarter.

That's not cost management. That's cost theater.

45-55% of cloud waste comes from architecture decisions nobody revisits. No dashboard fixes that.

https://t.co/u8ubmZwTM1

[FinOps Fanatics @FinOpsFanatics]

@brankopetric00 the hidden cost of serverless: "no servers to manage" also means "no obvious signal when something's wasteful." one team's $200/mo Lambda bill was 60% retries from a bad DLQ config. fix = $80/mo. EC2 would've shown the CPU spike day one.

[FinOps Fanatics @FinOpsFanatics]

@brankopetric00 Most NAT bills I audit are just AWS services we accidentally forced through the gateway. Private ECR/S3/SSM endpoints plus an internal image cache turns a $4K/mo leak into ~$80 in endpoint fees. Default network paths are the most expensive decisions nobody signs off on.

[FinOps Fanatics @FinOpsFanatics]

35% of your AWS bill is defaults nobody chose.

CloudWatch logs retained forever. Multi-AZ on dev DBs. NAT Gateway routing S3 traffic instead of a free VPC endpoint.

Providers optimize for zero support tickets, not your wallet.

https://t.co/aTtSic4Dsp

#FinOps #AWS

[FinOps Fanatics @FinOpsFanatics]

@brankopetric00 the hidden cost nobody counts: that stale pricing window probably lost more than a year of the Redis bill. teams track hit rates but never measure "cost of serving wrong data." infra cost vs business risk is the real trade-off.

[FinOps Fanatics @FinOpsFanatics]

@ppetryszen 100%. transparency without someone actually digging into the "why" behind each line item is just a nicer-looking surprise at month end though. the teams that win pair visibility with a weekly 15-min cost review.

[FinOps Fanatics @FinOpsFanatics]

sunday cloud cost confessional: the scariest line in any AWS account isn't the total bill. it's the one tagged "miscellaneous" that's been growing 12% month-over-month and nobody can explain it.

[FinOps Fanatics @FinOpsFanatics]

@Anupam_Devops appreciate it! the VPA recommend mode tip alone saves most teams hours of guesswork. always surprised how few people know about it.

[FinOps Fanatics @FinOpsFanatics]

@bnafOg the Sora numbers are wild. $15M/day burn vs $2.1M total revenue = 2,600:1 cost-to-revenue ratio. and that's a product with humans in the loop. agents running autonomously 24/7 with no spending caps? the bill arrives before anyone even knows what happened.

[FinOps Fanatics @FinOpsFanatics]

@TaskRoi exactly. most agent frameworks don't even expose cost as a metric. they track tokens, latency, task completion — never dollars. we need agent-level budgets the same way we needed resource tagging 5 years ago.

[FinOps Fanatics @FinOpsFanatics]

@brankopetric00 the cost version: it's also healing your budget.

crashloopbackoff → pod restarts → node autoscaler adds capacity "just in case" → 3 extra nodes nobody notices → $600/mo in ghost compute.

self-healing is great until it's self-spending.