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

The reason I even started going down this path was after configuring the AWS cli I spit out the AWS config and I'm currently seeing the following ....

```      Name                    Value             Type    Location
      ----                    -----             ----    --------
   profile                &lt;not set&gt;             None    None
access_key     ****************ISEZ              env    
secret_key     ****************0alB              env    
    region                us-east-1              env    ['AWS_REGION', 'AWS_DEFAULT_REGION']```

<@U03CZJBSKC4> the profile might be set inside the stack configuration, if you run a successful up with a config setting it gets passed to the stack config

I tried running `pulumi config rm aws:profile` right before `pulumi up` to see if that changed anything and it did not

Is it specified in code? When you construct the provider? Search for all provider constructors.

Have you output the value of AWS_PROFILE as seen by the CI job? Maybe that'll give you a hint where the value is coming from. Maybe an earlier step / action is setting it?