AWS EKS EC2 ASG

AWS-EKS-ASG PLATFORM SETUP

Before you get started with the AWS EKS EC2 Workflow, you need to check out our setup Workflow to Create your Account on CTO.ai and install CLI.

Installation

The AWS EKS EC2 ASG Auto scaling Workflow is open source on GitHub, and you can install it by cloning the repository.

git clone [email protected]:workflows-sh/aws-eks-ec2-asg.git

cd aws-eks-ec2-asg

When you’re done cloning it, follow the instructions below to build and deploy your Workflow.

Create Secret from Settings

Back in your CTO.ai dashboard, create your secrets by selecting Settings and Secrets.

Secrets are encrypted environment variables that CTO.ai utilizes within your workflow to build and run your application and deployments.

You will create four secrets:

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_ACCOUNT_NUMBER
GITHUB_TOKEN
To create your AWS SECRET KEY AND ACCESS KEY . Log into your AWS Account, select the Identity and Access Management (IAM) dashboard, create a new user, copy the Access Key ID and Secret access key and paste it in your secret dashboard on CTO.ai.

Your AWS ACCOUNT NUMBER can be gotten from your User ID on the top right corner in your AWS Console.

Generate GitHub Token

Generate your GITHUB_TOKEN from Github by going to Settings → Developer settings → Personal access tokens → Generate new token on your Github profile.

Back in your CTO.ai Secrets dashboard create your secret key/value pairs.

EKS EC2 ASG DEMO

Our EKS-EC2-ASG stack is a PaaS workflow with GitOps / ChatOps features that supports EKS on EC2, Aurora, SQS, Redis, and Autoscaling via CDK.

On our GitHub page, clone the workflow.sh repository. The workflow.sh repo contains the AWS EKS EC2 ASG and Auto scaling group stack that acts as your infrastructure for you to be able to deploy, manage and run your container services, resources, and sample applications.

version: "1"
commands:
  - name: setup:0.1.0
    run: ./node_modules/.bin/ts-node /ops/src/setup.ts
    description: "setup an environment"
    env:
      static:
        - STACK_TYPE=aws-eks-ec2-asg
        - AWS_REGION=us-west-1
      secrets:
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
      configs:
        - DEV_AWS_EKS_EC2_ASG_STATE
        - STG_AWS_EKS_EC2_ASG_STATE
        - PRD_AWS_EKS_EC2_ASG_STATE
  - name: deploy:0.1.0
    run: ./node_modules/.bin/ts-node /ops/src/deploy.ts
    description: "deploy to an environment"
    env:
      static:
        - STACK_TYPE=aws-eks-ec2-asg
        - AWS_REGION=us-west-1
      secrets:
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
      configs:
        - DEV_AWS_EKS_EC2_ASG_STATE
        - STG_AWS_EKS_EC2_ASG_STATE
        - PRD_AWS_EKS_EC2_ASG_STATE
  - name: destroy:0.1.0
    run: ./node_modules/.bin/ts-node /ops/src/destroy.ts
    description: "destroy an environment"
    env:
      static:
        - STACK_TYPE=aws-eks-ec2-asg
        - AWS_REGION=us-west-1
      secrets:
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
  - name: ssh:0.1.0
    run: ./node_modules/.bin/ts-node /ops/src/ssh.ts
    description: "connect to bastion with ssh"
    env:
      static:
        - STACK_TYPE=aws-eks-ec2-asg
        - AWS_REGION=us-west-1
      secrets:
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
  - name: tunnel:0.1.0
    run: ./node_modules/.bin/ts-node /ops/src/tunnel.ts
    description: "connect to bastion with ssh"
    env:
      static:
        - STACK_TYPE=aws-eks-ec2-asg
        - AWS_REGION=us-west-1
      secrets:
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
  - name: vault:0.1.0
    run: ./node_modules/.bin/ts-node /ops/src/vault.ts
    description: "manage secrets vault"
    env:
      static:
        - STACK_TYPE=aws-eks-ec2-asg
        - AWS_REGION=us-east-1
      secrets:
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
      configs:
        - DEV_AWS_EKS_EC2_ASG_STATE
        - STG_AWS_EKS_EC2_ASG_STATE
        - PRD_AWS_EKS_EC2_ASG_STATE
    help:
      usage: ops run vault <sub-cmd> <--key> <--value>
      arguments:
        init: "init the environments vault"
        create: "set a key in the enviroment vault"
        list: "list keys in the environment vault"
        remove: " remove a specific key in the environment vault"
        destroy: "destroy the environment vault"
