FWIW I submitted a support ticket and asked our Technical Account Manager to bump it to the team working on the client. So far no action.
IP forwarding is currently disabled when using the AWS Client VPN Desktop Application. It has been disabled since the launch of the service on December 18, 2018, in order to address an issue reported by NIST. We understand, however, that some customers may need this functionality for their services. While we do not have a specific date at this time, we do plan to safely enable IP forwarding in an upcoming release.
And this was in... August 2022. There were releases since, none has fixed it.
If you're up for it, you could do the same - create a support ticket to move this to the team. Maybe if there's enough voices, they will make this higher priority.
Pinned Comments
project0 commented on 2021-06-28 15:58 (UTC) (edited on 2022-04-21 09:36 (UTC) by project0)
Please note the following requirements for AWS VPN Client:
If you depend on DNS servers from VPN you need to have a running systemd-resolved.service. Please ensure it does not conflict with any other DNS resolver service or configuration you may use.
sudo systemctl --now enable systemd-resolved.service
You have to enable and start the awsvpnclient.service after installation:
sudo systemctl --now enable awsvpnclient
For troubelshooting its worth checking first the logs:
See also the official docs: https://docs.aws.amazon.com/vpn/latest/clientvpn-user/client-vpn-connect-linux.html
If you face any other problem please check the troubleshooting guide (DNS issues): https://docs.aws.amazon.com/vpn/latest/clientvpn-user/linux-troubleshooting.html#aws-provided-client