feat: Add zone-cross-account-vpc-association submodule #109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR add a new submodule to create cross-account Route53 VPC associations, using the authorization association resources (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-associate-vpcs-different-accounts.html)
Motivation and Context
For cross-account AWS documentation generally recommends using Route53Resolver. The API endpoint CreateVPCAssociationAuthorization is not even implemented in AWS Console.
However, this option is simpler as it does not require explicit resolver infrastructure (living within the VPC with specific Elastic Network Interfaces) and it does not involve cost on paying the Route53Resolver infrastructure, which makes it ideal for (most) cases.
Breaking Changes
N/A
How Has This Been Tested?
I have updated at least one of the
examples/*to demonstrate and validate my change(s)I have tested and validated these changes using one or more of the provided
examples/*projectsI have executed
pre-commit run -aon my pull request