
6 years of hands-on experience in designing, implementing, and maintaining secure and scalable AWS infrastructure, leveraged Terraform to streamline resource provisioning and maintaining automated infrastructure deployments, experienced in application migration to cloud, containerizing applications, implementing CI/CD pipelines
Over 24 years of IT experience ranging from Cloud Infrastructure design, architecture and automation, Project Management, Development of Dot Net based Web Applications. Experienced in managing the clients across industries and geographies
Excellent interpersonal, analytical & negotiation skills, with the ability to relate to people at any level of business
AWS & Terraform Consultant
Incepta Solutions Inc.Cloud and DevOps Consultant
NEC CorporationConsulting AWS Solutions Architect
The Cherry Hill CompanySoftware Programmer
Allion Technologies Ltd.Sr. Software Engineer
Illusions Online India Pvt. Ltd.Technical Project Manager
Capgemini India Pvt. Ltd.Software Programmer and Ecommerce Faculty
V to U.Com India Pvt. Ltd.
AWS ECS

ECR

EC2

S3

VPC

WAF

API Gateway

Lambda

Beanstalk

EBS

RDS

DynamoDB

CloudFormation

SNS

CloudWatch

AWS CLI

Azure VM

SQL Server

Terraform

Terragrunt

Packer

Github Actions

Chef

Github

Bitbucket

AWS CodeCommit

Shell Scripting

PowerShell

Linux

Ubuntu

CentOS

Windows Server 2016
.png)
Docker

Kubernetes
Vikas is highly skilled technically, while also being an excellent communicator - a rare combination. He is also very diligent, flexible, hard working and proactive, whether working on a team or on his own. In short, he's a pleasure to work with.
Vikas Arora worked in my team for around 4 years at Rave/NEC Software Solutions. He is a talented AWS/DevOps Architect with extensive experience which is always a value add. He has been instrumental in designing the architecture and contributing to the operational issues. He is a mature individual and always keen to learn and support team members whenever required.
Hi, my name is Vikas Arora. I have over 6 years of experience in cloud computing, which includes AWS, as well as some experience with Azure, Terraform, containerization using Docker and Kubernetes. Overall, I have 24 years of IT experience. I've also worked for 14 years at Capgemini in the capacity of technical lead and technical manager. This is my brief.
What method would you implement to automate the backup of ETLs? What is the best way to automate the backup of ETLs? What is the best way to automate the backup of ETLs? What is the best way to automate the backup of ETLs? What is the best way to automate the backup of ETLs?
my example could be serverless as well, so like lambda or your API gateway. We can then use a failover mechanism, like the failover mechanism of route 53, to switch to another region. However, that's only possible in an active-active setup. In an active-passive setup, we have to manually bring it up and then change route 53 to point to the other region.
The role of the load balancer in a Kubernetes cluster is to capture all the pods. So, there are multiple clusters in which there are multiple pods. So the load balancer will point to all these pods. Using auto-scaling, if there are more pods coming up, the load balancer will start pointing to them. In the case of scale-in, the number of pods reduces, then the load balancer will stop pointing to them as the pods are destroyed.
Can you suggest a strategy to migrate on-premises applications? So, assuming that these applications, on-premise applications, they are non-microservice-based or non-containerized applications. First, we have to come up with a strategy for converting them into microservices. This involves modularizing the application into microservices. Then, after dividing the application, we will have to write the required Docker files for all these microservices. Next, we have to create Docker images for these microservices, either using a Continuous Integration and Continuous Deployment (CICD) pipeline or manually. These Docker images will then be stored in Amazon Elastic Container Registry (ECR). From there, they can be deployed to Amazon Elastic Container Service (ECS) or Amazon Elastic Kubernetes Service (EKS), depending on the size of the application and the expected load.
There are a couple of ways which I am aware of, so one you could use HashiCorp Vault to secure sensitive data, and other ways to use environment variables.
We'll be back. The only issue I see in this particular Dockerfile is in the command `run mkdir slash code`. So that may give an error. So rather than using `slash code`, we will just use `code`, okay? So it will create a directory named `code`. And similarly, then we have to use `&&` `cd code`. The rest looks okay to me.
You need a security code set for instance. In instances this cancels the CPU, it's just a mistake not bad. Let's go and change the code to set for instance and let's install this. It will do the rest of the instructions. It could probably be related to multiple instances and how this could be how this list will be.
I'm not sure about this question.
Though we can use any CI-CD tool with Kubernetes, I have personally used GitHub Actions to create a CI-CD pipeline for Kubernetes, but the popular ones would say Argo CD is there.
I'm not sure what the question is asking. Can you give me a little more context about the question?