You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dsotirho-ucsc opened this issue
Feb 20, 2025
· 1 comment
Assignees
Labels
--[priority] Lowdebt[type] A defect incurring continued engineering costinfra[subject] Project infrastructure like CI/CD, build and deployment scriptsorange[process] Done by the Azul team
Our client VPN endpoints are currently use the default value (disabled) for the Disconnect on session timeout setting On April 30th, AWS will be changing the default value to enabled for newly created client VPNs (see below).
We need to see what the consequences of enabling Disconnect on session timeout would be.
Note: Terraform currently does not offer a resource attribute for this setting.
Starting April 30, 2025, the default behavior for new AWS Client VPN [1] endpoints will change from disconnect-on-session-timeout=false to disconnect-on-session-timeout=true. This means that for new Client VPN endpoints created after April 30, 2025, if an administrator has set a maximum session duration time [2], users will need to manually reconnect to the VPN once their session expires. You can override this default behavior by specifying disconnect-on-session-timeout=false for any Client VPN endpoint.
Existing Client VPN endpoints created prior to April 30, 2025, will not be affected by this change. You can use the DescribeClientVpnEndpoints API [3] to view the current value, and the ModifyClientVpnEndpoint API [4] to change this setting for existing endpoints.
Disconnect on session timeout: This flag will disconnect your connection on session timeout which requires users to reconnect again manually. If disabled, Client VPN will attempt to reconnect the session after timeout automatically.
The text was updated successfully, but these errors were encountered:
Surely, TF support will be added soon. Assignee to monitor the TF provider documentation.
Once support is available, I'd like to test what effect enabling the setting has on the VPN client. The test should use a short session timeout. We have a mandate to implement a session timeout but there is no mandate to prevent clients from automatically reconnecting after the session times out. Enabling pro-active disconnects might actual help with VPN clients maintain persistent connectivity (my client gets stuck at times, preventing it from reconnecting).
hannes-ucsc
added
debt
[type] A defect incurring continued engineering cost
infra
[subject] Project infrastructure like CI/CD, build and deployment scripts
--
[priority] Low
and removed
debt
[type] A defect incurring continued engineering cost
labels
Feb 20, 2025
--[priority] Lowdebt[type] A defect incurring continued engineering costinfra[subject] Project infrastructure like CI/CD, build and deployment scriptsorange[process] Done by the Azul team
Our client VPN endpoints are currently use the default value (disabled) for the
Disconnect on session timeout
setting On April 30th, AWS will be changing the default value toenabled
for newly created client VPNs (see below).We need to see what the consequences of enabling
Disconnect on session timeout
would be.Note: Terraform currently does not offer a resource attribute for this setting.
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ec2_client_vpn_endpoint
From AWS:
The text was updated successfully, but these errors were encountered: