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

ec2 (S3): Disable "Enable private DNS only for inbound endpoint" when creating a VPC endpoint interface #29739

Open
2 tasks
Nuno09 opened this issue Apr 5, 2024 · 4 comments
Labels
@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2

Comments

@Nuno09
Copy link

Nuno09 commented Apr 5, 2024

Describe the feature

AWS introduced a new feature for VPC endpoint interfaces for S3 that enables/disables "private DNS only for inbound endpoint": https://aws.amazon.com/blogs/storage/introducing-private-dns-support-for-amazon-s3-with-aws-privatelink/

According to the current documentation, there is not a way to disable/enable this feature.
We are using the following class: https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_ec2/CfnVPCEndpoint.html

We would like to see the option to do so.

Use Case

We want to create a VPC endpoint interface for S3 where the "Enable private DNS only for inbound endpoint" is disabled.

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CDK version used

2.135.0

Environment details (OS name and version, etc.)

We are running CDK from a docker container with UBI-minimal 8.9, nodejs 20.12.0 and python 3.11

@Nuno09 Nuno09 added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Apr 5, 2024
@github-actions github-actions bot added the @aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud label Apr 5, 2024
@khushail khushail added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label Apr 5, 2024
@khushail khushail self-assigned this Apr 5, 2024
@khushail khushail removed the needs-triage This issue or PR still needs to be triaged. label Apr 5, 2024
@khushail
Copy link
Contributor

khushail commented Apr 5, 2024

Hi @Nuno09 , thanks for reaching out. Looks like this issue is also similar to the your request,however the PR assicated, is closed. Marking current request as appropriate

@khushail khushail added p2 effort/medium Medium work item – several days of effort and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Apr 5, 2024
@khushail khushail removed their assignment Apr 5, 2024
@Nuno09
Copy link
Author

Nuno09 commented Apr 8, 2024

Hi @khushail , thanks for checking. It is similar to that other issue, indeed. I believe the solution will be then similar, but a new accepted value could be needed to extend to the new "private DNS only for inbound endpoint"?

Here is a screenshot of such option:
image

@khushail
Copy link
Contributor

khushail commented Apr 8, 2024

@Nuno09 , this sounds great. So I have marked this as appropriate. Please feel free to submit a PR. Contributions from community are also welcome!

@devnox-labs
Copy link

Hello,

Do you have any update around this? this is also breaking for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2
Projects
None yet
Development

No branches or pull requests

3 participants