VPC Client VPN limit Setting
I am accessing resources on a private network using AWS Client VPN. I am accessing and using an API server or database based on EKS, but when I look at the VPN connection status to Open VPN, it looks like there is a limit of 40 bytes as shown in the picture below, and there is inconvenience in terms of speed even when communicating with the client. there is. How can we improve?
- Newest
- Most votes
- Most comments
The throughout you can realize on the AWS Client VPN connection will depend on multiple factors such as the capacity of your connection from your location, network latency between the Client VPN desktop application on your computer and the VPC endpoint. The first step would be to run tests to baseline the ideal throughout you can realize on this connection using a tool such as iperf and an EC2 instance in the VPC. This will give you an idea of what throughput to expect with the connection to the API or EKS resources. In case the results yield similar throughput of 40B/s then the you can look to improve the capacity of your connection or reduce the network latency. Else in case the results yield better throughout, you might want to take a look at the API and or EKS resources. Ideally you can expect up to 10Mbps [1.25MB/s] bandwidth limit per user connection.
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 years ago
- Accepted Answerasked 3 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you! Well, doesn't my current VPN status say that the throughput is 40B/s? I wonder if there is a way to set this to 10Mbps. Do I need to measure the reference point for the connection separately