Position: DevOps engineer
Category: DevOps
English level: fluent
Years of experience: 4

• Linux Foundation Certified System
Administrator(LFCA)
• Certified Kubernetes Administrator
• Certified AWS cloud practitioner
• Certified AWS solutions Architect
1 Responsible for application Build & Release process which includes Code Compilation, Packaging, Security
Scanning and code quality scanning, Deployment Methodology and Application Configurations.
2 Designed and deployed the amazon eks cluster which is used for hosting stateless applications. This was
infrastructure was deployed using a terraform script and involved the eks worker nodes, vpc and vpc
components, the roles and policies, AWS ALB Ingress controller, cluster autoscaler, the elastic container
registry, route53, S3 buckets for the static application hosting, cloud front, AWS certificate manager, Amazon
relational databases and web application firewall.
3 Set up the monitoring stack based on Prometheus and grafana. Scrapped application logs using loki, and
configured alerting endpoints on slack and Microsoft teams. This was deployed using helmcharts.
4 Deployed the microservices on kubernetes using various kubernetes objects such as deployment (for the
stateless apps), configmap(to store environment variables), AWS secret manager and secret store CSI
drivers(to handle secrets), HPA(to handle pod scalability) and service monitor(to help send pod metrics to
appropriate endpoint).
5 Set up a CI/CD pipeline based on Jenkins and GitHub action. GitHub actions deploys the static
applications(frontend) to the S3 bucket and sends feedback alerts to slack while Jenkins implements a shared library for all the application repositories. It also sends feedback alerts to slack. The CI/CD workflow includes static code analysis using sonarqube to ensure code quality, security and coverage integrated other security tools like Fortify, Veracode, Snyk in Jenkins Ci/CD build pipeline. 
7 used lambda functions on AWS to automatate various processes which includes, copying the
automated generated snapshots from the primary region to the disaster recovery region, stopping and starting
RDS instances at a set time of the night and day respectively, deleting snapshots that have exceeded a certain number of days etc. This was achieved using cron expressions on cloud watch events.
7 Set up a site-to-site vpn connection with our partners to ensure a dedicated connection to our private
services. On Our AWS account, this was achieved using AWS transit gateway. Same was set up on our
digital ocean account using Strong swan.