I Followed the Official AWS Amplify Guide and Was Charged $1,100

Original Article ↗ Hacker News Discussion ↗

AWS billing surprises and responsibility

  • Many comments describe large unexpected bills from AWS guides or misconfigurations (SageMaker, Shield Advanced, S3 Glacier, high‑IOPS disks, ECS/Fargate, OpenSearch), sometimes in the hundreds or thousands of dollars.
  • Some report AWS readily issuing refunds as a “one‑time courtesy”; others say support refused, leading them to avoid AWS entirely.
  • There is disagreement on responsibility: some argue users must be “paranoid” and manually sweep accounts for stray resources; others say that’s unreasonable for tutorials and that official tooling/scripts should default to cheapest options and fully clean up.
  • Tutorials and “wrapper” services (Amplify, CDK, SageMaker high‑level tools, Beanstalk) are seen as especially risky because they create hidden resources across services/regions.

Lack of hard spend limits

  • Strong recurring demand for true hard spending caps, ideally set at account creation and per environment.
  • Critics see current “billing alerts,” budgets, anomaly detection, and Cost Explorer as insufficient and reactive.
  • Some argue hard caps are technically or operationally complex at AWS scale, and potentially harmful for enterprises if they cause downtime; others call this an excuse, noting smaller providers and Azure sandboxes offer caps and that AWS already solves harder problems.
  • A few suggest regulatory intervention to force spend limits; others distrust regulation or say AWS’s enterprise‑centric incentives make this unlikely.

Cloud vs self‑hosting and alternative providers

  • Many praise self‑hosting or bare metal (home servers, OVH, Hetzner, Exoscale, Vultr, dedicated boxes) as cheaper, simpler, and emotionally safer for modest workloads.
  • Others point out clear wins for cloud: massive short‑term scale (e.g., hundreds of GPUs for hours), serverless Lambda with generous free tiers, or managed training environments.
  • There’s consensus that cloud is not inherently cheaper; it trades hardware/admin complexity for billing/architecture complexity, and requires new skills (FinOps, careful design).

AWS tooling, docs, and UX

  • AWS documentation and examples are frequently criticized as inaccurate, confusing, and cost‑oblivious; CDK defaults (e.g., removalPolicy) and Amplify extensibility docs are cited as footguns.
  • Several complain it’s hard to get a unified view of all billable resources; available tools (tag editor, Config, Cost & Usage reports) are fragmented and incomplete.

Learning, sandboxes, and adoption barriers

  • Some avoid AWS entirely due to fear of runaway bills and the credit‑card requirement, wishing for safe, free, time‑limited sandboxes.
  • Third‑party training platforms with auto‑teardown sandboxes are praised as a safer way to learn.