Security Group
Last updated
Last updated
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 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.
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.
