and there is no

--account

property to tell sst which account to use. Seems like sst wants to use it's own way of authenticating cdk calls. Are there workarounds or is sst going to support CDK v2 way of selecting region/account?

I get around this the old fashioned way: I make an array of what is accepted, then check in the app if it matches, or else throw an error.

@Andrea Sciutto are you looking to create stacks to deploy to multiple AWS accounts in a single SST app?

I think its more about NOT allowing it, @Frank. For instance, if I accidentally run the

sst deploy

command without setting

profile

a stack may deploy to another account. With the CDK itself, there is an option to set the account so an error would be thrown in this case, but not so with SST.

Ah gotcha! That makes sense.. definitely did that myself 😅