This message was deleted.
# automation-api
s
This message was deleted.
l
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.)