vol. 2 of 3 · let claude deploy it

Deploy Your App with AI

Deploy Your App with AI, vol. 2, cover

Claude deploys your app to AWS. You approve every step. A guard stops it deleting data.

$39

or all three for $60 save $37

pdf + zip · instant download · 14-day refund · credits aren't guaranteed

pages + the starter kit
85
paste-into-Claude prompts
20
linked sources
85
checked september 2026
2026.09
vol. 2 · p. 5

what's inside.

“Claude types. you approve. your app goes live on AWS.”the cover

01 / connect Claude to AWS

  1. Get Claude Code running (on the “in a hurry” route), page 6
  2. Make it ask first (on the “in a hurry” route), page 8
  3. Connect your terminal to AWS (on the “in a hurry” route), page 12
  4. Prove the connection inside Claude (on the “in a hurry” route), page 16
  5. Which Claude login pays?, page 17

02 / choose a stack that fits

  1. Tell Claude what matters, page 18
  2. Existing app: inspect, then plan the move, page 21
  3. Pick one starting route (on the “in a hurry” route), page 25
  4. Networking and quiet costs, page 32
  5. Ask for a plan you can approve, page 36

03 / build it. then launch it.

  1. Keep the app separate from the deployer, page 39
  2. Red flags in what Claude drafts, page 43
  3. Build Route A, page 44
  4. Review the exact first deployment, page 51
  5. Keep a human in the loop (on the “in a hurry” route), page 56

04 / keep it working

  1. Two budgets and a quieter alarm, page 57
  2. Fix the first useful error, page 63
  3. If a key leaks, page 64

starter kit + reference

  1. What's in the kit, page 68
  2. Sources, page 80

In a hurry? Do pages 7–16, then 25 and 56. That's the method in 15 minutes of reading. the reading map, p. 5

the starter kit · every file the book talks about

Files in the starter kit, with the page of vol. 2 that explains each one
filewhat it doesvol. 2
AGENTS.mdrules for Claude Code and Codexp. 69
.claude/settings.jsonask-first mode, deny rules, the hookp. 70
.claude/hooks/guard.shblocks destructive commandsp. 71
compose.yamlCaddy, the API and Postgresp. 72
CaddyfileHTTPS routing (with backend/Dockerfile, the API image)p. 73
ops/backup.shbackups, with a systemd timerp. 74
ops/restore-test.shrestores into a throwaway containerp. 75
iam/guard-policy.jsondenies deleting databases, snapshots and backupsp. 77

also in the zip: the instance role policy (p. 76), the systemd timer files and a README.

three real pages

  • Vol. 2, page 26: One server is enough to start
    p. 26 One server is enough to start
  • Vol. 2, page 56: Keep a human in the loop
    p. 56 Keep a human in the loop
  • Vol. 2, page 71: guard.sh: a second seatbelt
    p. 71 guard.sh: a second seatbelt

no email needed: read 12 pages of vol. 1 first →

vol. 2 · p. 8

make it ask first.
every time.

Claude checks the account first and drafts every change for you to read. You say yes or no. A guard policy stops it deleting databases, snapshots or backups, even if you say yes.Claude drafts every change. You say yes or no. A guard policy denies deleting your AWS databases, disks and backups, even after a yes.

  1. change 01 · claude wants to

    create one small server

    about $19 a month · one EC2 server

    yes.
  2. change 02 · claude wants to

    set a $1 alert on the credits

    so they can't run out silently

    yes.
  3. change 03 · claude wants to

    delete the old database

    rds · no final snapshot

    yes. blocked.

paste into claude / 01 / check the connection

Check our local AWS connection before we talk about architecture. Use the AWS CLI with the founder-project profile. Run aws sts get-caller-identity and report the account and ARN. Confirm AWS_PROFILE and the Region in use, without showing any credential values.

Compare them with what I expect: account ending in [last 4 digits], user founder-deploy, Region [us-east-1]. Stop if anything differs, the login has expired, the identity is root, or you can't run the CLI here. Don't create resources, edit IAM, read secret values or change project files.

Report: project folder, profile, account, identity, Region, then PASS or the exact problem to fix.

from vol. 2 · p. 16 · one of 20 prompts in the book
the guard policy is on p. 77. the hook that blocks deletes is on p. 71.

who it's for.
who it isn't.

this is for you if

  • You'd rather approve what Claude drafts than type AWS commands yourself.
  • You have an app, new or already running (even on Supabase or Vercel), and want it live on AWS.
  • You want a backup you've actually restored, not just made.
  • You want a cost in dollars before anything gets created.

skip it if

  • You want an agent that deploys on its own. Here Claude asks first, every time.
  • A free plan already covers your app for good. Keep it.
  • You already have a DevOps team and a big AWS bill.

one route.
three books.

Get the credits, let Claude deploy your app, then run AI on the same credits. Each book stands on its own. Together they are the whole route I use.

  1. 1 get the credits

    The $0 Hosting Playbook

    Get startup credits: AWS Activate, NVIDIA Inception, and the landing page that got me in.

    vol. 1 · 67 pp · $29

  2. you're here.

    2 let claude deploy it

    Deploy Your App with AI

    Claude deploys your app to AWS. You approve every step. A guard stops it deleting data.

    vol. 2 · 85 pp · starter kit · $39

  3. 3 add ai, same credits

    The $0 AI API Playbook

    Run Claude and other models on the same credits, through Amazon Bedrock.

    vol. 3 · 59 pp · $29

all three + the starter kit

instead of $97 $60 save $37

what's in the bundle →

14-day refund · pdf + zip · instant download

questions.

Anything else? ahmed@nexarlabs.co.uk

Which Claude plan do I need?

Claude Code signs in with a Pro, Max, Team or Enterprise plan, or a Console account. It can also sign in through Amazon Bedrock, so AWS bills the tokens and your credits can pay them. Page 17 compares the two logins.

Is the starter kit ready for production?

It's a starting point. I wrote it from the official docs. Read it, replace the placeholders and test it with fake data before your real data depends on it.

Do I need to know AWS already?

No. You don't need to know all 200 services. You need to know what you're approving. In vol. 2, Claude drafts every command and file, and you read and approve each step, from your first login to a live app.

Do I have to leave Supabase and Vercel?

No. They're good tools, but their free plans aren't built to run a business: Vercel Hobby is for non-commercial use only, and Supabase Free pauses after about a week of low activity, with no backups. If you do move, vol. 2 moves one piece at a time: compute first, then data, then login. Your API on AWS can keep talking to your Supabase database.

What do I get after I pay?

An instant download of the PDFs you bought, plus the starter kit with vol. 2 or the bundle. The same links come by email. Updates are free when AWS or NVIDIA change their screens. If it's not for you, email me within 14 days for a refund.

Are you sponsored by AWS, NVIDIA or Anthropic?

No. These are independent guides. AWS, NVIDIA and Anthropic don't sponsor or endorse them, and their names belong to them. My company, Nexar Labs, is a member of NVIDIA Inception, the program vol. 1 walks you through.

all 3 books · $60
14-day refund