Comment (0)

Introduction

This article is an example of “Everything as a code” to create an ECS Fargate Stack in AWS using the Cloud Formation template through Jenkins.

Only Jenkins Master and codebase is required to check this flow. Check out the Github URL mentioned below to refer to the code.

You may also enjoy: The Best of Both Worlds With AWS Fargate

Jenkins Configuration

There is some Jenkins master node configuration required to trigger the pipeline. 

Docker Installation

Configure the Docker Installation in Jenkins > Manage Jenkins > Global Tool Configuration > Docker.

AWS Credentials

Need to store the AWS Credentials on Jenkins > Credentials > System > Global Credentials > Add Credentials

Then it will look like this under Jenkins > Credentials:

Be Familiar with Files and Folders 

In the code repository, there are some files and folder as below.

1. Templates folder — contains the YAML file which has Cloud Formation code to create the ECS Fargate.
2. Parameters folder — contains the JSON file and it contains all the parameters which are required Cloud Formation YAML
3. Dockerfile — A customized Dockerfile is created which has capabilities of AWS CLI and Cloud Formation Linting; no need to install these on Jenkins Master specifically.
4. Jenkinsfile — The  Jenkins Pipeline which will trigger all the stages like “Poll SCM,” “Validating CF template and JSON,” and “ Cloud Formation Stack creation.”

Approach 

There are so many approaches to achieve the same task. The first few of the CLI (AWSCLI and CFN-LINT) need to be installed on Jenkins Master or many Jenkins Plugins are available to trigger the ECS Fargate parameters.

Here, an approach is taken where code will take off everything and Jenkins Pipeline is written completely based on code.

A modular approach is taken for Cloud Formation code where templates and parameters are kept in the separate directory, so it will be easy to main the CF code better.

A customized Dockerfile will take care of the AWS CLI and CFN-LINT; no need to install these on Jenkins Master.

Jenkinsfile has 3 stages: 

1. Fetching code from the remote Git repository.
2. Validating the CF template and JSON file before creating the ECS Fargate stack. The CF template will be validated using CFN-LINT running inside the container. However, the Python “json.tool” module is used to validate the JSON file. If there is a problem with the CF template and JSON file validation, then this stage will be failed.
3. Here, ECS Fargate stack creation will be triggered, the ID will be successful, then it will return a stack ID.

Dockerfile code snapshot:

xxxxxxxxxx

FROM alpine:3.8

# Default evironment variables.

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_SECRET_ACCESS_KEY aws_Secret_key

COPY templates/New_ECS_Fargate_Para.yml .

COPY parameters/parameters.json .

RUN apk add -q --update /

    && apk add -q /

FROM alpine:3.8

FROM alpine:3.8

FROM alpine:3.8

FROM alpine:3.8

FROM alpine:3.8

FROM alpine:3.8

Jenkinsfile code snapshot:

FROM alpine:3.8

FROM alpine:3.8

FROM alpine:3.8

FROM alpine:3.8

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

# Default evironment variables.

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_DEFAULT_REGION us-east-1

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_ACCESS_KEY_ID aws_key_id

Create a Pipeline Job in Jenkins and execute the job. It will create the ECS Fargate stack in AWS.

However, this customized Dockerfile is not only for creating ECS Fargate stack, but even other commands can also be triggered which are working fine with the AWSCLI. 

For example:

ENV AWS_ACCESS_KEY_ID aws_key_id

ENV AWS_SECRET_ACCESS_KEY aws_Secret_key

It will show all the EC2 instances in the AWS account and the output will be displayed in tabular format.

Region name for AWS also can be passed using an argument like  -e “region-name”.

Find the code repository in Github here CF_ECS_FARGATE_Jenkins, and check out my DZone profile here.

Keep learning!!!

“Learning never exhausts the mind.” ― Leonardo da Vinci

Further Reading

Using CloudFormation to Set Up Scalable Apps

A Model-Based Approach to CD: From ”Everything as Code" to "Everything is a Model"

Comment (0)