Finalize Auto Scale Group Deployment
testgrinder service will be discontinued on January 31, 2025
testgrinder SMPC was discontinued as of February 1, 2024
Update tg_app_url Database Setting
Once you switch to managing tg-app instances by an Auto Scaling Group you will need to change the tg_app_url database setting to make it point to the internal load balancer DNS name rather than private tg-app instance address. See Finalize Database Stored Settings
Once the internal load balancer is created, you may get its DNS name from its Details in the EC2 console. The DNS name should look similar to this:
From which you can construct the value for the tg_app_url database setting by appending :3000/ra to it. In the end it should look similar to this:
Modifications to Launch Template
At some point you will find that you need to make changes to the Launch Template. For example, to update the tg-app AMI ID during an upgrade. AWS does not allow editing launch templates. Rather, it will offer you to create a new version of the template. When creating a new version of the Launch Template it is important to make sure that you are making a new version based on the Latest version. If you followed this guide when setting up the Auto Scaling group, no changes need to do there as it is configured to work with the Latest version of the launch template.
Refreshing tg-app Instances
Auto Scaling group will not automatically refresh tg-app instances when the launch template changes. You will need to kick it off yourself by going to the ASG in the EC2 console and initiating the instance refresh.
Last updated