Hello Ia there an official guide on how to manage...
# general
a
Hello Ia there an official guide on how to manage IaC on a multi account setup? (Aws with aws organizations)
l
Too many answers to consider, an official guide might end up being bigger than wikipedia. Here's a few basics: • Use as many projects as you need based on functionality. Don't manage your org, your auth, your users, your apps and your VoIP in a single project. • Don't feel you have to manage everything in Pulumi. Start with something small like a single app and its infrastructure. Expand when you're ready. • Don't be afraid to completely rework the projects. Migrating resources between projects isn't easy, but it's easy to learn and get good at.
f
For multi accounts with the same functionality, e.g single tenant arch or different envs, using a stack per account for a single project allows nice duplication
a
I want to access the
nameservers
of my root management account, regardless if I'm deploying to my
development
account or
production
account
f
Export the nameservers details on the root stack and read that stack in the dev and prod stack, then you can access the fields (am guessing NS records for delegation)
a
yes, domain and sub domain delegation
that makes sense, a stack for each one •
root
development
production
The development stack would have its own resources per developer, those that make sense?