Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AwsCommunity::Route53::VPCAssociation #266

Open
2 tasks
rhbecker-uw opened this issue Jan 17, 2025 · 0 comments
Open
2 tasks

AwsCommunity::Route53::VPCAssociation #266

rhbecker-uw opened this issue Jan 17, 2025 · 0 comments

Comments

@rhbecker-uw
Copy link

rhbecker-uw commented Jan 17, 2025

What type of extension are you looking for?

Resource

Describe the extension you'd like to request

I'm seeking implementation of an AwsCommunity::Route53::VPCAssociation resource type.

Issue 372, in the coverage roadmap repo, provides some high level details.

In my current use case, I'd like to use this new resource in lieu of embedding VPC associations within the VPCs property of the AWS::Route53::HostedZone resource type. (See below for further explanation as to why.)

Describe the solution you'd like

In a comment on a closely related issue 371, @rene84 indicates that an already developed set of resource extensions are being considered for inclusion in this repo. But that comment is from almost 2 years ago - I can't find any obvious evidence in this repo that this "migration" was ever discussed. Could this be (re)considered at this time?

Assuming the already developed solution is well implemented, this could be pretty low-hanging fruit. 🤷

The one I currently have an interest in using is Community::Route53::VPCAssociation, but there also seems to be broad interest in that repo's other Route53 custom resource - Community::Route53::VPCAssociationAuthorization.

Additional context

I'm attempting to implement Centralized access to VPC private endpoints, as described in the AWS Whitepaper: Building a Scalable and Secure Multi-VPC AWS Network Infrastructure.

I have a CFN template I'll use to create each VPC Endpoint to which I'm centralizing access. That template includes creation of the required private hosted zone.

Without a separate resource type to associate "client" VPCs, I'll have to manage the list of "client" VPC associations within the "service provider" stack, which seems undesirably circular (not to mention, difficult to maintain at scale); i.e. ...

  1. Create the endpoint stack ("service provider").
  2. Create one or more "client" VPC stacks.
  3. Update the endpoint stack ("service provider") with references to the "client" VPC stacks.

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request

Would this feature include a breaking change?

  • ⚠️ This feature might incur a breaking change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant