Is pulumi able to work with AWS profiles that use source_profile and role_arn? We have several AWS accounts so I have credentials for one account and cofigure cross-account access to other accounts. so I have an .aws/config that contains like

[profile is-signin]

[profile myprofile]
output=json
region=us-east-1
source_profile=is-signin
role_arn=arn:aws:iam::819835124123:role/Admins

so I can run aws cli like

aws s3 ls --profile=myprofile

and that works fine but when I configure pulumi to with

myprofile

it doesn't work.

Nice trick! Do you use that on Windows and how is the experience, if so?

Setting the AWS_PROFILE environment variable works for me on Mac, but I know some of my colleagues on Windows have had trouble with this (and just use temporary credentials generated by aws sts assume-role which they can put directly into AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN env vars).