End of support notice: On March 31, 2027, AWS will end support for Amazon WorkSpaces Thin Client. After March 31, 2027, you will no longer be able to access the WorkSpaces Thin Client console or WorkSpaces Thin Client resources. For more information, see [Amazon WorkSpaces Thin Client end of support](https://docs.aws.amazon.com/workspaces-thin-client/latest/ag/workspacesthinclient-end-of-support.html). # Identity and access management for Amazon WorkSpaces Thin Client AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use WorkSpaces Thin Client resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [Audience](#security_iam_audience) + [Authenticating with identities](#security_iam_authentication) + [Managing access using policies](#security_iam_access-manage) + [How Amazon WorkSpaces Thin Client works with IAM](security_iam_service-with-iam.md) + [Identity-based policy examples for Amazon WorkSpaces Thin Client](security_iam_id-based-policy-examples.md) + [AWS managed policies for Amazon WorkSpaces Thin Client](security-iam-awsmanpol.md) + [Troubleshooting Amazon WorkSpaces Thin Client identity and access](security_iam_troubleshoot.md) ## Audience How you use AWS Identity and Access Management (IAM) differs based on your role: + **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting Amazon WorkSpaces Thin Client identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How Amazon WorkSpaces Thin Client works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [Identity-based policy examples for Amazon WorkSpaces Thin Client](security_iam_id-based-policy-examples.md)) ## Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role. You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*. For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*. ### AWS account root user When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. ### Federated identity As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials. A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials. For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*. ### IAM users and groups An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*. An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*. ### IAM roles An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*. Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**. By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation. ### Identity-based policies Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*. ### Resource-based policies Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy. ### Other policy types AWS supports additional policy types that can set the maximum permissions granted by more common policy types: + **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*. + **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*. + **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*. + **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*. ### Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*. # How Amazon WorkSpaces Thin Client works with IAM Before you use IAM to manage access to WorkSpaces Thin Client, learn what IAM features are available to use with WorkSpaces Thin Client. **IAM features you can use with Amazon WorkSpaces Thin Client** | IAM feature | WorkSpaces Thin Client support | | --- | --- | | [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes | | [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No | | [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes | | [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes | | [Policy condition keys](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes | | [ACLs](#security_iam_service-with-iam-acls) | No | | [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | Yes | | [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes | | [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes | | [Service roles](#security_iam_service-with-iam-roles-service) | No | | [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | No | To get a high-level view of how WorkSpaces Thin Client and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Identity-based policies for WorkSpaces Thin Client **Supports identity-based policies:** Yes Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*. ### Identity-based policy examples for WorkSpaces Thin Client To view examples of WorkSpaces Thin Client identity-based policies, see [Identity-based policy examples for Amazon WorkSpaces Thin Client](security_iam_id-based-policy-examples.md). ## Resource-based policies within WorkSpaces Thin Client **Supports resource-based policies:** No Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Policy actions for WorkSpaces Thin Client **Supports policy actions:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation. To see a list of WorkSpaces Thin Client actions, see [Actions Defined by Amazon WorkSpaces Thin Client](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonworkspacesthinclient.html#amazonworkspacesthinclient-actions-as-permissions) in the *Service Authorization Reference*. Policy actions in WorkSpaces Thin Client use the following prefix before the action: ``` thinclient ``` To specify multiple actions in a single statement, separate them with commas, as shown in the following example: ``` "Action": [ "thinclient:action1", "thinclient:action2" ] ``` To view examples of WorkSpaces Thin Client identity-based policies, see [Identity-based policy examples for Amazon WorkSpaces Thin Client](security_iam_id-based-policy-examples.md). ## Policy resources for WorkSpaces Thin Client **Supports policy resources:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources. ``` "Resource": "*" ``` To see a list of WorkSpaces Thin Client resource types and their ARNs, see [Resources Defined by Amazon WorkSpaces Thin Client](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonworkspacesthinclient.html#amazonworkspacesthinclient-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions you can specify the ARN of each resource, see [Actions Defined by Amazon WorkSpaces Thin Client](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonworkspacesthinclient.html#amazonworkspacesthinclient-actions-as-permissions). To view examples of WorkSpaces Thin Client identity-based policies, see [Identity-based policy examples for Amazon WorkSpaces Thin Client](security_iam_id-based-policy-examples.md). ## Policy condition keys for WorkSpaces Thin Client **Supports service-specific policy condition keys:** Yes Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. To see a list of WorkSpaces Thin Client condition keys, see [Condition Keys for Amazon WorkSpaces Thin Client](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonworkspacesthinclient.html#amazonworkspacesthinclient-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions Defined by Amazon WorkSpaces Thin Client](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonworkspacesthinclient.html#amazonworkspacesthinclient-actions-as-permissions). To view examples of WorkSpaces Thin Client identity-based policies, see [Identity-based policy examples for Amazon WorkSpaces Thin Client](security_iam_id-based-policy-examples.md). ## ACLs in WorkSpaces Thin Client **Supports ACLs:** No Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. ## ABAC with WorkSpaces Thin Client **Supports ABAC (tags in policies):** Yes Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys. If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**. For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*. ## Using temporary credentials with WorkSpaces Thin Client **Supports temporary credentials:** Yes Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Cross-service principal permissions for WorkSpaces Thin Client **Supports forward access sessions (FAS):** Yes Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). ## Service roles for WorkSpaces Thin Client **Supports service roles:** No A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*. **Warning** Changing the permissions for a service role might disrupt WorkSpaces Thin Client functionality. Edit service roles only when WorkSpaces Thin Client provides guidance to do so. ## Service-linked roles for WorkSpaces Thin Client **Supports service-linked roles:** No A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles. For details about creating or managing service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). Find a service in the table that includes a `Yes` in the **Service-linked role** column. Choose the **Yes** link to view the service-linked role documentation for that service. # Identity-based policy examples for Amazon WorkSpaces Thin Client By default, users and roles don't have permission to create or modify WorkSpaces Thin Client resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*. For details about actions and resource types defined by WorkSpaces Thin Client, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for Amazon WorkSpaces Thin Client](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonworkspacesthinclient.html) in the *Service Authorization Reference*. **Topics** + [Policy best practices](#security_iam_service-with-iam-policy-best-practices) + [Using the WorkSpaces Thin Client console](#security_iam_id-based-policy-examples-console) + [Grant read-only access to WorkSpaces Thin Client](#security_iam_id-based-policy-examples-grant-read-only-access) + [Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions) + [Grant full access to WorkSpaces Thin Client](#security_iam_id-based-policy-examples-grant-full-access) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete WorkSpaces Thin Client resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: + **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. + **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. + **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. + **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*. + **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*. ## Using the WorkSpaces Thin Client console To access the Amazon WorkSpaces Thin Client console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the WorkSpaces Thin Client resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy. You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform. ## Grant read-only access to WorkSpaces Thin Client This example shows how you can create a policy that allows IAM users to view a WorkSpaces Thin Client configuration, but not make changes. This policy includes permissions to complete this action on the console or program by using the AWS CLI or AWS API. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "thinclient:GetEnvironment", "thinclient:ListEnvironments", "thinclient:GetDevice", "thinclient:ListDevices", "thinclient:ListDeviceSessions", "thinclient:GetSoftwareSet", "thinclient:ListSoftwareSets", "thinclient:ListTagsForResource" ], "Resource": "arn:aws:thinclient:*:*:*" }, { "Effect": "Allow", "Action": ["workspaces:DescribeWorkspaceDirectories"], "Resource": "arn:aws:workspaces:*:*:directory/*" }, { "Effect": "Allow", "Action": ["workspaces-web:GetPortal"], "Resource": ["arn:aws:workspaces-web:*:*:portal/*"] }, { "Effect": "Allow", "Action": ["workspaces-web:GetUserSettings"], "Resource": ["arn:aws:workspaces-web:*:*:userSettings/*"] }, { "Effect": "Allow", "Action": ["appstream:DescribeStacks"], "Resource": ["arn:aws:appstream:*:*:stack/*"] } ] } ``` ------ ## Allow users to view their own permissions This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam::*:user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "*" } ] } ``` ## Grant full access to WorkSpaces Thin Client This example shows how you can create a policy that grants full access to WorkSpaces Thin Client IAM users. This policy includes permissions to complete all WorkSpaces Thin Client actions on the console or program by using the AWS CLI or AWS API. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": ["thinclient:*"], "Resource": "arn:aws:thinclient:*:*:*" }, { "Effect": "Allow", "Action": ["workspaces:DescribeWorkspaceDirectories"], "Resource": "arn:aws:workspaces:*:*:directory/*" }, { "Effect": "Allow", "Action": ["workspaces-web:GetPortal"], "Resource": ["arn:aws:workspaces-web:*:*:portal/*"] }, { "Effect": "Allow", "Action": ["workspaces-web:GetUserSettings"], "Resource": ["arn:aws:workspaces-web:*:*:userSettings/*"] }, { "Effect": "Allow", "Action": ["appstream:DescribeStacks"], "Resource": ["arn:aws:appstream:*:*:stack/*"] } ] } ``` ------ # AWS managed policies for Amazon WorkSpaces Thin Client An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles. Keep in mind that AWS managed policies might not grant least-privilege permissions for your specific use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases. You cannot change the permissions defined in AWS managed policies. If AWS updates the permissions defined in an AWS managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*. ## AWS managed policy: AmazonWorkSpacesThinClientReadOnlyAccess You can attach the `AmazonWorkSpacesThinClientReadOnlyAccess` policy to your IAM identities. This policy grants full access permissions to the WorkSpaces Thin Client service and its dependencies. For more information on this managed policy, see [ AmazonWorkSpacesThinClientReadOnlyAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonWorkSpacesThinClientReadOnlyAccess.html) in the *AWS Managed Policy Reference guide*. **Permissions details** This policy includes the following permissions. + `thinclient` (WorkSpaces Thin Client) – Allows read-only access to all WorkSpaces Thin Client actions. + `workspaces` (WorkSpaces) – Allows permissions to describe WorkSpaces directories and connection aliases. This is used to check that your WorkSpaces resources are compatible with WorkSpaces Thin Client. It is also used to show these resources in the WorkSpaces Thin Client AWS console. + `workspaces-web` (WorkSpaces Secure Browser) – Allows permissions to describe WorkSpaces Secure Browser portals and user settings. This is used to check that your WorkSpaces Secure Browser resources are compatible with WorkSpaces Thin Client. It is also used to show these resources in the WorkSpaces Thin Client AWS console. + `appstream` (WorkSpaces Applications) – Allows permissions to describe WorkSpaces Applications stacks. This is used to check that your WorkSpaces Applications resources are compatible with WorkSpaces Thin Client. It is also used to show these resources in the WorkSpaces Thin Client AWS console. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "AllowThinClientReadAccess", "Effect": "Allow", "Action": [ "thinclient:GetDevice", "thinclient:GetDeviceDetails", "thinclient:GetEnvironment", "thinclient:GetSoftwareSet", "thinclient:ListDevices", "thinclient:ListDeviceSessions", "thinclient:ListEnvironments", "thinclient:ListSoftwareSets", "thinclient:ListTagsForResource" ], "Resource": "*" }, { "Sid": "AllowWorkSpacesAccess", "Effect": "Allow", "Action": [ "workspaces:DescribeConnectionAliases", "workspaces:DescribeWorkspaceDirectories" ], "Resource": "*" }, { "Sid": "AllowWorkSpacesSecureBrowserAccess", "Effect": "Allow", "Action": [ "workspaces-web:GetPortal", "workspaces-web:GetUserSettings", "workspaces-web:ListPortals" ], "Resource": "*" }, { "Sid": "AllowAppStreamAccess", "Effect": "Allow", "Action": [ "appstream:DescribeStacks" ], "Resource": "*" } ] } ``` ------ ## AWS managed policy: AmazonWorkSpacesThinClientFullAccess You can attach the `AmazonWorkSpacesThinClientFullAccess` policy to your IAM identities. This policy grants full access permissions to the WorkSpaces Thin Client service and its dependencies. For more information on this managed policy, see [ AmazonWorkSpacesThinClientFullAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonWorkSpacesThinClientFullAccess.html) in the *AWS Managed Policy Reference Guide*. **Permissions details** This policy includes the following permissions: + `thinclient` (WorkSpaces Thin Client) – Allows full access to all WorkSpaces Thin Client actions. + `workspaces` (WorkSpaces) – Allows permissions to describe WorkSpaces directories and connection aliases. This is used to check that your WorkSpaces resources are compatible with WorkSpaces Thin Client. It is also used to show these resources in the WorkSpaces Thin Client AWS console. + `workspaces-web` (WorkSpaces Secure Browser) – Allows permissions to describe WorkSpaces Secure Browser portals and user settings. This is used to check that your WorkSpaces Secure Browser resources are compatible with WorkSpaces Thin Client. It is also used to show these resources in the WorkSpaces Thin Client AWS console. + `appstream` (WorkSpaces Applications) – Allows permissions to describe WorkSpaces Applications stacks. This is used to check that your WorkSpaces Applications resources are compatible with WorkSpaces Thin Client. It is also used to show these resources in the WorkSpaces Thin Client AWS console. + `iam` – Allows WorkSpaces Thin Client to create a service-linked role in your account. This role enables WorkSpaces Thin Client to publish metrics to CloudWatch on your behalf. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "AllowThinClientFullAccess", "Effect": "Allow", "Action": [ "thinclient:*" ], "Resource": "*" }, { "Sid": "AllowWorkSpacesAccess", "Effect": "Allow", "Action": [ "workspaces:DescribeConnectionAliases", "workspaces:DescribeWorkspaceDirectories" ], "Resource": "*" }, { "Sid": "AllowWorkSpacesSecureBrowserAccess", "Effect": "Allow", "Action": [ "workspaces-web:GetPortal", "workspaces-web:GetUserSettings", "workspaces-web:ListPortals" ], "Resource": "*" }, { "Sid": "AllowAppStreamAccess", "Effect": "Allow", "Action": [ "appstream:DescribeStacks" ], "Resource": "*" }, { "Sid": "AllowCreateServiceLinkedRole", "Effect": "Allow", "Action": "iam:CreateServiceLinkedRole", "Resource": "arn:aws:iam::*:role/aws-service-role/monitoring.thinclient.amazonaws.com/AWSServiceRoleForAmazonWorkSpacesThinClientMonitoring", "Condition": { "StringEquals": { "iam:AWSServiceName": "monitoring.thinclient.amazonaws.com" } } } ] } ``` ------ ## WorkSpaces Thin Client updates to AWS managed policies | Change | Description | Date | | --- | --- | --- | | AmazonWorkSpacesThinClientMonitoringServiceRolePolicy – Removed policy | WorkSpaces Thin Client removed the AmazonWorkSpacesThinClientMonitoringServiceRolePolicy section. | November 12, 2025 | | [AmazonWorkSpacesThinClientFullAccess](#security-iam-awsmanpol-AmazonWorkSpacesThinClientFullAccess) – Updated policy AmazonWorkSpacesThinClientMonitoringServiceRolePolicy – New policy | WorkSpaces Thin Client updated the policy to include service linked roles. | August 26th 2025 | | [AmazonWorkSpacesThinClientReadOnlyAccess](#security-iam-awsmanpol-AmazonWorkSpacesThinClientReadOnlyAccess) – Updated policy | WorkSpaces Thin Client updated the policy to include limited read permissions for device details and WorkSpaces connection aliases. | January 9th 2025 | | [AmazonWorkSpacesThinClientFullAccess](#security-iam-awsmanpol-AmazonWorkSpacesThinClientFullAccess) – Updated policy | WorkSpaces Thin Client updated the policy to include limited read permissions for WorkSpaces connection aliases. | January 9th 2025 | | [AmazonWorkSpacesThinClientReadOnlyAccess](#security-iam-awsmanpol-AmazonWorkSpacesThinClientReadOnlyAccess) – Updated policy | WorkSpaces Thin Client updated the policy to include limited read permissions for WorkSpaces Applications, WorkSpaces Web and WorkSpaces. | August 9th 2024 | | [AmazonWorkSpacesThinClientFullAccess](#security-iam-awsmanpol-AmazonWorkSpacesThinClientFullAccess) – New policy | Provides full access to Amazon WorkSpaces Thin Client as well as limited access to required related services. | August 9th 2024 | | [AmazonWorkSpacesThinClientReadOnlyAccess](#security-iam-awsmanpol-AmazonWorkSpacesThinClientReadOnlyAccess) – New policy | Provides read-only access to Amazon WorkSpaces Thin Client and its dependencies. | July 19th 2024 | | WorkSpaces Thin Client started tracking changes | WorkSpaces Thin Client started tracking changes for its AWS managed policies. | July 19th 2024 | # Troubleshooting Amazon WorkSpaces Thin Client identity and access Use the following information to help you diagnose and fix common issues that you might encounter when working with WorkSpaces Thin Client and IAM. **Topics** + [I am not authorized to perform an action in WorkSpaces Thin Client](#security_iam_troubleshoot-no-permissions) + [I want to view my access keys](#security_iam_troubleshoot-access-keys) + [I'm an administrator and want to allow others to access WorkSpaces Thin Client](#security_iam_troubleshoot-admin-delegate) + [I want to allow people outside of my AWS account to access my WorkSpaces Thin Client resources](#security_iam_troubleshoot-cross-account-access) ## I am not authorized to perform an action in WorkSpaces Thin Client If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password. The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `my-thin-client-device` resource but does not have the fictional `thinclient:ListDevices` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: thinclient:ListDevices on resource: my-thin-client-device ``` In this case, Mateo asks his administrator to update his policies to allow him to access the `my-thin-client-device` resource by using the `thinclient:ListDevices` action. ## I want to view my access keys After you create your IAM user access keys, you can view your access key ID at any time. However, you can't view your secret access key again. If you lose your secret key, you must create a new access key pair. Access keys consist of two parts: an access key ID (for example, `AKIAIOSFODNN7EXAMPLE`) and a secret access key (for example, `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`). Like a user name and password, you must use both the access key ID and secret access key together to authenticate your requests. Manage your access keys as securely as you do your user name and password. **Important** Do not provide your access keys to a third party, even to help [find your canonical user ID](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html#FindCanonicalId). By doing this, you might give someone permanent access to your AWS account. When you create an access key pair, you are prompted to save the access key ID and secret access key in a secure location. The secret access key is available only at the time you create it. If you lose your secret access key, you must add new access keys to your IAM user. You can have a maximum of two access keys. If you already have two, you must delete one key pair before creating a new one. To view instructions, see [Managing access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey) in the *IAM User Guide*. ## I'm an administrator and want to allow others to access WorkSpaces Thin Client To allow others to access WorkSpaces Thin Client, you must grant permission to the people or applications that need access. If you are using AWS IAM Identity Center to manage people and applications, you assign permission sets to users or groups to define their level of access. Permission sets automatically create and assign IAM policies to IAM roles that are associated with the person or application. For more information, see [Permission sets](https://docs.aws.amazon.com/singlesignon/latest/userguide/permissionsetsconcept.html) in the *AWS IAM Identity Center User Guide*. If you are not using IAM Identity Center, you must create IAM entities (users or roles) for the people or applications that need access. You must then attach a policy to the entity that grants them the correct permissions in WorkSpaces Thin Client. After the permissions are granted, provide the credentials to the user or application developer. They will use those credentials to access AWS. To learn more about creating IAM users, groups, policies, and permissions, see [IAM Identities](https://docs.aws.amazon.com/IAM/latest/UserGuide/id.html) and [Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. For more information, see [Grant full access to WorkSpaces Thin Client](security_iam_id-based-policy-examples.md#security_iam_id-based-policy-examples-grant-full-access). ## I want to allow people outside of my AWS account to access my WorkSpaces Thin Client resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: + To learn whether WorkSpaces Thin Client supports these features, see [How Amazon WorkSpaces Thin Client works with IAM](security_iam_service-with-iam.md). + To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*. + To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*. + To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*. + To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.