feat: add privateDns parameter for interface endpoints #912
Conversation
This file contains hidden or 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
Add optional privateDns parameter to InterfaceEndpointConfig to allow disabling private DNS for S3 interface endpoints when needed for specific connectivity scenarios like Direct Connect. - Add privateDns field to IInterfaceEndpointConfig interface - Update network-config JSON schema - Update endpoint creation logic to use configured value - Maintain backward compatibility with existing default behavior
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue, #620
This PR adds an optional
privateDnsparameter to theInterfaceEndpointConfigto allow disabling private DNS for interface endpoints when needed for specific connectivity scenarios.Changes:
privateDnsboolean field toIInterfaceEndpointConfiginterfaceprivateDns: falseprivateDns: trueUse Case:
This addresses scenarios where S3 interface endpoints are needed outside the central endpoint VPC for specific connectivity requirements (e.g., Direct Connect), where disabling private DNS avoids conflicts with S3 gateway endpoints.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution under the terms of your choice.