Had to look up Amazon Workspace as a service I hadn't seen before. The way you describe it vs. what I'm reading seem a little different, but i think my first stab at a test might still apply.
Pop open a web browser and slap in ipchicken.com (or whatismyip.com, or any similar site) and take note of the IP you see.
Connect to Amazon Workspace and load up a new browser and same website.
Is the IP the same? I'm halfway expecting it to not match, which means traffic in AWS is routing out from the virtualized desktop environment. Even a local browser vs. one inside the VDE might be affected because I'd bet the system uses a VPN that re routes all traffic on the physical hardware you're using through the secured tunnel.
Best guess/stab that I can think of without getting my hands on that kind of setup though. If correct though, it's either gonna be a limitation of the VDE/VPN tunnel provided which would probably be out of Cox's hands.
That kinda issue is part of what keeps me from using always-on-vpn services since regardless of how good the connectivity speeds are on my device, it still won't go faster than what the remote/vpn side will process/allow.
Thank you. I ran the test you suggested and you are correct. Outside AWS indicates IPv6 and about a 20 character name and IN AWS is IPv4 and a 10 character name. Wish I had a choice but because this is my profession and a company requirement, no choice. there's got to be an option. I was running it fine up until about 10 days ago. Welcome any recommendations you might have.
