feat(core): PHZ-Resolver-Rules-Worldwide #395
Merged
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.
Phase 1
Phase 3
global-options/zones/<index>/names/public and privateusing VPC configuration specified in same indexaccountconfig/vpc/resolversuse-central-endpoints:truebased 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
outputs, use-central-endpoints and vpc regionuse-central-endpoints and vpc region.**This is Runs in Master Accounteg.. 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.