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

It looks like we do not currently apply all the same AWS configuration options in configuring the client for `pulumi logs`.  See <https://github.com/pulumi/pulumi/blob/f6c25b7d2dd881ef892ce03b5cf1ca579b8c71e4/pkg/operations/operations_aws.go#L47-L61>.

How exactly are you configuring AWS in your case?  Is it just setting `aws:profile` to a valid profile in `~/.aws/credentials`?   Is that configuration working for deployments but not for `pulumi logs`?

Exactly. I have several profiles in `~/aws/credentials` and I set `aws:profile`in the stack's config (e.g. `Pulumi.dev.yaml`). This works fine for deployment, but not for `pulumi logs`, which uses the default profile of `~/.aws/credentials`.