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 can't answer the first part, but for the second part, <https://www.pulumi.com/docs/intro/concepts/config/>

Yes, I think I understand generic per-stack config, but I didn't see how to associate a particular pulumi stack with an entry in my `~/.aws/credentials` file.

Yes, generally people use different AWS accounts for prod, dev, etc. stacks. This gives the best isolation of resources from impacting each other and best cost reporting from AWS as well.

<https://www.pulumi.com/docs/intro/cloud-providers/aws/#configuration> mentions `profile` setting

The access keys you provide to Pulumi determine the account that the operations run within. Using AWS profiles is a good way to do this.

Also, you can set `allowedAccountIds` as an extra measure to ensure your Pulumi stacks are operating in the right AWS account. <https://www.pulumi.com/docs/reference/pkg/aws/provider/#allowedaccountids_nodejs>

Oh drat, I just missed that entry. Thank you so much!