-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Support for AWS Client VPN #6949
Comments
I'd like to take a shot at this but if someone has something already written up don't wait for me. |
I submitted #7009 which provides a resource that manages AWS Client VPN endpoints. If anyone wants to provide some additional testing, it would be much appreciated. |
Whoops sorry, the PR for the There is a followup PR for an |
This may be a dumb question but how do I link multiple PRs to an issue without one closing the issue upon merge? Just omit the "Fixes #XXX" line? |
@slapula Here's the relevant GitHub documentation: https://help.github.com/articles/closing-issues-using-keywords/ Personally, I just use something like |
Oh wow, I never realized that... Thanks! You learn something new everyday. |
The For any additional feature requests (e.g. a resource to manage Client VPN Routes) or bug reports, please open new issue(s). Thanks! |
The new |
Hi @bflad. Is there any new resource for adding routes and authorization rules? EDIT: I have seen that there is a pull request regarding the authorization ingresses: #7564 but I haven't found anything relevant to the Routes creation |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
AWS just released a new VPN service that works with OpenVPN-based clients
References
https://aws.amazon.com/about-aws/whats-new/2018/12/introducing-aws-client-vpn-to-securely-access-aws-and-on-premises-resources/
The text was updated successfully, but these errors were encountered: