I see that you have a problem connecting to your AWS Client VPN service because the IP address associated with it is continuously changing,
This is an expected behavior of the AWS VPN Client service, and as such, it is recommended that the customer uses the DNS provided by Amazon as stated in the Client VPN documentation under the limitations and rules section of the documentation found here: https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/what-is.html
Additionally, if you want to route out the traffic from the client network interface, you can create a NAT gateway inside the same VPC as the client interface, but in a public subnet. Similar scenarios and their recommended architecture can be found here: https://aws.amazon.com/blogs/networking-and-content-delivery/using-aws-client-vpn-to-scale-your-work-from-home-capacity/
Relevant questions
AWS VPN Client - how does it open a browser for SSO ?
asked 6 months agoVPN Connection Public IP
Accepted AnswerAWS VPN Client on macOS - DNS not resolving
asked 6 months agoVPN client endpoint interfaces have public IP, how to remove?
Accepted Answerasked 2 years agoUsing client vpn with Okta, session re-authenticates multiple times throughout the day
asked 5 months agoHow to configure AWS Client VPN users to have outbound Elastic (fixed) IP when connecting to resources outside of the Client VPN associated VPC?
Accepted Answerasked 2 years agoAWS Client VPN Certs
Accepted Answerasked 3 years agocan I prevent Client VPN from setting the hostname on the client machine?
Accepted Answerasked a year agoSOS: accidentally released EIP
asked 3 years agoAWS VPN Client with fixed EIP for interfaces
asked a month ago