sst deploy Command Reference

Deploy an SST application to a named stage.

sst deploy provisions your SST app to AWS for a given stage. SST v3 builds on Pulumi under the hood, so a deploy reconciles your infrastructure with the live state.

What it does

sst deploy builds your functions and frontends, then provisions or updates the underlying cloud resources for the named stage. It is non-interactive and is the command CI uses to ship both preview and production environments.

Common flags and usage

--stage STAGE: deploy to a named stage (per-branch or shared)
--print-logs: stream resource logs during deploy
--verbose: detailed output for debugging
sst deploy then sst remove --stage NAME: pair for ephemeral previews

Example

shell

- name: SST Deploy
  env:
    AWS_REGION: us-east-1
  run: npx sst deploy --stage prod

In CI

Pass --stage explicitly; a per-PR stage name gives isolated preview environments, and a fixed stage like prod ships production. Authenticate with GitHub OIDC against an AWS role rather than static keys. sst deploy is non-interactive, so no extra confirmation flags are needed.

Key takeaways

sst deploy provisions an SST app to AWS for a named stage.
Use per-PR stage names for isolated previews and a fixed stage for prod.
Authenticate with OIDC; the command is already non-interactive in CI.