NAT gateways cost $36.50 a month per AZ before moving a byte, then $0.045 for every gigabyte. We find what is going through NAT, move AWS traffic onto endpoints, and replace the gateways with fck-nat where it fits: deployed as code, highly available per AZ, with alarms, a patch routine and a rehearsed rollback.
1–2 weeks
$3k–$8k
The NAT gateway is the most common surprise on a startup's AWS bill: an hourly charge in every Availability Zone, and a per-gigabyte charge on traffic that often never needed to leave through it. Most of that can go. We measure first, take the free wins, and replace the gateways with fck-nat instances where your traffic suits them, keeping a managed gateway where it doesn't.
Turn on VPC Flow Logs and query them in Athena: which subnets, which destinations, how many gigabytes
Read NatGateway-Hours and NatGateway-Bytes in Cost Explorer for the baseline
Gateway endpoints for S3 and DynamoDB
Interface endpoints for high-volume AWS services such as ECR and CloudWatch Logs, where they pay for themselves
IPv6 egress for destinations that support it, where your stack allows
fck-nat per AZ in high-availability mode, sized from the measured sustained bandwidth
Route tables switched one AZ at a time, with the managed gateway left in place until each AZ is proven
Alarms, a monthly AMI roll, and a written rollback
Infrastructure as code in your repository
The Flow Logs queries, so you can rerun the analysis
The cost before and after, and the runbook
Tell us about your current environment and goals. We'll review the details and respond with a proposed engagement structure and timeline.
Typical response time: 1–2 business days.
Prices and timelines are estimates for typical engagements, not offers. Scope, price and terms are set in a written agreement after we understand your situation. Terms of use.