Your route table looks fine but I think the problem here is DNS. What is your DNS server set to?
You can check that the split tunnel is working correctly by doing a
ping to a working external IP address. That's easy to find - when the VPN isn't running do
ping www.amazon.com and take note of the IP address. With the VPN running do
ping <IP address> and see if you get a response. If you do then DNS is definitely the issue.
Make sure that you can reach your DNS server when on the VPN. If the DNS server is in the VPC then it needs to be able to resolve IP addresses and return responses to your computer via the VPN tunnel.
When you enable split-tunnel mode, all the routes in the Client VPN endpoint's route table are added to the client's route table when the VPN connection is established. This operation is different from the default behavior, which overwrites the client's route table with the entry 0.0.0.0/0 to route all traffic over the VPN.
I am assuming the above route table is on your on-premise end. It is not recommended to add a 0.0.0.0/0 route to the Client VPN endpoint's route table when using split-tunnel mode.
Can you confirm if you have added the same ? If yes, can you remove 0.0.0.0/0 and try ?
Unable to access ElastiCache and Internet VIA VPNasked 9 months ago
AWS client vpn selfserviceasked 7 months ago
AWS SSO with GSuite external identify with AWS VPN Client Endpointasked 2 years ago
Unable to access internet from my laptop when I connect to a VPC using client VPNAccepted Answerasked 24 days ago
Why Can't I Associate Multiple Client VPN Endpoints in the Same Availability Zone?asked 2 days ago
Issues getting split-tunnel in client VPN endpoint to work correctly.asked 5 months ago
AWS VPN Client with fixed EIP for interfacesasked 3 months ago
AWS VPN Client on Linux Ubuntu not workingasked 2 months ago
VPN client endpoint interfaces have public IP, how to remove?Accepted Answerasked 2 years ago
VPN Client Endpoint - losing internet access even with split tunnel enabledasked a month ago