- Newest
- Most votes
- Most comments
Is there any update on this? It's quite frustrating to experience this multiple times a day.
If there is no intention of adding the feature to stop authentication popups, could you at least provide us with a workaround?
this issue has been fixed
This has been bugging me (and many colleagues at work) so much that I've googled it and found this post. I really sure hope there's going to be a way to disable this behaviour. 🤞🏼
I can relate and find this really annyoing. Please allow us to disable it.
I'd appreciate the Client working on background with no pop'ups, it's really annoying
Hello ,
Greetings from AWS!
I understand that you would like to stop the pop ups from occurring after signing into your Client VPN endpoint.
I do understand that this behavior can be annoying and inconvenient. Please note that there is already a Feature request raised with the Client VPN team for the same issue.
We always appreciate hearing how we can improve our services and production. I have gone ahead and +1 to the feature request to have the AWS Client run in the background rather than pop up in the foreground once connected.
Thank you for providing your valuable feedback on the service. While I am unable to comment on if/when this feature may get released, I request you to keep an eye on our What's New and Blog pages for any new feature announcements.
Have a great day ahead!
References:
[1] https://aws.amazon.com/new/ [2] https://aws.amazon.com/blogs/aws/
I don't think this has been prioritized enough. It's been more than 10 month that this is pointed out and to be honest this is such an obvious issue that does not need any feedback from customers. Hope to hear more from the AWS team.
We switched the org to AWS VPN after testing looked good, but now that the whole team is reminded of this issue daily it looks like we switched to a half baked VPN solution. An issue this obvious and customer facing (multiple new tabs opened daily!) should have been addressed years ago, so it is likely indicative of a tool or team in AWS that is not prioritized and staffed.
Considering the level of support the software is getting, our current workaround is to try something else, either spinning something up in house or moving back to our previous provider. We don't want to paper over compliance requirements with "letter of the law" levels of security, and we definitely don't want poorly supported software in our security stack.
Relevant content
- asked 7 months ago
- asked 4 years ago

This has actually been fixed in the latest version of the vpn client, thanks!