Skip to content

Conversation

AlexanderJangAMZN
Copy link

@AlexanderJangAMZN AlexanderJangAMZN commented Mar 22, 2025

Enabling features for ipv6 and dualstack support with corresponding unit tests

Issue #33493

Closes #33493

Reason for this change

Currently, AWS Services, i.e., Xray, Wafv2, Workmail, have started to release support for IPv6 or Dualstack for their VPC endpoints. We would like to modify our infrastructure to be able to support. these new IP address types.

Description of changes

  1. Passed necessary props to the VPC Endpoint interface
  2. Added necessary props that need to be passed to enable all different IP address types
  3. Abstracted address types as enum to abide by L1, L2 constructs
  4. Added necessary unit tests to cover all cases
  5. Added necessary changes to integ tests

Added more detailed descriptions and guidlines for usage in the aws-ec2 README.md as well as very detailed comments above each code change.

Description of how you validated changes

Added unit tests and integ tests to cover all valid and invalid cases. Throws necessary errors according to documentation. Detailed descriptions of each case are outlined in comments.

Checklist


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@aws-cdk-automation aws-cdk-automation requested a review from a team March 22, 2025 07:56
@github-actions github-actions bot added beginning-contributor [Pilot] contributed between 0-2 PRs to the CDK effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2 labels Mar 22, 2025
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pull request linter fails with the following errors:

❌ Features must contain a change to an integration test file and the resulting snapshot.

If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: efb948b
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@daniilmc
Copy link
Contributor

This work has been moved to PR #33898, which contains an updated implementation.
Please close this PR as it's no longer needed.

@aws-cdk-automation
Copy link
Collaborator

This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing

To prevent automatic closure:

  • Resume work on the PR
  • OR request an exemption by adding a comment containing 'Exemption Request' with justification e.x "Exemption Request: "
  • OR request clarification by adding a comment containing 'Clarification Request' with a question e.x "Clarification Request: "

This PR will automatically close in 14 days if no action is taken.

mergify bot pushed a commit that referenced this pull request Apr 16, 2025
…esponding unit tests (#33898)

Enabling features for ipv6 and dualstack support with corresponding unit tests

### Original PR: [#3873](#33873)

### Issue [#33493](#33493)
Closes [#33493](#33493)

### Reason for this change
Currently, AWS Services, i.e., Xray, Wafv2, Workmail, have started to release support for IPv6 or Dualstack for their VPC endpoints. We would like to modify our infrastructure to be able to support. these new IP address types.

### Description of changes
1. Passed necessary props to the VPC Endpoint interface
2. Added necessary props that need to be passed to enable all different IP address types
3. Abstracted address types as enum to abide by L1, L2 constructs
4. Added necessary unit tests to cover all cases
5. Added necessary changes to integ tests

Added more detailed descriptions and guidlines for usage in the aws-ec2 README.md as well as very detailed comments above each code change.

### Description of how you validated changes
Added unit tests and integ tests to cover all valid and invalid cases. Throws necessary errors according to [documentation](https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html#connect-to-endpoint-service). Detailed descriptions of each case are outlined in comments.

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)
@aws-cdk-automation
Copy link
Collaborator

This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error.

@aws-cdk-automation aws-cdk-automation added the closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. label Apr 28, 2025
@github-actions
Copy link
Contributor

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

beginning-contributor [Pilot] contributed between 0-2 PRs to the CDK closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(EC2): Add support for dualstack OR ipv6 VPC endpoints

3 participants