FREE CHECKLIST

Developers get infrastructure in minutes. Production stays safe.

Waiting days for the infra team to create a bucket or a queue slows every release. This is the checklist we use so developers ask Claude for infrastructure as a pull request, and guardrails catch anything unsafe before it reaches production.

The 12-step infrastructure self-service checklist

Google Doc · 12 steps · 10-minute read. Sent to your inbox in a minute. No spam.

We use your email to send this guide. See our privacy policy.

A TASTE OF WHAT IS INSIDE
  1. 01
    Write down your rules, once

    Encryption on, nothing public, required tags, approved instance sizes and a cost limit per change, in the CLAUDE.md file Claude reads in the repo.

  2. 02
    Guardrails on every pull request

    The Terraform plan as a PR comment, a cost estimate with an alert above your threshold, and security checks such as Checkov or Trivy.

  3. 03
    Only the pipeline can change the cloud

    No developer write access to the prod console. CI uses short-lived OIDC credentials, and prod needs an extra approval.

…and 9 more steps, from good examples in the repo to measuring how long an infrastructure request takes.

Written by the engineers at Cloud Solitaire, an AWS Partner that sets up and runs cloud infrastructure for growing teams.