No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I'm having trouble getting pulumi to respect `aws:accessKey` and `aws:secretKey` in my stack config while using the automation api. Is this not possible or is there documentation I'm missing? I have `PULUMI_CONFIG_PASSPHRASE_FILE` set and it works when I take out the automation api parts and run pulumi up.

I guess it doesn't know about the config at all using inline. Maybe if I specify the workspace?

im not sure if this will help you but add your aws:profile in the config file for your stage

and then it will use that profile for future deployments