Skip to content

Launch automation

Create IAM role
  • Login into ElasticDev here

  • Here is a walk-through video

  • Here is the actual stack1

  • Click Add Project
    • It will list git repositories in your account
    • Click launch-ed
    • It will prompt you to enter a branch. 
      iam
    • Provide a unique name for the project 
      iam-101
    • Click Add Project
    • The automation will begin.
    • Please wait approximately 5 mins.
    • Click the name of the project (iam-101)
      • You will see the jobs
      • Click one of the job(s)
      • Click output tab
Create VPC
  • Login into ElasticDev here

  • Here is a walk-through video

  • Here is the actual stack2

  • Click Add Project

    • It will list git repositories in your account
    • Click launch-ed
    • It will prompt you to enter a branch. 
      vpc
    • Provide a unique name for the project 
      vpc-101
    • Click Add Project
    • The automation will begin.
    • Please verify the VPC jobs finished before proceeding to automations below.

  • Notes

    • you must delete vpc below before deleting iam. wait for the vpc projects to disappear before deleting the iam.
Select and Launch other automations
  • The branches refer to the sample automation that will build on top of the IAM and VPC just created.
  • Featured3
    • rds – rds placed in the AWS VPC
    • eks – eks placed in the AWS VPC
    • kafka – kafka cluster placed in the AWS VPC
    • mongodb – mongodb replica set placed in the AWS VPC

  • Here is a walk-through video

  • Notes

    • the automation below will cost money in the cloud
    • delete project below to destroy the cloud resources to minimize cost
    • you must delete all these projects below before deleting vpc and iam. wait for the projects to disappear before deleting the vpc and iam.

  1. IAM role is needed for all subsequent automations. ↩

  2. VPC is needed for automations that will be inserted into the network. The VPC consist of NAT gateway. ↩

  3. The featured automations use selectors to perform variable substitution. For example, 

    vpc_name: selector:::vpc_info::name
    will insert use the selector vpc_info (defined and not shown) and insert name of the selector for the variable vpc_name. This will be shown in the elasticdev/elasticdev.yml file in the branches. For example, for EKS, you can find substitution by:

    cd launch-ed
git checkout eks
cat elasticdev/elasticdev.yml
     ↩