Skip to content

Conversation

@naveenkoppula
Copy link
Contributor

Phase 1

  • Adding all interface endpoint hosted zones to outputs

Phase 3

  • Creating Route53 Public and private Hosted Zones mentioned under global-options/zones/<index>/names/public and private using VPC configuration specified in same index
  • Creating Route53 Resolver Endpoints based on accountconfig/vpc/resolvers
  • Create Route53 Resolver Rules for outBound Endpoint and MAD if required
  • Share Route53 Resolver Rules to Accounts whose use-central-endpoints:true based on region (eg.. vpc in perimeter account in region us-east-1 will get rules shared from us-east-1 rules created in shared-network account from global-options/zones/1/ config)

Phase 4

  • Create Association to Route53 Resolver Rules which is shared in phase-3 based on outputs, use-central-endpoints and vpc region
  • Create Association for Route53 Hosted Zones (interface-endpoints + private hosted zones) based on use-central-endpoints and vpc region. **This is Runs in Master Account
    eg.. VPC in us-east region in perimeter account will be associated to interface endpoints (excluding local endpoints) of us-east-1 region central vpc (global-options/zones/1/) and global private hosted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@naveenkoppula naveenkoppula merged commit c50c0fe into master Sep 18, 2020
@naveenkoppula naveenkoppula deleted the feat/PHZ-resolver-rules branch September 18, 2020 08:31
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

Successfully merging this pull request may close these issues.

2 participants