{"slug": "fck-nat", "name": "fck-nat", "category": "networking", "category_name": "Networking and VPN", "description": "", "recommenders": 3, "commenters": 3, "warners": 0, "score": 2.495, "rising": -0.98, "first": "2025-11-19", "latest": "2026-04-27", "why": "", "why_is_quote": false, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 0, "compare": 0, "warn": 0}, "spark": [2, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "", "kind": "", "icon": false, "domain": "fck-nat.dev", "github_repo": null, "official_url": "https://fck-nat.dev", "pricing": "", "aliases": ["fck-nat"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 766892673, "item_id": 47930792, "url": "https://news.ycombinator.com/item?id=47930792", "by": "leonardosul", "date": "2026-04-27", "version": null, "stance": "recommend", "quote": "fck-nat, which is great", "excerpt": "Repo: https://github.com/MachineDotDev/nat-zero We built this because we run GPU workloads across 22 AZs and most are idle most of the time. NAT Gateway would have cost us ~$792/month for AZs that mostly do nothing. Always-on NAT instances (fck-nat, which is great) were closer but still felt wasteful. nat-zero starts a NAT when a workload appears in a private subnet and stops it when the last one leaves. Idle cost is", "context": "", "use_case": "always-on NAT instances", "switched_from": "", "story": "Show HN: Nat-zero \u2013 Scale-to-zero NAT instances for AWS (Terraform module)"}, {"id": 735677632, "item_id": 45979852, "url": "https://news.ycombinator.com/item?id=45979852", "by": "wulfstan", "date": "2025-11-19", "version": null, "stance": "recommend", "quote": "consider using fck-nat", "excerpt": "This happens so often that the S3 VPC endpoint should be setup by default when your VPC is created. AWS engineers on here - make this happen. Also, consider using fck-nat (https://fck-nat.dev/v1.3.0/) instead of NAT gateways unless you have a compelling reason to do otherwise, because you will save on per-Gb traffic charges. (Or, just run your own Debian nano instance that does the masquerading for you, which every o", "context": "", "use_case": "cheaper NAT for AWS VPC", "switched_from": "", "story": "A $1k AWS mistake"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["always-on nat instances", "cheaper aws nat", "cheaper nat for aws vpc"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=45977744", "title": "A $1k AWS mistake", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=47930776", "title": "Show HN: Nat-zero \u2013 Scale-to-zero NAT instances for AWS (Terraform module)", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 2}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 766892673, "item_id": 47930792, "url": "https://news.ycombinator.com/item?id=47930792", "by": "leonardosul", "date": "2026-04-27", "version": null, "stance": "recommend", "quote": "fck-nat, which is great", "excerpt": "Repo: https://github.com/MachineDotDev/nat-zero We built this because we run GPU workloads across 22 AZs and most are idle most of the time. NAT Gateway would have cost us ~$792/month for AZs that mostly do nothing. Always-on NAT instances (fck-nat, which is great) were closer but still felt wasteful. nat-zero starts a NAT when a workload appears in a private subnet and stops it when the last one leaves. Idle cost is", "context": "", "use_case": "always-on NAT instances", "switched_from": "", "story": "Show HN: Nat-zero \u2013 Scale-to-zero NAT instances for AWS (Terraform module)"}, {"id": 735737680, "item_id": 45983605, "url": "https://news.ycombinator.com/item?id=45983605", "by": "the8472", "date": "2025-11-19", "version": null, "stance": "recommend", "quote": "", "excerpt": "Or go IPv6 and use an egress gateway instead. https://docs.aws.amazon.com/vpc/latest/userguide/egress-only-internet-gateway.html", "context": "", "use_case": "cheaper AWS NAT", "switched_from": "", "story": "A $1k AWS mistake"}, {"id": 735677632, "item_id": 45979852, "url": "https://news.ycombinator.com/item?id=45979852", "by": "wulfstan", "date": "2025-11-19", "version": null, "stance": "recommend", "quote": "consider using fck-nat", "excerpt": "This happens so often that the S3 VPC endpoint should be setup by default when your VPC is created. AWS engineers on here - make this happen. Also, consider using fck-nat (https://fck-nat.dev/v1.3.0/) instead of NAT gateways unless you have a compelling reason to do otherwise, because you will save on per-Gb traffic charges. (Or, just run your own Debian nano instance that does the masquerading for you, which every o", "context": "", "use_case": "cheaper NAT for AWS VPC", "switched_from": "", "story": "A $1k AWS mistake"}]}