AWS config in pulumi stack config is no longer respected

Issue

Previously, aws config, including aws:accessKey, aws:region, and aws:secretKey were used from the Pulumi.{stack}.yaml file.
This no longer seems to be the case after what I can only guess was a dependency update.
It was working on Even though pulumi itself was not updated, and no packages in the package.json (using TypeScript) were updated, a CICD build that used to work now no longer works with no changes. And using pulumi refresh no longer works locally.

I can’t recommend or use a tool that can break when I haven’t even updated anything myself.

Error Message

error: Preview failed: unable to discover AWS AccessKeyID and/or SecretAccessKey - see https://pulumi.io/install/aws.html for details on configuration

This page defined how to configure AWS credentials using the AWS CLI, which I am not using.

Config

This is the stack config I am using with sensitive info changed.

config:
  aws:accessKey: <accesskey>
  aws:region: <region>
  aws:secretKey:
    secure: <secret>

References

https://www.pulumi.com/docs/intro/cloud-providers/aws/#configuration

[ron137]

I have the same problem here, “pulumi up” is working fine, but “pulumi refresh” is not.

[MvnTruong]

Sorry to bring up a 2-year old issue, but I am just encounting this exact issue today where pulumi up works fine, but pulumi refresh does not, with the same error message error: unable to discover AWS AccessKeyID and/or SecretAccessKey - see https://pulumi.io/install/aws.html for details on configuration.

I have two stacks that have identical pulumi.X.yaml files. It can pick up the AWS creds for one stack but not the other