This message was deleted.

sparse-intern-71089

09/16/2020, 5:18 PM

This message was deleted.

incalculable-dream-27508

09/16/2020, 5:30 PM

I can't answer the first part, but for the second part, https://www.pulumi.com/docs/intro/concepts/config/

silly-address-30441

09/16/2020, 5:34 PM

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.

gentle-diamond-70147

09/16/2020, 5:34 PM

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.

✔️ 1

👍 1

incalculable-dream-27508

09/16/2020, 5:35 PM

https://www.pulumi.com/docs/intro/cloud-providers/aws/#configuration mentions

profile

setting

gentle-diamond-70147

09/16/2020, 5:35 PM

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.

gentle-diamond-70147

09/16/2020, 5:36 PM

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

👍 1

silly-address-30441

09/16/2020, 5:36 PM

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

silly-address-30441

09/16/2020, 5:36 PM

oh cool, that's great

Open in Slack

Previous Next

Pulumi Community

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.