As part of my Pulumi code, I'd like to be able to be sure that I'm deploying the stack to the correct place (AWS account). I started off by using the

aws:profile

in the stack config; however when authenticating this way, I can't create and EKS cluster (gets error

could not get token: NoCredentialProviders: no valid providers in chain. Deprecated

). So now I have to use the environment variables. The problem is I could easily have the wrong environment variables and deploy my stack to the wrong place. Does anyone have any suggestions?

Re: EKS not supporting aws:profile - I believe that was fixed with https://github.com/pulumi/pulumi-eks/pull/205 which should be available in a release soon (or you can use “dev” tag to test it out). You can also do something like this to print out details of the current provider being used (or even go further and assert that you are targeting a certain account or set of accounts and fail the update if not): https://pulumi-community.slack.com/archives/C84L4E3N1/p1562694949223200?thread_ts=1562694728.222600&channel=C84L4E3N1&message_ts=1562694949.223200

Thanks, I'll have a play with that.