Questions tagged with Amazon WorkSpaces
Content language: English
Sort by most recent
Hello,
We have created workspaces (Windows Server 2016), and copy/paste b/n the workspace and the local computer is not working.
It is not restricted by policy. It is not working from the workspace client and from the web as well.
I tried to create a policy to allow copy/paste too, and still not working.
Can someone help here, is there some workaround, is this a known issue ?
Best Regards,
I want to invite a friend to a workspace I setup. When I got into Actions -> Invite Users for the specific workspace, it only lists the original user I had added. Is there a way to invite a new user?
Hi, Why does the WorkspacesClientDiagnosticUploader.exe open so many processes and use so much bandwidth to s3-1-w.amazonmaws.com.
Have some users where we had to uncheck the option of Automatic Diagnostic Logging in the Workspaces Settings section or just reboot their PCs to kill the amount of processes that was created by the log uploader
On some PCs I saw more than 20 Processes running and the amount of connections being made to s3-1-w.amazonmaws.com.
Want to know what triggers it happening ?
Why does it start so many different processes?
Why does it have to use so much bandwidth to upload the logs?
Hi,
I have setup AWS workspace with Windows. Now when I am using it, it just keeps freezing in between and when every time I have to disconnect and reconnect, then it comes back to life.
Any help will be really good.
I am using ubuntu bundle and trying to connect with aws workspace using aws workspace client but it shows error "the workspace you are attempting to connect is using WSP , wsp is not supported on this platform"
where is the problem . as i check aws blog for workspace , i can see that they access ubuntu using workspace client.
I'm trying to follow this guide to set up Google as Idp for AWS Workspace via SAML2.0.
https://docs.aws.amazon.com/workspaces/latest/adminguide/setting-up-saml.html
What I got working:
AWS Workspace working with AWS Managed MS AD.
Created user can log into Workspace with desktop App
For Step 1
I downloaded the Metadata from Google SAML here
Then upload to AWS IAM to create an identity providers
Step 2-3: I created a role with an inline permission
Step 4:
Step 5:
I created a custom attribute for the user to map to the Role value in AWS
Step 6:
I put the Relay State on Start URL field in Google
Step 7
Not sure what is the Idp deep link parameter name for Google so I leave it as RelayState
When I tried to do Idp-initiated flow
It open the right RelayState URL, then open the Workspace desktop app
When I clicked Continue to Sign in to Workspace it gave this error
My guess is something off with my Assertion mapping so when Workspace tries to get credentials from Google it errors out.
If anyone can help me point out where I did it wrong, it would be much appreciated. Thank you!
Hello everyone 
I am trying to do Remote SSH for quite some time and unable to make it work .
The problem :
Trying to connect to Aws Codecatalyst Dev environment Linux(remote ssh) to my local windows machine and it is in an endless loop of " Setting up SSH Host aws -exampleID".
I had tried it with my remote ubuntu aws workspace and it works flawlessly (ubuntu remote workspace to Aws codecatalyst Dev Environment) so it seems like some issue with my local machine .
Things I have tried:
When comparing the logs of failed vs successful I have noted that the remote.SSH.useLocalServer was true in my success log. So tried to add this to the settings.json but during run time it automatically changes from true to false .
Also tried clean uninstall and install couple of times (remove appData and ssh config files)
I have added an image of log of the failed Remote SSH .
Would appreciate if Remote SSH users can take a look into the logs and give their insights
I've been trying unsuccessfully to apply CIS hardening to Workspaces. There is limited documentation of what's know to break Workspaces in terms of GPOs, it doesn't appear to cover the issues we've had, and support doesn't appear to be familiar with CIS, although they are a well-established authority. Windows on Workspaces needs hardening, this falls on the CSC side of shared responsibility, but it's a struggle given what documentation I've been able to find thus far.
Does anyone have documentation on exceptions required for Workspaces when running Windows Server 2019?
i set up AD, and the work space also , but not able to make connection with aws workspace client. following are the error
I recently deployed Amazon workspaces and AWS Managed AD.
How do I hide the default AD users (Administrator, Guest, krbtgt) objects from showing up in the Workspaces Directory user search?
Thank you,
Matt M.
EC2 Session manager is not loading for linux instances when trying to access it from inside AWS workspaces station. It shows blank black screen although I'm able to connect to EC2 session manager from my personal system. Please guide.
Also, RDP connection for windows is working fine from AWS workspaces.
We recently rolled out 50 WorkSpaces to a division of the company and when things are all working properly, things work great!
However, when there are issues, we struggle so I'm here looking for some best practices.
Due to corporate policies, we only run the WorkSpaces Web Client. The native clients aren't allowed on our corporate machines...
Our most common issue is at the start of the day a user will log in to the web client, their machine will start up (I can verify this at the console) but they'll just go to a spinning "connecting" page forever. There's no apparent reason why. We try a variety of things, but I'm never sure what actually solves the issue:
* Close the browser tab, then close the browser.
* Re-open the browser, try again.
* No luck? Clear cache/cookies in the browser, try again.
* Try another browser!
* Still no luck? Stop the WorkSpaces machine via the AWS console, try again
At some point in this dance, things usually work. And I should be clear. For all users, we're in great shape over 95% of the time. There's no consistency in anyone person having more issues than any other.
What else should we be trying? There's precious little info in the console so we're sort of flying blind here.
This weekend we had an issue where NOBODY could connect. This morning still nobody could connect (35 people all over the city/country). Support, of course, wanted to zero in on one random machine and get network logs from it. We'll never know what the issue was because at 7:30 AM all of the sudden EVERYONE connected. Lol. How do you root cause analyze that? ;-)