AWS : CICD Automation — Deployment to AWS

Overview

In the below architecture the code repository and Gitlab CI tool are on premises. The CICD tool and Code Repo are setup in docker containers. Deployment is being done from on premises to AWS Cloud.

Steps Description:

Step 1: Developer commits the code on feature/development branch in the Gitlab repo. This Repo is set up using docker container.

Step 2–4: CICD development pipeline picks the committed code and performs build of the code and automated tests are executed. The results are published in the CICD logs. This Gitlab CICD is setup as docker container. A private registry is configured on-premise. The missing dependencies are downloaded from cloud. Else the build uses on-premises registry.

Step5 : Code is merged from feature branch to master branch.

Step 6–9: CICD development pipeline picks the committed code, performs build of the code &automated tests are executed. The results are published in the CICD logs.

Step 10: On Successful completion of tests, the docker images of the code are deployed to AWS cloud on elasticbeanstalk via awscli and awsebcli.