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

Hi! Does anyone happen to know if it's possible to set static credential values for a storage backend?

I'm using a self-hosted Minio bucket as a backend. It's wanting to use the `AWS_*`  variables for authentication, creating a credential knife fight when trying to deploy AWS resources.

Running this doesn't store the credentials in `~/.pulumi/credentials.json`:

```AWS_ACCESS_KEY_ID=minio-id AWS_SECRET_ACCESS_KEY=minio-secret \
pulumi login "<s3://bucket?endpoint=http://my-server:9000&amp;ForcePathStyle=true>"```
Is the only real option to update the Pulumi program and set credentials manually in the provider?

&gt; Does anyone happen to know if it's possible to set static credential values for a storage backend?
Unfortunately not. All the storage backend logic goes through <http://gocloud.dev|gocloud.dev>, I don't know if there's a backend agnostic way to pass options down with that.

Thanks so much for the fast response!

I'll stop being lazy and update the Pulumi program.