Hey, i am new to pulumi. can someone share with me what are the best practices for using pulumi with different aws accounts and state buckets, regarding different variables values, using remote state and so on? thanks in advanced.
04/21/2020, 2:04 PM
Do you have any more details on what specifically you are looking for?
For state management, you can just leave that up to the Pulumi service backend if you want - so you shouldn’t have to worry about that up front.
For working with multiple AWS accounts, you can easily do that either from a single program (create aws.Provider instanced for each account), or by deploying multiple stacks from a single project, each to a different account. Which of these makes sense for you really depends on your workload, but starting off with a single program is likely the easiest place to get going.
04/21/2020, 7:55 PM
Hey Luke, thanks for your response. the goal is to be able to create different stacks in different environment and to be able to deliver different values for each one of them. for example create an ecs cluster with autoscaling group on one account and without autoscaling group in second account. until now i was using terraform with a structure of module and live for parameters passed to the module for each account and environment, and i wonder what are the best practices for that in pulumi. any relevant documentation would be great. i have started from that one: https://www.pulumi.com/blog/controlling-aws-costs-with-lambda-and-pulumi/