Browse through the questions and answers listed below or filter and sort to narrow down your results.
Error with Workspace HTML5 Client
First a question, then a problem Is there an ‘internal’ portal for Workspaces? I want to keep traffic to the workspaces off the public internet. Users will access through direct connect if there is an option to connect via something in our VPC. Similar to S3 Access point in that respect. I setup a PoC workspace and it works fine with the windows client but the web client gives this error on 3 different machines on 2 different networks. All trying firefox and chrome. Same error all. The odd part is that there are only one or two google hits on this error so it must be very unusual. From my same machine I can connect to one of our Client’s Workspaces with Web client but not my own. HTML Client is enabled in workspaces and it lets me log on, just fails to present the desktop. ** An Error Occurred while connecting to your workspace. If the problem persists please contact your Workspace Administrator. ERR_SIG_CREATE_FAILED**
How to limit Workdocs access for only AWS Workspace
Thanks for any help, I know we can limit workdocs access by IP, but currently even if I'm accessing it from my AWS Workspace machine, the IP used to access workdocs is a public IP, and although the IP for each of the AWS workspace machines seems to not change, there seems to be no logic, so every time I create a new workspace I need to wait for the user to login to get their public IP to add to the allow list of my workdocs domain. Is there a way to wither make all workspace machines use public IPs from the same pool or to make them access my workdocs using their private IP so I can allow all their private IPs and be done with this instead of configure on a per machine basis? thanks for any help on this.
AWS Workspaces Latency
Hello AWS Experts! First and foremost, if you have stumbled upon my inquiry and are ready to aid me in resolving the issue, I appreciate you. My company has established an AWS Workspaces environment in the Virginia region. The Workspaces service is located in two private subnets within our Virginia VPC. When a U.S.-based user connects to the Workspaces environment, they do not deal with latency issues. Additionally, from Workspaces, the user will connect to a private EC2 instance using AWS System Manager (SSM) port forwarding. The user deals with slight latency when port forwarding/RDP into the instance. If there is a way to increase network speeds for SSM port forwarding, please inform me. Furthermore, this is where your phenomenal expertise is most needed; our users in Bulgaria experience high latency when attempting to connect to their Workspaces and even higher when trying to use SSM to connect to their EC2 instance. When a Bulgarian user uses Workspaces, their round trip time averages around 150ms. I had them test their local network bandwidth, which most averaged around 84 to 120Mbps download speeds and 140 to 160Mbps upload speeds. Additionally, they checked their "connection status..." from the following website: https://clients.amazonworkspaces.com/Health The site stated that Frankfurt provided the best connection; however, we do not want to create an entirely new VPC in the Frankfurt region for Workspaces. And have our customers question why a European IP is trying to connect to their assets. A VPN may be a possibility, but we're hoping for a better solution. I have tried the following, which non proved to improve network speeds for U.S. or Bulgarian members. - Established an Internal Load Balancer - Established VPC Endpoints - Established Global Accelerator So, how could one increase network speeds to Workspaces and SSM port forwarding? Thank you!
Connect Windows 10 WorkSpace to Amazon Linux 2 EC2 Instance
Hi, I'm experimenting with a Windows 10 WorkSpace for the first time and need some guidance on how to access an application on my Linux EC2 instance. They are both in the same account and when I created the WorkSpace I selected the default VPC which is also where my EC2 instance is. I have installed a Java application on the Workspace that needs to connect to an application on the Linux EC2 instance but so far I've failed miserably. I've added the WorkSpace IP into the Security Group associated with my EC2 instance but it just can't see it. I've tried both the public and private IP address of the EC2 instance. Any help will be greatly appreciated.
AWS Workspaces disconnects when using screenshot / snipping tool
We are using the Windows AWS Workspaces client to connect to a Linux Workspaces VM. We are finding that whenever we use the "Snipping Tool" app on the local machine (which has the Workspaces client installed) then after a few seconds the Workspaces client will say that its lost connectivity and then disconnect. It is consistently when using the tool and we are having no issues with connectivity / network reliability when we don't use the snipping tool. We are using the latest version of the Workspaces client. Does anyone know why this might be and how to fix it?
ERR_SIG_CREATE_FAILED on login to AWS workspace (reboot did not help) - it was working fine earlier today
I had no issues with this workspace for years, suddenly i couldn't login today. Rebooting did not help. Full Error: Error An error occurred while connecting to your WorkSpace. If the problem persists please contact your WorkSpaces administrator. ERR_SIG_CREATE_FAILED
Mouse Back Button Does Not Work In AWS Workspace
When using my AWS WorkSpace, my mouse's back button does not work. The button works fine outside of my AWS WorkSpace. Left click, right click, middle click, and scrolling do work. I do not have other mouse buttons, such as forward, so I cannot test those. I am running AWS WorkSpace v22.214.171.1245, and I updated a few days ago. The WorkSpace is running Windows Server 2019 Datacenter, Version 1809. The PC that I'm running AWS WorkSpace from, is running Windows 10 Home, Version 21H2. I couldn't find an solution online. Seems like this issue was reported on the AWS Developer Forums: [https://forums.aws.amazon.com/thread.jspa?threadID=151445](https://forums.aws.amazon.com/thread.jspa?threadID=151445) but I did not find the issue on re:Post. Does anyone have a solution to this?