# automation-api


01/28/2021, 3:31 AM
Not doing it yet, but the thing I want to use it for is for managing accounts with dependencies as stacks with dependencies.
Have you any tips for getting started with setting up VPC peering, Route53 VpcAssociationAuthorization+ZoneAssocation, and similar? Is it enough to have one stack per account? I can see a very-complete pattern that requires 5 stacks (accountAPrePeering, accountBPrePeering, peering, accountADependentOnPeering, accountBDependentOnPeering), but I'd like something a lot simpler...
(AD shared domains would be nice too, but TF doesn't yet support that.)