testgrinder
Go to testgrinder
  • Overview
  • testgrinder uses
    • Testing
      • User Acceptance Testing
      • Change Testing
      • Regression Testing
      • Performance Testing
      • Stress Testing
    • Data management
      • Data verification
    • Configuration management
    • Training videos development
  • Getting Started
    • Video: Get Started with testgrinder
    • First steps
    • Example Scripts
    • Writing your first scenario
    • Scenarios
    • Run reports
  • Writing Scenarios
    • Anatomy of Maximo UI
      • Maximo login page
      • Start Center
      • Application Screen
      • Value lists
      • Advanced Search
      • Targeting fields with no labels
    • Finding the right steps
    • Step autocompletion
    • Scenarios vs Scenario Outlines
    • Snippets and Templates
      • testgrinder Templates Project
      • testgrinder Snippets Project
  • Examples
    • Interacting with electronic signature dialog
    • Automated granting of application access
    • Add a job plan
    • Add an item
    • Add an item to storeroom
  • Administration
    • Accessing Maximo behind a firewall
    • Managing User Access
    • Using Git to Back Up and Version Control testgrinder Projects
  • Self Managed Private Cloud (SMPC)
    • testgrinder SaaS vs testgrinder SMPC
    • Releases
      • Version 1.0.8
      • Version 1.0.0
    • testgrinder Architecture
    • testgrinder Configuration
      • Configuration Files
      • Database Stored Settings
    • Deployment Instructions
      • Prerequisites
      • Subscribing to testgrinder on AWS Marketplace
      • Virtual Private Cloud
      • Security Groups
      • S3 Buckets
      • IAM Roles
      • Key Pair
      • Launch tg-app
      • Finalize Configuration File .env
      • Finalizing Database Stored Settings
      • Minimal Deployment Complete
      • Install SSL Certificate
      • Force HTTP to HTTPS
      • External Database
      • Configure Auto Scaling Group
        • Target Groups
        • Load Balancers
        • Launch Template
        • Auto Scaling Group
        • Finalize Auto Scale Group Deployment
    • Test the Deployment
    • Monitoring
    • Backup and Restore Database
Powered by GitBook
On this page
  • testgrinder service will be discontinued on January 31, 2025
  • testgrinder SMPC was discontinued as of February 1, 2024
  • Launch tg-app
  • Confirm tg-app launch
  • Elastic IP Address

Was this helpful?

  1. Self Managed Private Cloud (SMPC)
  2. Deployment Instructions

Launch tg-app

PreviousKey PairNextFinalize Configuration File .env

Last updated 1 year ago

Was this helpful?

testgrinder service will be discontinued on January 31, 2025

testgrinder SMPC was discontinued as of February 1, 2024

You can manage EC2 instances on the Instances page in AWS EC2 console at

Launch tg-app

Using the tg-app AMI (see for how to find it), launch an instance of tg-app while making the following choices:

Launch the instance.

Confirm tg-app launch

Navigate to the launched instance in AWS console and copy its public IPv4 DNS address. After about a minute, navigate to the address in a browser using http protocol (e.g. http://my-tg-app-dns-name/) and you should see the testgrinder home page.

On the page you should see a message indicating that testgrinder setup is incomplete. You will resolve these later. The page should look like this:

Elastic IP Address

When tg-app launched as described above, it will be assigned a random IP address by AWS. This IP address will change if you stop and start the instance again. Since this also changes the instance's DNS name, testgrinder will stop responding to the browser requests but you will be able to connect to it via ssh to make configuration changes. To avoid IP address changes, consider assigning an Elastic IP address to the tg-app instance. For that:

  • Allocate an Elastic IP address in AWS EC2 console

  • Associate the EIP with the tg-app instance

  • Map the EIP to a domain of your choosing in your DNS

  • Update DOMAIN_WEB setting to match the domain (see Finalize Configuration File .env)

  • If you want to use HTTPS: obtain and configure an SSL certificate that matches the domain (see Install SSL Certificate)

  • Restart the tg-app server

Often browsers will automatically switch to HTTPS and this will generate a security warning because tg-app comes with a self-signed SSL certificate which browsers don't trust. See on how to install your own SSL certificate and eliminate the security warning. Your browser should give you an option to bypass the warning. Also you should be able to force your browser to communicate on HTTP without switching to HTTPS. See the browser's documentation on how to do it.

https://console.aws.amazon.com/ec2
Subscribing to testgrinder on AWS Marketplace
Configuration Files
Install SSL Certificate
testgrinder page after launching the tg-app instance with default configuration