This message was deleted.

sparse-intern-71089

10/27/2021, 8:30 PM

This message was deleted.

billowy-army-68599

10/27/2021, 8:36 PM

it's a tough question to solve. You could use our SaaS 😉 but generally i recommend having a dedicated "infrastructure" account that stores states and host your bucket there

astonishing-quill-88807

10/27/2021, 8:37 PM

Makes sense (both answers 🙂 )

billowy-army-68599

10/27/2021, 8:39 PM

is our SaaS an option?

little-cartoon-10569

10/27/2021, 8:44 PM

Explicit AWS providers in code make this a lot easier to manage. Your default AWS creds (env vars) are used only for state storage; all Pulumi resources are created via explicit providers. Reduces risk of creating stuff in wrong account.

🙌 1

clever-painter-96148

10/28/2021, 4:09 PM

I never mix different AWS accounts in a single stack. When I want to share a bucket, I define it in a stack that's applied on the AWS account which holds the bucket, and I set a bucket policy that whitelist my org or part of it depending on my needs. Same as @billowy-army-68599: I have some kind of "infrastructure / shared services" accounts.

little-cartoon-10569

10/28/2021, 7:31 PM

Unfortunately it isn't always possible.. for example, setting up VPC peering requires access to 2 accounts. You could do it via 2 stacks, but then you'd have to write some state-detection code. It's much easier to use two providers to solve this sort of issue.

2 Views

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.