Created CICD pipeline using Jenkins, Nexus, SonarQube and Elastic Beanstalk environment on AWS
Integrated Jenkins with GitHub, Nexus, Sonarqube, slack and Elastic beanstalk Environment
Used Maven to build Java Web application and Nexus server to host dependencies for Maven
Created quality gates in SonarQube dashboard and enforced it in the pipeline to fail the builds when conditions were not met
Once the code passed unit, Integration tests and SonarQube quality gates then well tested artifact with build version was stored in Nexus Repository
Deployed tested artifact to staging Elastic Beanstalk environment, conducted performance tests on staging environment by adding Windows server as node to Jenkins server
Deployed serverless website with view counter on AWS and created CICD pipeline using GitHub actions
Hosted a responsive personal wesite in AWS using S3, CloudFront, Lambda, DynamoDB and API gateway
Frontend consist of S3- to store a static content and CloudFront- to implement HTTPS
Backend provides website visitor counter and comprises API gateway, Lambda function and DynamoDB
Automated the entire backend using AWS Serverless Application Model (SAM)
Created CI/CD pipeline with GitHub actions
Automated deployment of highly available infrastructure for Java based web application on AWS using Terraform
Configured Terraform state for the infrastructure on Amazon S3
Deployed VPC using Terraform modules
Launched frontend and backend services in private subnets and only web facing ALB in public subnet
Deployed highly available Web Application using Amazon Elastic Beanstalk, Amazon MQ, Elastic Cache and Amazon RDS
Created custom VPC with 3x Public subnets and 3x private subnets
Provisioned Multi-AZ MySQL using RDS service, 2xnode Memcached cluster using Elastic Cache, Active/Standby ActiveMq message broker using Amazon MQ service in private subnets of custom VPC
Using Elastic Beanstalk deployed ALB and tomcat ec2 instances in Auto Scaling Group (ASG)
Uploaded build artificact into Elastic Beanstalk environment
Added Elastic Beanstalk environment end point as CNAME in the domain provider dns setting to divert the traffic to ALB, So, that users can use meaningful URL to reach our application. And update the same URL in Cloud Front to be distributed using CDN
Provisioned a Web application stack on AWS using EC2
Deployed Web application using Amazon EC2 instances, Route53, Application Load balancer (ALB) and Amazon Certificate Manager (ACM)
Backend consists of RabbitMQ, Memcached, Mariadb and frontend consists of Tomcat instance. Deployed Tomcat, RabbitMQ, Memcached, Mariadb instances with user-data scripts (bash).
Created a private hosted zone in Route53 to map the names of backend services to ip address of the instances so that frontend can interact with backend services
Assigned appropriate IAM role to Tomcat instance to access the build artifact from s3
Configured Application Load Balancer (ALB) with HTTPS using certificate from Amazon Certificate Manager (ACM) and then mapped ALB endpoint to custom domain name
