Ritish Rampa

Description: Designed, developed, and maintained CI/CD pipelines, infrastructure automation scripts, and cloud solutions. Focused on automating deployment processes, improving infrastructure reliability, and enabling self-service capabilities for platform teams. Responsibilities included scripting, infrastructure monitoring, and troubleshooting within Jenkins and GitLab-CI pipelines, with a strong emphasis on AWS services and tools such as Terraform, Ansible, and Puppet.

Responsibilities:

• Developed and maintained Terraform scripts, for infrastructure provisioning, ensuring consistency across platforms.
• Deployed large-scale applications utilizing almost the entire AWS stack (Including EC2, Route53, S3, RDS, Dynamo DB, SNS, SQS, IAM) focusing on high-availability, fault tolerance, and auto-scaling in AWS CloudFormation.
• Participated in application deployment using Continuous Integration (CI) and Continuous Deployment (CD) through Jenkins.
• Developed AWS Lambda Pythonscript to automate the removal of unused security groups and network ACLs.
• Configured Cloudwatch dashboards to monitor real-time, granular metrics for all AWSServices.
• Migrated applications from on-premises to AWSusing the lift-and-shift method.
• Implemented Puppet for configuration management and deployment automation, ensuring best practices in SCM processes.
• Used Splunk for monitoring and metric collection in a cloud-based environment.
• Created CI/CD pipeline to enable end to end setup of build &deployment processes for applications includes testing and deploying code to multiple environments.
• Provided self-service access for platform teams via the Jenkins console, enabling them to start and stop EC2 and RDS instances.
• Built and maintained automation scripts using Linux, Bash, Groovy and python scripts.

Environment: AWS, CI/CD, Jenkins, Linux, Bash, Gitlab-CI, Ansible, Terraform, AWS, Route53, S3, RDS, Dynamo DB, SNS, SQS, IAM, PowerShell, Puppet, Apache, Splunk.

Description: This project's objective was to create and maintain reusable Terraform modules and Ansible playbooks to simplify infrastructure configuration for developers, saving time and allowing them to concentrate on creating apps. This made sure that developers never had to worry about configuring infrastructure themselves and always had access to the most recent configurations.

Responsibilities:

• Worked on writing infrastructure as a code (laC). Have developed reusable Terraform modules for both the AWS and Azure cloud platforms.
• Worked on public/private cloud infrastructures using AWS which include EC2, S3, Cloud Front, Elastic File System, RDS, VPC, Direct Connect, Route53, ECS, Cloud Watch, Cloud Trail, Cloud Formation, and IAM which allowed automated operations.
• Troubleshoot issues along the CI/CD for Jenkins and Gitlab-CI pipelines and Configuring the Gitlab runner for Gitlab-CI pipelines.
• Builds of the Kubernetes apps, managed releases of Helm packages, provided a set of configuration options to modify the deployment, and managed Kubernetes charts using Helm.
• Worked on Ansible playbooks to automate the process of installation, maintain servers like patching and upgrading the applications.
• Installed, tested and deployed monitoring solutions with Splunk services and installed Power shell for Windows based projects.
• Skilled on database technologies, such as SQL, PLSQL, MySQL, RDS, and NoSQL (DynamoDB) databases.
• Used scripting languages like Python, Ruby, Bash, and configuration management tools Chef, Puppet, and Web Services like AWS.
• Configuring and managing an ELK stack, setup the Elastic search ELK Stack to collect, search and analyze log files across the servers. Evaluated system logs using ELK Stack.
• Configured Grafana and Prometheus to monitor databases, and use Grafana to create personalized dashboards.
• Performed regular builds and deployment of the packages for testing in different Environments (DEV, UAT and PROD).
• Used application should be monitored with New Relic after it has been developed and put into production environment.
• Developed automation scripts in Perl, Shell, and Python to deploy some apps as well as automate the build and release process.
• Maintain GIT repository giving access and group controls and automated the existing build process using build tools like ANT and Maven.
• Created quality gates in SonarQube and enforced in the pipelines to fail the builds when conditions not met.
• Worked on setting up fresh connections to the Azure Resource Manager (ARM) Service for several teams.
• Azure portal and ARM Templates were used to deploy Azure IaaS virtual machines (VMs) and Cloud services (PaaS role instances) into secure VNets and subnets.
• Worked on tracking tools to trigger issues and update defects logs using Jira.
• Good experience in Agile/Scrum methodologies.
• Installed Firmware Upgrades, kernel patches, systems configuration, system Performance tuning on Unix/Linux systems.

Environment: AWS, Azure, Terraform, Kubernetes, Python, New Relic, SonarQube, Perl, Shell, ARM, Chef, Puppet, Docker, Jenkins, Chef, Puppet, SQL, PLSQL, No SQL, MY SQL, ELK, Grafana, Prometheus, SonarQube, Agile, Scrum, Unix, Linux, Jira, Git, Ant, Maven.

Description: This project's major objective was to create a CI/CD pipeline that enhanced teamwork and automated testing using SonarQube, tracked system performance with Prometheus and Grafana, and allowed developers to scale infrastructure to meet demand. Customers now have access to higher-quality products because to the system's accelerated development and release cycle.

Responsibilities:

• Implemented infrastructure as code (IaC) using tools like Terraform to automate the provisioning and management of cloud resources, ensuring consistency and reproducibility across environments.
• Created Kubernetes Deployment YAML files to configure the set of Pods running’s and also created Kubernetes Service file to enable the network access.
• Enhanced Chef, Puppet work as configuration management tools to deploy consistent infrastructure across multiple environments.
• Worked on Docker hub, creating Docker images and handling multiple images primarily for middleware installations and domain configurations.
• Extensively worked on Jenkins by installing, configuring, and maintaining the purpose of CI and End-to- End automation for all build and deployments implementing CI/CD for the database using Jenkins.
• Configured network and server monitoring using Grafana, ELK stack with Nagios for notifications and installed/configured monitoring tool Nagios for monitoring the network bandwidth and the hardware status.
• Used Ansible Playbooks with Ansible modules, implemented CD automation using Ansible, managing existing servers and automation of build/configuration of new servers.
• Responsible for design and maintenance of the Subversion/GIT Repositories and access control strategies.
• Involved in Grafana and Prometheus monitoring system build and integrated gray log into it.
• Used engineering teams have implemented the NoSQL notion using MongoDB and various queuing systems
• Developed Bash and Python scripts to automate applications migration and monitor application health during migration.
• Integrated Jenkins with other DevOps tools, including as Nexus, SonarQube, and Ansible.
• Used Atlassian tools, JIRA as ticketing tool for task/bug/request tracking and Confluence as collaboration tool and BitBucket to share code segments.
• Software Release Management techniques were developed and implemented utilizing the agile methodology, and they were effective for a range of applications.

Environment : AWS, Terraform, Agile, No SQL, MongoDB, Bash, Python, Nexus, SonarQube, Ansible, Docker, Kubernetes, Chef, Puppet, Jenkins, Grafana, Prometheus, CI/CD, ELK, Nagios, SVN, GIT, Jira, Confluence, Bitbucket.