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

<@U02GCR8KHL4> are you doing a stack per cluster/post request?

Well each client would get his own project and the cluster would be in a separate stack yes

you could do the automation API equivalent of
```pulumi config set aws:accessKey &lt;key&gt; --secret
pulumi config set aws:secretKey &lt;key&gt; --secret```

this would encrypt the values in state with a unique key per project, you'd just need to handle the values safely client side/in the browser

OK so just set the config inside the Pulumi Automation API?

yeah, with `ConfigValue`:

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/automation/#ConfigValue-secret>

I'm building (or planning to) something very similar, so if you're interested in comparing notes at some point, let me know

One more quick thing - what if I wanted to use the client’s Pulumi credentials? Is that also possible?

yes, you can set their access token: <https://app.pulumi.com/settings/tokens>,

i'm not sure we have a login method on automation api yet though, so you'd have to shell out to it

You don't have to shell out, you can just set the backend url

<@U01038HJ93R> Sorry can you elaborate a little? If you can point me to a short example, that’d be really helpful

Actually I think I might be misunderstanding… how do you want to use the client’s Pulumi credentials? 

<@U01038HJ93R> For example, say you want to create an EKS cluster in your client’s AWS and Pulumi (i.e. so the client can manage the pulumi state with their Pulumi account, not mine)