Key Pair

testgrinder service will be discontinued on January 31, 2025

testgrinder SMPC was discontinued as of February 1, 2024

Once launched, you will need to perform configuration tasks on the tg-app instances. For that, you will be accessing the instances via ssh using a key pair that was selected at launch. Identify an existing key pair or create a new one if you don't have one available.

You can manage key pairs on the Key Pairs page in AWS EC2 console at https://console.aws.amazon.com/ec2

Later on, you may specify a key to be assigned to tg-bots when they are launched by tg-app. While this is not strictly necessary, you'll need to do it in order to ssh into the launched tg-bots for monitoring or troubleshooting. To specify the key, assign its name to the ec2_instance_key_name database stored setting. Refer to Database Stored Settings page for how to manage database stored settings.

To access a tg-app or tg-bot server, use the following commands:

The example below assumes that ssh knows where to find your key. If you need to identify the key explicitly, use the -i option for ssh

Substitute my-tg-app-or-bot with public DNS name of the server you need to access

You initially login to user ubuntu account. All testgrinder services run under testgrinder account. The second command swiches to the testgrinder user. Both ubuntu and testgrinder are authorized for sudo.

$ ssh ubuntu@my-tg-app-or-bot
$ sudo su - testgrinder