Questions tagged with Amazon WorkSpaces
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
Amazon Workspaces Error: We can't sign in to your account
When I log into a specific AWS Workspace I get the windows error: We can't sign in to your account The fix for this is to login to the account via safe mode... which obviously isnt possible via Workspaces. Is there any way that I can fix this (other than to delete the workspace and rebuild)? This happned after I made two changes: Upgraded to more CPU/RAM Changed from AutoStop to AlwaysOn I spent most of the day setting this machine up with the software needed, and I would hate to have repeat this (especially indefinately). Any suggestions?
WorkSpaces freezing upon WorkSpaces Client screen resize
Has anyone else had issues with WorkSpaces freezing upon dragging to resize the client? I have had this at multiple clients with multiple unrelated AWS environments. Doesn't matter what version of the Amazon WorkSpaces Client software you use. Basically, what happens is: 1. You log on, let's say with the WorkSpaces Client for Windows. Everything is fine. 2. You drag the edge of the WorkSpaces Client to make the window of the application larger, OR let's say you go to Full Screen mode. 3. The client simply freezes. The desktop does not immediately resize, OR the screen goes black. 4. It stays frozen for about 5 mins, then magically the resize "catches up" and everything settles down and goes back to normal. 5. It also happens if you use a zero client, but the WorkSpace was previously running in the WorkSpaces Client software (and sized for the client it was running on) and thus needs to resize again to fit the zero client. Or vice versa. Hope I'm explaining this properly. It does not happen on all WorkSpaces at all times. There does not even need to be any applications open. However, when it does start to happen on a particular WorkSpace, it is very repeatable on that WorkSpace for a considerable amount of time (like all day, or occasionally all week). Multiple reboots and it still recurs. Then on another day it might not do it at all, and resizes work fine on that same WorkSpace. I can't think of any common denominator that these WorkSpaces have. Maybe ScreenConnect? Incidentally, if you view the desktop through ScreenConnect while this is happening, it remains “stuck” - you click on things, nothing happens - you can't really interact with it…but you *can* connect to it. Interestingly, it does not disconnect the session. And if you send a reboot command it immediately restarts the WorkSpace, so it is still "alive" so to speak. I'm curious to hear if anyone else has run into this. Thanks!
Can't create Graphics Bundle Workspace. An Error Has Occurred
Hello, I'm trying to create a Graphics.g4dn in São Paulo region, but it fails imediately when I click on launch: > An Error Has Occurred > **It only happens with Graphics.g4dn bundle, any other bundle works perfectly.** We've been using Workspaces for quite a long time and this is the first time I get a problem like this.
White screen accessing workspace
I can't access my workspace since yesterday. After login, it just keeps the screen white and disconnect, maybe it's because I turned on the firewall inside the workspace, I don't know. The log: "Error while making a request to : https://d1cbg795sa4g1u.cloudfront.net/prod/iad/d-906745bae9/en_US/wsassets.json. Message: HttpClient - 4xx Network error Exception while getting file headers from URI: https://d1cbg795sa4g1u.cloudfront.net/prod/iad/d-906745bae9/en_US/wsassets.json. Exception: WorkSpacesClient.Common.Infrastructure.ExceptionHandler.WorkspacesClientNetworkException: HttpClient - 4xx Network error ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (Forbidden)." I hope someone can help me with it, Thanks.
aws workspaces linux user contains dangling character
hi from Spain! Iv'e configured a Linux workspace and, when prompted for a username I wrote "qa", but the actual username created was "CORP\qa". The problem is that the added backslash can be annoying and make some scripts to fail. For instance, configuring a Github Actions self-hosted runner as a service, fails because the service unit created uses a wrong username "CORPqa" Is there any way of removing the "CORP" and let the username just be "qa"? Thanks!
WorkDocs Drive hangs during setup.
When setting up WorkDocs Drive in a Workspace, after typing in the site name, it says "Processing..." and hangs. The log file indicates an authentication error. This is before it asks you to logon. It appears to be an issue with the workspaces (it happens on all workspaces in this AWS account that I have tried). I tried it from a workspace in a different AWS account and it worked fine.
Lack of "workspaces:RegisterWorkspaceDirectory" permission when registering a Workspaces Directory
Hi, I am using Terraform to provision a new Amazon Workspaces. I have an AD Connector created and linked to our internal domain. The next step is to create a Workspaces Directory. Part of creation is to link the Directory to the AD Connector using the Terraform "aws_workspaces_directory" resource. However, I've got the following error when running the Terraform code even though the user below is granted AmazonWorkSpacesAdmin & AWSDirectoryServiceFullAccess permission policies. ` Error: error registering WorkSpaces Directory (d-xxxxxxxxxx): AccessDeniedException: User: arn:aws:iam::xxxxx:user/xxxx is not authorized to perform: workspaces:RegisterWorkspaceDirectory on resource: arn:aws:workspaces:us-east-1:xxxxx:directory/d-xxxxxxx because no identity-based policy allows the workspaces:RegisterWorkspaceDirectory action` Is there anybody who knows what permission policy is needed to grant the "workspaces:RegisterWorkspaceDirectory" action? If I read the error correctly, the user is lack of permission to register workspace directory with the AD connector? If so, how do I check who has such permission on the AD Connector? Thank you.
Server Error During Password Recovery via Workspaces Windows Client
Hello, I'm trying to recover a password for a workspace I created previously. I'm using Amazon Workspaces Windows Desktop client and the password recovery form falls into a loop of the "Server Error There was an error with your request. Please try again later." message. I'm pretty sure that my username is correct. The username contains uppercase letters. I also tried typing username with lowercase letters but it did not work. Restarting the workspace through the AWS web console did not resolve the issue. Please kindly assist me. Thanks, Ismet
Disconnected when Logged in from another location
Hi, When using Workspaces, we will sometimes have one workspace setup that multiple users need to access. When a single user is logged in and then another user logs in using the same credentials, the first user gets logged out and the system says "You have been disconnected because you logged in from another location". This works as intended. My question is, is there any way to have the system prompt either of the users that multiple logins are happening? Currently the system immediately kicks out the first user and the 2nd user (using the same credentials) also has no idea they are kicking the 1st user out. A simple prompt would be very helpful. Is there any way to have the system prompt that multiple users are logging each other out? TIA.