Skip to content

wings-software/AutoStoppingLab

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

27 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Getting started

Following are the requirements to get started

  1. Terraform setup and ready to run
  2. Harness Account ID
  3. AutoStopping enabled cloud connector ID
  4. Next gen API key (personal key/service token)

Each folder contains variable.tf. Modify the following variables accordingly:

variable "account_id" {
  type    = string
  default = "wOSgd9G8SuajZo1dISEF2g"
}
variable "cloud_connector_id" {
  type    = string
  default = "Lightwing_Non_Prod"
}
variable "api_key" {
  type    = string
  default = "Set the env variable TF_VAR_api_key"
}

Creating AutoStopping proxy

This is required for any sample app installation which uses proxy.

cd aws/proxy
terraform init
terraform apply

After the above commands are successful,

  • Navigate to Harness -> CloudCost -> Setup -> Load Balancer and ensure the proxy is created without errors.
  • Open AWS console and search for the proxy VM in the list of EC2 VMs. Proxy VM name will be defined in variable.tf. Default name will be proxy-demo1.

EC2 HTTP & SSH with proxy

cd aws/ec2-with-proxy
  • Open the variable.tf file and change the following values
  • proxy_id: Copy the proxy id from the Load Balancers page in Harness
  • proxy_public_ip: Copy the proxy public IP from AWS console. Search for proxy name in the AWS EC2 instance list and copy the public IP
cd aws/ec2-with-proxy
terraform init
terraform apply

RDS Connect using proxy

cd aws/rdsconnect
terraform init
terraform plan

About

Terraform templates to be used in AutoStopping Labs

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •