Static private IP addresses for AWS Client VPN connections

Typically, we see customers use a 3rd-party/partner solution to assign private IP addresses when AWS Client VPN is not a match for customer requirements. I don't understand what you're trying to do. Do you want to be able to restrict individual users to only be able to access specific resources? I suggest you look at dynamic solutions that do not rely on client IP address.

Hi Directory Service Integration: Integrate AWS Client VPN with AWS Directory Service (such as AWS Managed Microsoft AD or AD Connector). This allows you to authenticate users based on their Active Directory credentials.

Use DHCP Option Sets: With AWS Client VPN, you can configure DHCP option sets to assign static IP addresses to users based on their Active Directory usernames. Each user can be associated with a specific IP address through DHCP reservations.

Here you can refer https://repost.aws/knowledge-center/client-vpn-static-ip-address

Hello strel0k!

One currently cannot assign a static IP on the AWS Client VPN side "natively", I am afraid. Happy to discuss your specific use-case (some form of restricting access to 'intra-AWS' resources, I would assume?) - as you are probably aware, we are offering either Security Group-based (whole Client VPN endpoint-scope) or [recommended in this scenario] a user-group based filtering (user/group level, configured within authorization rules).

If using the former, one in principle can create multiple/several AWS Client VPN endpoints and assign different CIDRs (and Security Groups), but this realistically won't be at user level granularity.