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
  • Public Target Group for port 22 (SSH)
  • Public Target Group for port 80 (HTTP)
  • Public Target Group for port 443 (HTTPS)
  • Private Target Group for port 3000 (HTTP)

Was this helpful?

  1. Self Managed Private Cloud (SMPC)
  2. Deployment Instructions
  3. Configure Auto Scaling Group

Target Groups

PreviousConfigure Auto Scaling GroupNextLoad Balancers

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

Load balances (created later) will route requests to the tg-app instances in target groups.

Each target group is responsible for handling a specific port. You will need to create 3 target groups for public traffic on ports 22, 80, 443. And one for private traffic on port 3000.

You can manage target groups on the Target Groups page in AWS EC2 console at

Public Target Group for port 22 (SSH)

Follow these steps to create the public target group:

  1. Visit the Target Groups page in AWS EC2 console

  2. Click Create target group

  3. Basic Configuration:

    1. Choose target type: Instances

    2. Target group name: tg-prod-app-public-ssh

    3. Protocol: TCP

    4. Port: 22

    5. VPC: choose testgrinder VPC

  4. Health checks:

    1. Health check protocol: TCP

  5. Click Next

  6. On Register targets page:

    1. Click Create target group

Public Target Group for port 80 (HTTP)

Follow these steps to create the public target group:

  1. Visit the Target Groups page in AWS EC2 console

  2. Click Create target group

  3. Basic Configuration:

    1. Choose target type: Instances

    2. Target group name: tg-prod-app-public-http

    3. Protocol: TCP

    4. Port: 80

    5. VPC: choose testgrinder VPC

  4. Health checks:

    1. Health check protocol: HTTP

    2. Health check path: /

  5. Click Next

  6. On Register targets page:

    1. Click Create target group

Public Target Group for port 443 (HTTPS)

Follow these steps to create the public target group:

  1. Visit the Target Groups page in AWS EC2 console

  2. Click Create target group

  3. Basic Configuration:

    1. Choose target type: Instances

    2. Target group name: tg-prod-app-public-https

    3. Protocol: TCP

    4. Port: 443

    5. VPC: choose testgrinder VPC

  4. Health checks:

    1. Health check protocol: HTTPS

    2. Health check path: /

  5. Click Next

  6. On Register targets page:

    1. Click Create target group

Private Target Group for port 3000 (HTTP)

Follow these steps to create the public target group:

  1. Visit the Target Groups page in AWS EC2 console

  2. Click Create target group

  3. Basic Configuration:

    1. Choose target type: Instances

    2. Target group name: tg-prod-app-private-bot

    3. Protocol: TCP

    4. Port: 3000

    5. VPC: choose testgrinder VPC

  4. Health checks:

    1. Health check protocol: HTTP

    2. Health check path: /

  5. Click Next

  6. On Register targets page:

    1. Click Create target group

https://console.aws.amazon.com/ec2