Bootstrap your cloud

placemy needs exactly one piece of cloud infrastructure: a state bucket where it writes scan history, diffs, and the derived metadata the Optimise pass uses between runs. You can let placemy create it for you (AWS only, for now), or you can register a bucket you already own (Azure, GCS, or AWS).

The one-liner: AWS

If you have AWS credentials and the IAM permissions to create an S3 bucket and write a Systems Manager parameter, this is the path of least resistance:

placemy bootstrap --provider aws

This creates an S3 bucket called placemy-state-<account-id> in your default region, locks it down (public access block, SSE-S3 encryption, versioning), and writes its URI to the SSM parameter /placemy/state-bucket so other machines in the same account pick it up automatically.

Dry-run first if you want to see the plan without applying it:

placemy bootstrap --provider aws --dry-run

BYO bucket: Azure Blob Storage

placemy does not create Azure resources for you — the IAM story is too variable to automate safely. Create a container in the portal or with az storage container create, then:

placemy bootstrap --provider azure --uri https://myacct.blob.core.windows.net/placemy-state

The URI is written to ~/.placemy/config.toml under the [bucket] section.

BYO bucket: Google Cloud Storage

Same story as Azure. Create the bucket, then register it:

placemy bootstrap --provider gcp --uri gs://my-placemy-state

What goes in the state bucket?

Per-scan directories, each containing a JSON snapshot of the resource graph and the rule outputs. Nothing in here is required for a scan to work — if the bucket vanishes, the next scan will rebuild its own state. The bucket exists so that diffs between scans are possible and so that a team can share history.