Is there a guide or a list of do’s and dont’s if we need to change the AWS account used for an app and all of its stacks? This gets confusing because all the resources live in the one AWS account and we’d need to spin up resources in the other AWS account. Almost everything is stateless (no databases thankfully)… so I’m hoping it’s not as crazy of a lift as it might be. Might as well throw out there that we had been considering changing the name of the project in Pulumi (don’t know if that has any bearing on anything, but I thought I’d mention it). Thanks for any pointers!

Probably don't need to "change the account"; just add new stacks for the new account(s). That way you can test that you have no hardcoded bits that you need to change. You should be able to configure the provider to have the right credentials based on the stack. Spin up the new stack, test, redeploy etc., then switch to the original stack and destroy.

I.e. I would take a

Pulumi.old.yaml

and create a

Pulumi.new.yaml

and then do something like

AWS_PROFILE=new-profile pulumi up

on the new stack?

No, you need a Pulumi.dev.yaml, Pulumi.otherregion.yaml, etc. No need to change Pulumi.yaml (probably)

I’m gonna give it a try…