Devops Engineer
CurrentAWS:-Setup weighted routing records on Route53, configured automatic failover from primary to backup disaster recovery region based on health checks. Troubleshoot DNS related user connectivity issues to services-Created a proof of concept serverless architecture for Lambda functions, wrote out all the core logic in Python mainly with boto3 library-Utilized various networking tools on AWS for traffic control and monitoring such as VPC peering, Transit Gateway-Cost optimized developer environments to run on spot instances, freed up a significant amount of m5 reserved instances for only mission critical workloads, saving us over $12,000 over the course of 1 year-Setup Config and IAM across multiple AWS accounts for DEV, UAT, and PROD to implement fine grain access control for various groups of engineers connecting to our environment-Would regularly troubleshoot developer issues on AWS such as service restarts, DNS related problems, identifying performance bottlenecks, adjusting IAM roles-Adjusted security groups, NACLs, setup new subnets, NAT gateways, route tables-Leveraged AWS EventBridge for cron based triggers to Lambda functionsKubernetes/Monitoring:-Created and modified helm charts for deploying new applications to EKS clustersInfrastructure as Code:-Refactored a large amount of messy Terraform code into clean, reusable modulesBundled together all permanent infra changes from other team members into Terraform code -Used Ansible to bootstrap environment variables before applying terraform deploy modules (done through a Jenkins CD pipeline)Security:-Leveraged AWS IAM analyzer for auditing our various IAM policies for vulnerabilities-Used both Sonarqube and Checkmarx through CI/CD pipelines for static code analysis to check for code smells-Used Trivy for automated scanning of our Docker container images -Implemented best security practices for any code I developed such as no hardcoding, proper use of environment variables