By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Workspaces pooled - some issues getting started

0

The first issue is that can't find a correct role type to apply to pooled workspaces. None of my existing workspace or appstream roles show up in the drop down so this must be a new type. What should the trust relationbship look like if not this? I tried workspacespool workspacespools and a few others.

        "Principal": {
            "Service": "workspaces.amazonaws.com"
        },

Second issue is when trying to create the first pool for the SAML2 workspace directory. Get this error every time Failed to create workspace. One or more parameter values are not valid. The Subnet: subnet-abc123 provided is not a public Subnet. Please provide a valid public Subnet to enable default Internet access.

Of course I didn't provide public subnets when I created the directory and there was no option when creating the directory to choose if the workspaces should have Internet access or not as it did with the old style Workspaces. A bug or a requirement to use public subnets?

Topics
End User Computing
Tags
Amazon WorkSpaces
Language
English
rePost-User-1579460
asked a month ago256 views
3 Answers
0

The role you need is workspaces_DefaultRole, which is automatically created when using WorkSpaces Quick Setup or when launching a WorkSpace using the AWS Management Console. You might need to attach the AmazonWorkSpacesPoolServiceAccess managed policy to this role. You encountered an error stating that the provided subnet is not public when trying to create a pool for the SAML2 workspace directory. This is not a bug but a requirement for WorkSpaces to have default Internet access. The issue might be due to a VPN issue or a firewall blocking necessary ports.

profile picture
EXPERT
Giovanni Lauria
answered a month ago
0

The Pooled directory setup doesn't accept workspaces_DefaultRole or the arn of this role. The role exists.

I'm not following on the web access problem. The Directory setup page allowed me to choose private subnets and these subnets have access and routes to a NAT gateway in a public subnet. It wouldn't make sense to put workspaces in public subnets with an internet gateway and public IP's for each workspace.

rePost-User-1579460
answered a month ago
0

I spoke to AWS support, there's an inconsistency in the GUI when you configure your pooled directory where InternetAccess is turned on by default. (and no GUI option to turn off) If you want to turn it off and use private subnets:

aws workspaces modify-workspace-creation-properties --resource-id wsd-XXXXXXXXX --workspace-creation-properties EnableInternetAccess=false

rePost-User-1579460
answered a month ago

Relevant content