AWS v7 Provider upgrade

[jamesgibbons92]

AWS provider upgade has some breaking changes which requires some manual intervention before the user should deploy using the new version.
The steps are explained here https://www.pulumi.com/registry/packages/aws/how-to-guides/7-0-migration

• Upgrade pulumi to latest version (this contains the new arg flag --run-program for refresh). (Thanks to @abnud11) This will be merged separately in another PR.
• Upgrade AWS from v6 -> v7 (Thanks to @abdnud11)
• Add provider major upgrade check when running sst deploy. Which asks the user to explicitly run sst refresh to migrate their state to the new version. Deploy/diff will be blocked until this is done and no resources in your state are using an outdated version.
• Add --run-program pulumi arg to refresh command, which is required for the migration.

[jamesgibbons92]

Draft message for release notes:

This release updates the aws provider from v6 to v7. This major upgrade contains a number of breaking changes and deprecations. Follow the guide here https://www.pulumi.com/registry/packages/aws/how-to-guides/7-0-migration/ to view the changes and update any affected pulumi aws components you may have.
There should be no breaking changes to your SST components (except for possibly any inputs you were transforming), however as part of the upgrade you must migrate your state using sst refresh before deploying with the new provider. It's advisable to also use sst diff after this command to ensure there are no unexpected changes.

[jamesgibbons92]

One thing to consider, adding support for --refresh arg to the deploy command, to automatically run refresh before deploy. This would provide a way of getting around having to do a manual refresh step before deploy and may be useful for people that have lots of stages to update.

[abnud11]

I hope we can push on this PR as a lot of features are blocked by it 👍
@jamesgibbons92 @vimtor

[jamesgibbons92]

@vimtor Now that pulumi has been merged I've updated this PR so it's good to review now.
I'm doing some more testing, but would appreciate a second pair of eyes on this as well!

[austeane]

Would love for this to be merged, it's key for my project, and I've switched to using this branch as my base.

[vimtor]

hey @jamesgibbons92

i left a couple of minor comments about the migration steps

everything else seems to be working. great job!

will be testing more examples today to see if they still work

[samuelzapote]

Really appreciate all the hard work. Just spent the whole day figuring out the "mx-central-1" region isn't supported yet because it needs this provider upgrade. Our non-profit team is really hoping to hit the ground running with sst on our nextjs project. We're rooting for y'all! 🥹🚀

We're currently getting Type '"mx-central-1"' is not assignable to type 'Input<Region> | undefined'. Did you mean '"me-central-1"'? when trying to initialize sst and setting the following config,

providers: {
  aws: {
    region: "mx-central-1"
  }
}

We've found out that the reason is because support for mx-central-1 was added in pulumi-aws v7.16.0. This PR will get us nearly there, hope we can have a quick follow up PR to bump it to 7.16.0 once this one merges. Leaving all the info I've found here in case anyone else runs into this problem, and in case this takes a while longer. (Animo banda, ya mero llega sst a Mexico! 🇲🇽🧑🏽‍💻)

Edit (Feb 14, 2026 💌): We're going to go ahead and work with an npm symlink to update our pulumi-aws to v7.16.0. Hopefully to help prepare any findings we run into for future contributions. See y'all soon! Happy Valentines Day lovely contributors. <3

[vimtor]

@samuelzapote viva méxico! a ver si mergeamos esto pronto

[kevinnorris]

Really looking forward to this upgrade. Any updates on how close it is to merging?

[vimtor]

@kevinnorris we’re looking to merge it this week or beginnings of the next

[vimtor]

soon after merging this i'll release a major v4 version

thanks everyone, especially the goat himself @jamesgibbons92