IAM Requirements: Custom Policies
Last updated
Last updated
WorkSpaces Manager requires an IAM Instance Role to be associated with the EC2 instance(s), along with custom policies to enable access to other AWS services. The necessary policies should be created and attached to both the role and the EC2 Instance Profile.
If using the Git Repo for Terraform from Nuvens' public site, the Security Group, Policies, Role, and EC2 Instance Profile will be created together as part of the automated deployment process.
Although you can name these policies based on your internal naming conventions, we recommend using the following names for better clarity and organization:
WSMCloudwatchPolicy: Grants access to AWS CloudWatch for monitoring and managing logs and metrics.
WSMCostExplorerPolicy: Provides access to AWS Cost Explorer to retrieve cost and usage reports.
WSMEC2Policy: Allows management and interaction with EC2 instances and related resources.
WSMEUCPolicy: Facilitates the management of Amazon WorkSpaces and other End-User Computing (EUC) services.
WSMPricingPolicy: Enables retrieval of pricing information from the AWS Pricing API.
WSMS3Policy: Grants access to S3 buckets used by WorkSpaces Manager, such as for storage and backups.
WSMSecretsPolicy: Allows retrieval of data from Secrets Manager for database connections.
The JSON definitions for these policies are available in our GitLab repositories and can be accessed in both Terraform and CloudFormation template formats.
For example, in Terraform, the policy might be structured as follows:
For all the JSON raw code related to the IAM policies, please refer to this appendix. This appendix contains the complete policy configurations needed for WorkSpaces Manager, including those for CloudWatch, Cost Explorer, EC2, EUC, Pricing, and S3. You can find the full code in both Terraform and CloudFormation formats in the corresponding sections.