This message was deleted.

in other words I expected this to work:

The one way you could accomplish this today is to set the profile for your program via config instead of relying on the ambient

AWS_PROFILE

. That's a generally good practice to isolate your programs/stacks from ambient credentials that might need to change over time for other tools (or in this case,

pulumi login

). I believe it is not possible to specify

AWS_PROFILE

configuration explicitly for

pulumi login s3://

yet today.

to set the profile for your program via config

could you please tell me how to do that?

pulumi config set aws:profile profilename

See: https://pulumi.io/reference/clouds/aws/#configuration

from the example here https://pulumi.io/reference/clouds/aws/setup/ I've assumed that using AWS_PROFILE is the recommended way

Yes - it looks like the docs on that page could be improved to note that either

AWS_PROFILE

or the

profile

config setting can be used.

thanks a lot, will try to use the config settings