Security Groups
testgrinder service will be discontinued on January 31, 2025
testgrinder SMPC was discontinued as of February 1, 2024
You will need to create two security groups - one for tg-app and one for tg-bot instances
You can manage Security Groups on the Security Groups page of the AWS EC2 Console
tg-app Security Group
Create a security group with name tg-app for the VPC with the following access rules:
Egress
*
0.0.0.0/0
*
SSH
Ingress
TCP
YOUR_IP/32
22
HTTP
Ingress
TCP
0.0.0.0/0
80
HTTPS
Ingress
TCP
0.0.0.0/0
443
tg-bot API
Ingress
TCP
VPC_CIDR
3000
Note: For SSH rule choose the most appropriate CIDR in your circumstance. It could be as restrictive as the IP of the machine from which you will be accessing tg-app server or as permissive as the world (0.0.0.0/0).
Note: tg-bot API (TCP port 3000) should be only accessible by tg-bots, which will be launched by tg-app in the same VPC. Hence, CIDR of the VPC is a good choice for the source there.
tg-bot Security Group
Create a security group tg-bot for the VPC with the following access rules:
Egress
*
0.0.0.0/0
*
VNC
Ingress
TCP
VPC_CIDR
5900
Note: VPC rule is to enable tg-app to stream screencasts of running scenarios
Last updated