-
Notifications
You must be signed in to change notification settings - Fork 4k
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: Support for ClientVpnEndpoint resources #4206
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
caphrim007
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
Sep 23, 2019
mergify bot
pushed a commit
that referenced
this issue
Mar 22, 2021
Add support for client VPN endpoints with the following L2s: `ClientVpnEndpoint`, `ClientVpnAuthorizationRule` and `ClientVpnRoute`. Client VPN endpoints can be added to VPCs with the `addClientVpnEndpoint()` method. Both mutual and user-based authentication are supported. The `ClientVpnEndpoint` class implements `IConnectable`. Use a custom resource to import server and client certificates in ACM for the integration test. Close #4206 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
eladb
pushed a commit
that referenced
this issue
Mar 24, 2021
Add support for client VPN endpoints with the following L2s: `ClientVpnEndpoint`, `ClientVpnAuthorizationRule` and `ClientVpnRoute`. Client VPN endpoints can be added to VPCs with the `addClientVpnEndpoint()` method. Both mutual and user-based authentication are supported. The `ClientVpnEndpoint` class implements `IConnectable`. Use a custom resource to import server and client certificates in ACM for the integration test. Close #4206 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
hollanddd
pushed a commit
to hollanddd/aws-cdk
that referenced
this issue
Aug 26, 2021
Add support for client VPN endpoints with the following L2s: `ClientVpnEndpoint`, `ClientVpnAuthorizationRule` and `ClientVpnRoute`. Client VPN endpoints can be added to VPCs with the `addClientVpnEndpoint()` method. Both mutual and user-based authentication are supported. The `ClientVpnEndpoint` class implements `IConnectable`. Use a custom resource to import server and client certificates in ACM for the integration test. Close aws#4206 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
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
Today, there exists a
VpnConnection
Construct, but support for aClientVpnEndpoint
does not appear to exist.The VpnConnection, "Specifies a VPN connection between a virtual private gateway and a VPN customer gateway or a transit gateway and a VPN customer gateway."
This feature is different from a ClientVpnEndpoint which requires less configuration on the customer side (for example, no coordination with IT departments to arrange VPN hardware/software internally)
ClientVpnEndpoint appears to have been added to CloudFormation in/around June 14th 2019
https://aws.amazon.com/about-aws/whats-new/2019/06/aws-client-vpn-includes-support-for-aws-cloudformation/
There are 4 resources that are related to this in CloudFormation
Ideally support for all of these are added. Perhaps different issues should be created for each?
Use Case
In our environment we make use of the ClientVpnEndpoint resource in CloudFormation because we do not have the ability to use other AWS VPN solutions. Additionally, we manage access to this VPN using certificates in ACM.
Proposed Solution
Propose that constructs be added to the EC2 package to support ClientVpn related constructs. Should the Constructs have a 1-to-1 relationship to the CloudFormation resources? or should the Construct present a more abstracted view of the resources?
I would be fine with a 1-to-1 relationship.
Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: