I’ve been trying to use AWS Client VPN on my Windows ARM device with Okta SAML, but it doesn’t seem to work. From what I’ve gathered, the AWS Client VPN for Windows isn’t currently compatible with ARM-based devices. Specifically, I’m using a Surface Laptop 7 with Snapdragon® X 12-core X1E80100 @ 3.40 GHz processor, which doesn’t meet the system requirements.
Since ARM isn’t supported, I’m wondering if anyone has found a workaround or has heard anything about future support for Windows ARM devices.
Regarding when AWS Client VPN might support Windows Desktop ARM devices:
There is no official announcement or timeline for ARM support in AWS Client VPN for Windows.
AWS regularly updates its services and clients, but specific roadmap details for future releases are not publicly available.
Support for new architectures like ARM is typically driven by customer demand and technological advancements.
Unfortunately, this means there’s no solution for ARM compatibility at the moment. If anyone knows of alternative solutions or has insights on when AWS might introduce ARM support, I’d appreciate your input
We have a colleague who moved to a Windows on ARM device, which broke his access to our federated-auth Client VPN Endpoint. I raised a case with AWS Support and they told me they had an existing feature request, but no info on priority or whether it will ever happen at all. I’d encourage you to raise your own case with AWS Support to add your ‘voice’ to the feature request.
I created a temporary (intended to be temporary!) mutual/cert-auth Client VPN Endpoint to get our colleague working, but I’d love Amazon to fix the problem so that I can decommission this temporary solution.
Right now, you would need to use AWS to make another vpn config without SAML Auth. Then use openvpn to connect with the new config profile, that is what im currently doing until they release an arm supported client,
Yeah, hmm, yeah. I don’t know if I’m the only one having this issue with AWS VPN with Okta SAML. Maybe someone knows how to get technical advice from AWS.
Thanks for bringing this to our attention! I’ve shared this internally with our team. You can stay up to date with new releases, here: What’s New at AWS – Cloud Innovation & News.
I’d encourage everyone affected by this to raise your own case with AWS Support to add your ‘voice’ to the feature request, and/or raise the subject with your AWS Account Manager, if you have one.
Now I need to deploy these OpenVPN drivers… or pray AWS VPN is updated to support ARM.