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
  • How to Get Assistance
  • Deployment Scenarios

Was this helpful?

  1. Self Managed Private Cloud (SMPC)

Deployment Instructions

PreviousDatabase Stored SettingsNextPrerequisites

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

These pages will guide you through the deployment of testgrinder to your private Amazon Web Services (AWS) Cloud. This guide assumes that you are familiar with AWS and Ubuntu linux.

How to Get Assistance

If you need assistance with testgrinder deployment, let us know by emailing . Alternatively, you can start a conversation with us via Intercom from the testgrinder page

Deployment Scenarios

The simplest deployment of testgrinder will have the following limitations:

  • Limitation: a tg-app server allows insecure communication on HTTP, and for requests on HTTPS it gives a security warning

    • the security warning is due to tg-app servers using a preinstalled self signed SSL certificate

    • to remove the security warning you will need to provide and install a valid SSL certificate as described in

    • once the SSL certificate is installed, it is advisable to force the tg-app server to redirect all HTTP requests to HTTPS by changing the FORCE_SSL parameter in to true.

    • follow and to resolve this limitation

  • Limitation: tg-app server hosts the database

    • tg-app servers come with preinstalled MongoDB database, which is good for evaluating testgrinder, but not advisable for production use

    • to host the database externally, see

    • if you are planning to manage tg-app servers with an Auto Scaling Group (advisable for production) you will have to switch to an external database

    • follow to resolve this limitation

  • Limitation: sole tg-app server offers low fault tolerance and may not keep up with large runs (200+ parallel scenario execution sessions)

    • to automate management of tg-app servers based on load, to automatically refresh them on failures, and to simplify tg-app upgrade process, it is advisable to manage tg-app servers with help of an Auto Scaling Group, which is described in

    • managing tg-app servers with an Auto Scaling Group requires that you have already switched to an

    • follow to resolve this limitation

Deploying testgrinder with the above limitations in place is a good start if you want to get to evaluating testgrinder quickly. For production use, we recommend eliminating all limitations listed above.

Until you install SSL certificate and force HTTP to HTTPS, testgrinder will allow HTTP requests, which are insecure. Using testgrinder with HTTP is inadvisable if it is exposed to the internet and not recommended on private networks.

Until you switch to an Auto Scaling Group for managing tg-app server, you will need to periodically monitor the health of the tg-app server manually. With the Auto Scaling Group deployed, it will automatically refresh failed tg-app servers.

Until you switch to an external database, the database will be located on the tg-app server. Make sure not to terminate the tg-app instance (for example when upgrading) prior to taking a backup of the database (see ) and moving the backup to a safe location.

Backup and Restore Database
support@testgrinder.com
Contact
Install SSL Certificate
Install SSL Certificate
Force HTTP to HTTPS
External Database
External Database
Configure Auto Scaling Group
External Database
Configure Auto Scaling Group
.env Conifguration File