127.0.0.53 is not a DNS server!
Like a few reviews have mentioned, this image has trouble resolving domain names. My client can reach the admin page without issue, but it fails to connect to the internet. I don't know why this hasn't been fixed already in this AMI, but /etc/resolvd.conf is linked to the broken stub-resolver configuration. The fix is very simple, but it took hours to figure the default system configuration was broken.
Try to navigate to Web UI -> Configuration -> VPN Settings -> Routing -> Should client Internet traffic be routed through the VPN? -> Yes.
Hello! Thank you for bringing this issue to our attention. We are aware and working quickly to develop a solution moving forward. If you encounter this issue again, you can update your Access Server to the latest version with instructions here: https://openvpn.net/vpn-server-resources/keeping-openvpn-access-server-updated/ which will resolve the issue. You can also specify specific DNS servers to push in the VPN Settings page. We are currently working to have the latest release of Access Server available on the AWS Marketplace, which will be the latest version at launch. Please let us know if you have any other questions or how we can ensure you are happy with our product.