LogoLogo
  • Welcome to WorkSpaces Manager
  • Overview
    • Change Log
      • Stable
      • Beta
    • Portal Requirements
      • Software Requirements
      • Hardware Requirements
    • Installation Prerequisites
      • Active Directory Service Account
      • Amazon WorkSpaces Cost Optimizer
      • CloudWatch Log Group & Eventbridge Rule
      • Port Requirements
      • AWS Service Endpoints
    • Installation Procedure
      • Subscribe to WorkSpaces Manager License Key
      • Request a License Key
      • Subscribe to WorkSpaces Manager Appliance
      • Deploy WorkSpaces Manager Appliance via CloudFormation
      • Configure WorkSpaces Manager
    • Upgrade Procedures
      • From Version 5
      • WSM Update Tool
      • Latest Version Updates
    • Alternate deployment options
      • Install manually on EC2
      • Deployment from Shared AMI
        • Security Group
        • IAM Requirements: Custom Policies
        • IAM Requirements: Role and EC2 instance profile
        • Shared AMI (Amazon Machine Image)
      • Create AMI via Packer
      • Deploy an RDS Database via Terraform
    • WorkSpaces Performance Monitor Agent
    • High Availability (HA)
    • Appendices
      • Administrator Active Directory Permissions
      • SES Configuration
      • HTTPS/TLS Encryption
      • Friendly Portal URL Address
      • GPO and values for WorkSpaces Performance Monitor Agent
      • GPO and value for Disconnection after idle time
      • IAM Policies in JSON format
      • AWS CLI v2
      • LDAP (Active Directory) Troubleshooting for WSM
      • RDS Database Options
Powered by GitBook
On this page
  1. Overview
  2. Alternate deployment options
  3. Deployment from Shared AMI

Security Group

PreviousDeployment from Shared AMINextIAM Requirements: Custom Policies

Last updated 6 months ago

A Security Group for the EC2 instance hosting WorkSpaces Manager must be created prior to deployment so it can be associated with the instance. While the roles and policies were set up in the previous section, it's important to ensure that a Security Group is also configured.

If using the from Nuvens' public site, the Security Group, Policies, Role, and EC2 Instance Profile will be created together as part of the automated deployment process.

Ensure that the AWS Security Group complies with your organization's internal governance policies. At a minimum, the Security Group should allow the following inbound access:

  • TCP/80 (HTTP)

  • TCP/443 (HTTPS)

  • TCP/1433 (MS-SQL)

  • TCP/3389 (RDP)

For outbound access, configure the Security Group to allow:

  • All traffic (all ports and protocols) to 0.0.0.0/0.

We recommend naming this Security Group according to your organization's internal naming convention. If no specific naming convention is required, you can use "SG-WorkSpacesManager" as a suggested name.

If you prefer to create the Security Group individually using Terraform, you can refer to the provided .tf file for guidance. This file contains the necessary configurations to define the Security Group and its rules.

Git Repo for Terraform
security.tf · main · Nuvens-Public / IAM-Policy-Role-SG-Terraform · GitLabGitLab
Logo