Amazon App Deployment: A DevSecOps Approach with Terraform and Jenkins CI/CD | Docker |

In these project we are deploying the Amazon App using the DecSecOps Plugins with Jenkins CI/CD & Docker For the Containerizing . These All Whole Infrastructure Creating with the terraform.

Use the below Blog to install Terraform and Aws cli

AWS CLI - https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html

Terraform - https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli

Step1: create an IAM user

Search for IAM -> Click "Users" -> Click "Add users" -> Click the "User name" field. -> Type "Terraform" or as you wish about the name -> Click Next -> Click "Attach policies directly"

Click this checkbox with Administrator access -> Click "Next" -> Click "Create user" -> Click newly created user -> Click "Security credentials" -> Click "Create access key" -> Click this radio button with the CLI -> Agree to terms -> Click Next -> Download .csv file

Step2: Aws Configure

Go to vs code or Cmd your wish

Provide your Aws Access key and Secret Access key

Step3: Terraform files and Provision Jenkins,sonar

main.tf

provider.tf

install.sh

Terraform commands to provision

OUTPUT -

SonarQube -

Copy your Public key again and paste it into a new tab

Enter username and password, click on login and change password

Check trivy version

Step 4 — Install Plugins like JDK, Sonarqube Scanner, NodeJs, OWASP Dependency Check

4A — Install Plugin

Goto Manage Jenkins →Plugins → Available Plugins →

Install below plugins

1 → Eclipse Temurin Installer (Install without restart)

2 → SonarQube Scanner (Install without restart)

3 → NodeJs Plugin (Install Without restart)

4B — Configure Java and Nodejs in Global Tool Configuration

Goto Manage Jenkins → Tools → Install JDK(17) and NodeJs(16)→ Click on Apply and Save

Step 5 — Configure Sonar Server in Manage Jenkins

Grab the Public IP Address of your EC2 Instance, SonarQube works on Port 9000, so <Public IP>:9000.

Goto your Sonarqube Server. Click on Administration → Security → Users → Click on Tokens and Update Token → Give it a name → and click on Generate Token -> copy Token

Goto Jenkins Dashboard → Manage Jenkins → Credentials → Add Secret Text. It should look like this

Now, go to Dashboard → Manage Jenkins → System and Add like the below image.

Click on Apply and Save

The Configure System option is used in Jenkins to configure different server

Global Tool Configuration is used to configure different tools that we install using Plugins

We will install a sonar scanner in the tools.

In the Sonarqube Dashboard add a quality gate also

Administration--> Configuration-->Webhooks

Let's go to our Pipeline and add the script in our Pipeline Script.

Click on Build now, you will see the stage view like this

To see the report, you can go to Sonarqube Server and go to Projects.

Step 6 — Install OWASP Dependency Check Plugins

GotoDashboard → Manage Jenkins → Plugins → OWASP Dependency-Check. Click on it and install it without restart.

First, we configured the Plugin and next, we had to configure the Tool

Goto Dashboard → Manage Jenkins → Tools →

Click on Apply and Save here.

Now go configure → Pipeline and add this stage to your pipeline and build.

The stage view would look like this,

Step 7 — Docker Image Build and Push

We need to install the Docker tool in our system, Goto Dashboard → Manage Plugins → Available plugins → Search for Docker and install these plugins

Docker

Docker Commons

Docker Pipeline

Docker API

docker-build-step

and click on install without restart

Now, goto Dashboard → Manage Jenkins → Tools →

Add DockerHub Username and Password under Global Credentials

Add this stage to Pipeline Script

Stage View -

You will see the output below, with a dependency trend.

When you log in to Dockerhub, you will see a new image is created

Now Run the container to see if the game coming up or not by adding the below stage

Stage view

You will get this output

Let's destroy everything

Go to VS Code and provide the below command (or) Go to the path where you provisioned the Ec2 instance

Pipeline

Last updated