You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using a multi account AWS Setup (consolidated billing) with unified PRIVATE and PUBLIC DNS Namespace. As transitive routing is not supported, we need to associate PRIVATE Route53 Zones in sibling / project / department accounts to a VPC in a shared services account which hosts some DNS Servers. This allows DNS self service for the users and transparent DNS resolution.
Until now we needed to open a ticket with AWS which takes a lot of time to do the cross account association. Now AWS added API Support for this (woohoo!):
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 18, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
we are using a multi account AWS Setup (consolidated billing) with unified PRIVATE and PUBLIC DNS Namespace. As transitive routing is not supported, we need to associate PRIVATE Route53 Zones in sibling / project / department accounts to a VPC in a shared services account which hosts some DNS Servers. This allows DNS self service for the users and transparent DNS resolution.
Until now we needed to open a ticket with AWS which takes a lot of time to do the cross account association. Now AWS added API Support for this (woohoo!):
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-associate-vpcs-different-accounts.html
Currently Terraform does not support this. It would be great if this would be added.
Regards,
Robert
The text was updated successfully, but these errors were encountered: