Aswani Mamidi

Results-driven over all experience 4.5 years , process associative with 2 years of experience , I have skilled in using Git, Jenkins, Terraform, Ansible, Docker, ArgoCD, and Kubernetes. Proficient in AWS services including VPC, EC2, S3, Route 53, Load Balancer, and Auto Scaling. Adept at automating deployment processes, managing infrastructure,and optimizing container orchestration.Committed to leveraging technical expertise to enhance development workflows and system reliability. Diligent [Desired Position] with solid background in streamlining operational processes and improving efficiency. Proven track record of supporting workflow improvements and ensuring compliance with company standards. Demonstrated ability in problem-solving and effective communication. Process professional with keen eye for detail and commitment to continuous improvement. Skilled in identifying process inefficiencies and implementing solutions that drive productivity. Highly collaborative team player known for reliability and adaptability. Expertise in process documentation and data analysis.

Project Title: Blue-Green Deployment on AWS EKS

Key Responsibilities:

Infrastructure Setup:Provisioned AWS EC2 instances (t2.medium) with security groups allowing traffic on ports .Installed necessary tools on EC2 instances, including AWS CLI, Terraform, and kubectl.

Terraform Configuration:Cloned and configured the Blue-Green deployment repository.

Executed Terraform commands (init, plan, apply) to set up the Kubernetes cluster on EKS.

Kubernetes Resource Management:Created a namespace (webapps) and set up a Service Account for Jenkins.

Defined and applied Kubernetes roles and role bindings to manage permissions for the Jenkins service account. Managed Kubernetes secrets for secure credential storage.

Jenkins Installation and Configuration:

Installed Jenkins on a dedicated server, including necessary plugins for Docker, Maven, and Kubernetes integration. Configured Jenkins to use tokens and credentials for connecting with SonarQube and Nexus.

Containerization and Deployment:

Deployed SonarQube and Nexus using Docker containers, ensuring integration with the Jenkins CI/CD pipeline. Configured Jenkins jobs for building, testing, and deploying applications to the EKS cluster.

Security and Access Management:Implemented role-based access control (RBAC) for Kubernetes resources.

Managed Docker permissions for Jenkins and ensured secure access to Nexus for artefact storage.

Technologies Used:

 AWS (EC2, EKS, IAM)

 Terraform

 Kubernetes

 Docker

 Jenkins

 SonarQube

 Nexus

Project Title: 3-Tier Application Deployment on AWS with DevSecOps Practices

Key Responsibilities:

IAM User Setup:

Created an IAM user with appropriate permissions for deployment and management tasks on AWS.

Infrastructure as Code (IaC):Utilized Terraform and AWS CLI to provision a Jenkins server on an EC2 instance.

Jenkins Server Configuration: Installed and configured essential tools on the Jenkins server, including Jenkins, Docker, SonarQube, Terraform, kubectl, AWS CLI, and Trivy.

EKS Cluster Deployment: Deployed an Amazon EKS cluster using eksctl for managed Kubernetes service orchestration.

Load Balancer Configuration: Configured an AWS Application Load Balancer (ALB) to manage traffic for the EKS cluster.

Amazon ECR Repositories: Created private Amazon ECR repositories for storing frontend and backend Docker images.

ArgoCD Installation:Installed and configured ArgoCD for continuous delivery and GitOps practices.

SonarQube Integration:Integrated SonarQube for automated code quality analysis within the DevSecOps pipeline.

Jenkins Pipelines:

Developed Jenkins pipelines to facilitate the deployment of backend and frontend applications to the EKS cluster.

Monitoring Setup:

Implemented monitoring for the EKS cluster using Helm, Prometheus, and Grafana for performance insights.

ArgoCD Application Deployment:

Utilized ArgoCD to deploy a 3-tier application architecture, including database, backend, frontend, and ingress components.

DNS Configuration:Configured DNS settings for custom subdomain accessibility of the application.

Data Persistence:

Established persistent volume and persistent volume claims for database pods to ensure reliable data storage.

Route 53 Configuration:Created DNS records in Route 53 for the ingress load balancer to manage traffic routing.

Technologies Used:

 AWS (EC2, EKS, IAM, ECR, Route 53)

 Terraform

 Jenkins

 ArgoCD

 Docker

 SonarQube

 Prometheus

 Grafana

 Helm