Arch Linux User Repository

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:

/home/$USER/.config/AWSVPNClient/
/var/log/aws-vpn-client/$USER/

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

@damentz Thanks! For some reason it worked out well. Took some time to figure out the nss which even broke my boot up and wifi connection on boot.

Regardless it worked! I am amazed at how efficient the AUR community is.

@dcaixinha The log message you shared looks normal to me. Can you check if xdg-open 'http://google.de' works (package xdg-utils if not installed..) ? Maybe there is just an issue with opening the browser (Not sure if this is the mechanism the AWS tool is using)

I've followed the suggestions below to enable systemd-resolved and awsvpnclient services, they're both running, but when I try to connect I get an "unexpected error" message and in the logs I see:

2021-06-30 15:32:07.409 +01:00 [DBG] [TI=18] [PID: 5416] Wed Jun 30 15:32:07 2021 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:8096
2021-06-30 15:32:07.409 +01:00 [DBG] [TI=18] [PID: 5416] Wed Jun 30 15:32:07 2021 Need password(s) from management interface, waiting...

I'm using federated-auth in the client config and it should open up a browser window when it reaches this stage, but nothing happens. Any hints from anyone?

@ambots13, if you didn't have systemd-resolved originally, that means you still have more to configure. Check the wiki: https://wiki.archlinux.org/title/Systemd-resolved

1) Their first suggestion is to replace /etc/resolv.conf with a symlink to systemd-resolved's stub: ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf.

2) Update /etc/NetworkManager/NetworkManager.conf to specify which DNS subsystem you're using:

# Configuration file for NetworkManager.
# See "man 5 NetworkManager.conf" for details.
[main]
dns=systemd-resolved

3) Update /etc/nsswitch.conf to support resolve resolution: https://man.archlinux.org/man/nss-resolve.8

For example: hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns

Distributions that are configured to use systemd-resolved do all these things ahead of time, but to convert over from a non-systemd-resolved system requires more than simply turning on the service. You have to inform your system to use it at the network manager and system level, as shown in the examples above.

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:

/home/$USER/.config/AWSVPNClient/
/var/log/aws-vpn-client/$USER/

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

Hey there, just updated the package with a patched desktop file (KDE).

@jantman Thanks sharing the fixes in KDE,

I have managed to run system-resolved followed by enable system-resolved.service

However, I still can't connect. Is there a specific config I need to modify that is not out of the box?

I am new to arch btw

The .desktop file needs spaces double escaped. After adding spaces using KDE's application shortcut UI, it turned the exec from:

Exec=/opt/awsvpnclient/AWS\ VPN\ Client %u

to

Exec=/opt/awsvpnclient/AWS\\ VPN\\ Client %u

After this, launching the VPN client through launcher works.

EDIT: When running kbuildsycoca5 to process .desktop file updates, you can see the error that something is wrong with the file:

kf.config.core: "KConfigIni: In file /usr/share/applications/awsvpnclient.desktop, line 6: " "Invalid escape sequence \"\\ \"."
kf.config.core: "KConfigIni: In file /usr/share/applications/awsvpnclient.desktop, line 6: " "Invalid escape sequence \"\\ \"."

@jantman thanks for the info. I can add a hint during the installation (like the awsvpnclient service).

The problem with the destkop file is strange, with Gnome it works perfectly fine. However, we can add per default a softlink to the package as general workaround.