Client Connection Handler for Client VPN Endpoint

[KyleKotowick]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS Client VPN Endpoints support a featured called "Client Connection Handler", which is a Lambda function that dynamically determines if a client should be allowed to connect or not. Currently, the Terraform AWS provider does not have any configuration option to support this feature.

New or Affected Resource(s)

• aws_ec2_client_vpn_endpoint

Potential Terraform Configuration

aws_ec2_client_vpn_endpoint "client_vpn" {
  ... existing config options
  client_connect_handler_arn = aws_lambda_function.vpn_connection_handler.arn
}

Note that there are a couple restrictions on the Lambda that would be good to check. Namely, its name must start with the prefix "AWSClientVPN-" and it must have a timeout of 30 seconds.

[ewbankkit]

Announcement.

Requires AWS SDK v1.35.21:

• build(deps): bump github.com/aws/aws-sdk-go from 1.35.19 to 1.35.21 #16021

[ewbankkit]

Strictly speaking the new syntax should be

aws_ec2_client_vpn_endpoint "example" {
  client_connect_options {
    enabled = true

    lambda_function_arn = aws_lambda_function.example.arn
  }
}

to match the AWS API.

[choeflake]

Hi, could this issue get some prio?

[github-actions]

This functionality has been released in v4.0.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.