pipelines:
  - name: sample-app-pipeline:0.1.0
    description: build a release for deployment
    env:
      static:
        - DEBIAN_FRONTEND=noninteractive
        - ORG=workflows-sh
        - REPO=sample-app
        - REF=PROD-1
        - AWS_REGION=us-west-1
        - STACK_TYPE=aws-eks-ec2-asg
      secrets:
        - GITHUB_TOKEN
        - AWS_ACCESS_KEY_ID
        - AWS_SECRET_ACCESS_KEY
        - AWS_ACCOUNT_NUMBER
    jobs:
      - name: sample-app-build-job
        description: sample-expressjs build step
        packages:
          - git
          - unzip
          - python
        bind:
          - /Users/<user>/Development/<user_org>/ops/<sample_application>:/ops/application
        steps:
          - curl https://s3.amazonaws.com/aws-cli/awscli-bundle-1.18.200.zip -o awscli-bundle.zip
          - unzip awscli-bundle.zip && ./awscli-bundle/install -b ~/bin/aws
          - export PATH=~/bin:$PATH
          - aws --version
          # - git clone https://$GITHUB_TOKEN:[email protected]/$ORG/$REPO
          # - cd $REPO && ls -asl
          # - git fetch && git checkout $REF
          - cd application && ls -asl
          - aws ecr get-login-password --region $AWS_REGION | docker login --username AWS --password-stdin $AWS_ACCOUNT_NUMBER.dkr.ecr.$AWS_REGION.amazonaws.com/$REPO
          - docker build -f Dockerfile -t $AWS_ACCOUNT_NUMBER.dkr.ecr.$AWS_REGION.amazonaws.com/$REPO-$STACK_TYPE:$REF .
          - docker push $AWS_ACCOUNT_NUMBER.dkr.ecr.$AWS_REGION.amazonaws.com/$REPO-$STACK_TYPE:$REF

Build Pipelines locally with the CTO.ai CLI

In your terminal, enter the ops build . command and select the sample-app-pipeline. This ops build . command will build your op for sharing, your Docker image from your Docker file, and the set of files located in the specified path you created in your source code.

When your image is built, it’s going to create an image ID, and successfully tag it in your CTO.ai console.

Run Pipelines locally with the CTO.ai CLI

Run your pipeline by entering ops run . in your terminal. The ops run . command will start the workflow you built from your team or registry.

select the sample-app-pipeline - build a release for deployment

It will start running your pipeline job

Run and Setup your Infrastructure

Back in your AWS EKS EC2 ASG workflow, build and set up your infrastructure using the ops run -b . command. This will provision your AWS-EKS EC2 ASG stacks using Cloud Formation.

select setup an environment

The process will build your Docker image and start loading up your EKS EC2 ASG Autoscaling stack.

Enter the name if your environment. You can use dev as the name of your environment. You can also use Prod or Stage, depending on what you want.

Enter the name of your application repo you created which is sample-app and hit enter

Enter the name of the GitHub branch you want to use

Your workflow will start deploying and creating your resources on AWS using CloudFormation

You can see the deployment process and how your AWS EC2 and Elastic Kubernetes Service workflow is been deployed

view changes on AWS CloudFormation

After deploying your AWS EC2 and Elastic Kubernets workflow, you can see your stack directly on AWS CloudFormation. In your CloudFormation Stack you can see your AWS resources created:
Dev-AWS-EKS-ASG-Provider
AWS-EKS-EC2-ASG Resource
Dev-AWS-EKS-EC2-ASG
Sample-App-AWS-EKS
CDKToolkit
Dev-Sample-App-AWS-EKS-EC2-ASG

If you click on the stack name you will see your Stack info, Events, Resources, Outputs, Paramaters, Template, and Change sets

View EC2 instances on AWS

Back in your AWS console, you can see your EC2 instances running. The AWS EC2 Workflow creates four instances for you:

dev-aws-eks-ec2-asg-bastion
dev-aws-eks-ec2-asg/dev-aws-eks-ec2-asg-asg
dev-aws-eks-ec2-asg/dev-aws-eks-ec2-asg-asg
dev-aws-eks-ec2-asg/dev-aws-eks-ec2-asg-asg

When you click on the instance, you will see your Details, Security groups, Networking, Storage, Status checks, Monitoring and Tags resources

View Elastic Kubernetes Service Cluster

Next, in your EKS console you will see that your EKS cluster is automatically provisioned.

Inside your Cluster, you can see your kubernetes version, Status, Resourcs, Compute, Networking, Add-ons, Authentication, Logging, Update history and Tags.

View Auto Scaling groups

In your EC2 dashboard, you can see your auto scaling groups instances and status.

AWS Auto Scaling schedules the scaling actions that proactively increases and decreases capacity to match the load forecast. At the scheduled time, AWS Auto Scaling updates the minimum capacity with the value specified by the scheduled scaling action

DigitalOcean GCP-GKE-Pulumi-py