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 think you'll just need two+ files,

`Pulumi.&lt;stack&gt;.yaml` like this...

Thanks I have edited my question so it is a clearer but what I am after is storing state in one account that can be used across other accounts. I don't think that will work with this setup?

I believe the only way to configure the S3 backend is with environment variables. So there's only one set of credentials available to pulumi to access the backend when invoking `pulumi`.

If you could add more details about your use case and how you would _like_ for it to work to <https://github.com/pulumi/pulumi/issues/4665>, that would be helpful.

<@U01HDAP5WM8> you can sort of do this by using the AWS environment variables for accessing your state store, then setting your provider configuration inside the stack. So for examples
```export AWS_PROFILE=shared_account
pulumi config set aws:profile=target_account```

You can also set an explicit provider on resources, which is something terraform/terragrunt can't do