Migrate From v3

SST v4 upgrades the underlying Pulumi AWS provider from v6 to v7. This guide covers migrating your SST v3 apps to v4.

Tip

SST components are already updated for v7. Most users only need to run sst refresh and deploy.

For the full list of upstream changes, refer to the Pulumi AWS v7 migration guide.

---

Breaking changes

No code changes are needed if you are only using SST components without transforms or direct @pulumi/aws usage. Otherwise, refer to the Pulumi AWS v7 migration guide for the full list of breaking changes.

The internal changes to SST components were minimal: mostly S3 resource renames (dropping the V2 suffix) and switching from tags to tagsAll. You can see the full list of changes in the upgrade PR.

---

Migration steps

When you update SST and the AWS provider version changes, sst deploy will be blocked until you migrate your state:

1. Install the latest v4

   Make sure you’re on the latest v4 version before running any commands.

2. Update your config

   If you have any breaking changes from above, update your sst.config.ts accordingly.

3. Review changes

   Run sst diff to preview what will change. This is a one-way migration, so it’s worth reviewing first.

   sst diff

4. Migrate state

   Run sst refresh to migrate your state.

   Caution

   Do not use the --target flag during migration. The state refresh must cover all resources to ensure a consistent migration.

   sst refresh

   Repeat for each stage.

   sst refresh --stage production

   If the stage was deployed using sst dev, use the --dev flag.

   sst refresh --dev

   If you share resources across stages, run sst refresh on the stage where the resource is created first — not the stage that references it via .get().

5. Deploy

   Once refreshed, deploy as usual.

   sst deploy

That’s it — once refreshed and deployed, your app is fully migrated to v4.

---

Upgrade testimonials

Upgrading your infra framework can feel scary. Here’s what teams have shared in Discord after migrating:

Successfully migrated two projects to SST v4.

waterbear

We just had a succesful upgrade too! Thanks team.

Zac

I just migrated our production app to SST v4. It's a fairly complex app with frontends, REST APIs, plenty of backend processes, usage of S3 buckets, DynamoDB, RDS, etc. Everything just worked fine.

Rodrigo

Excellent work on the upgrade to v4! I did a large project upgrade with no problems.

sockthedev

We flawlessly upgraded our production environment to v4 (ECS, RDS, SQS, etc.)

marv