Learn. Build. Secure. Automate. Accelerate with AI. Live Training • Hands-On Labs • Expert Mentorship by Coach AK Contact: +1 (469) 733-5248 | devops.coaching@gmail.com
🔴 FREE LIVE WEBINAR
How to Become a DevOps Engineer in 2027
From Zero to DevOps Champion!
November 21st, 2026
9:30 AM CST
Live DevSecOps CI/CD Demo
Career Roadmap • Live Q&A
Setup SSH keys and upload public key into Ubuntu EC2 instance where Tomcat will be installed.
Modify hosts/inventory file to add target Ec2 instance ip address/dns name.
port 8080 is opened in firewall rule
Steps to setup SSH keys:
1. Login to Ansible management server/machine. Create SSH keys in Ansible host machine by executing the below command: (if you already have keys created, please skip this step)
ssh-keygen
enter three times..now you will see keys successfully created. 2. Execute the below command on Ansible management node and copy the public key content: sudo cat ~/.ssh/id_rsa.pub
copy the above output. 3. Now login into target node where you want to install Tomcat, execute the below command to open the file sudo vi /home/ubuntu/.ssh/authorized_keys type shift A and then enter now and paste the key in the above file. please do not delete any existing values in this file.
4. Now go back to Ansible mgmt node, do changes in /etc/ansible/hosts file to include the node you will be installing software. Make sure you add public or private IP address of target node as highlighted below in red color: sudo vi /etc/ansible/hosts [My_Group] xx.xx.xx.xx ansible_ssh_user=ubuntu ansible_ssh_private_key_file=~/.ssh/id_rsa ansible_python_interpreter=/usr/bin/python3
5. Create a Playbook for setting up Tomcat 9
sudo vi installTomcat.yml --- - hosts: My_Group tasks:
sh ('kubectl apply -f jenkins-aks-deploy-from-acr.yaml')
}
}
}
}
}
}
Step # 5 - Build the pipeline
Step # 6 - Verify deployments to AKS
kubectl get pods
kubectl get services
Steps # 7 - Access Springboot App Deployed in AKS cluster
Once deployment is successful, go to browser and enter above load balancer URL mentioned above
You should see page like below:
Clean up the Cluster:
To avoid charges from Azure, you should clean up unneeded resources. When the cluster is no longer needed, use the az group delete command to remove the resource group, container service, and all related resources.
az group delete --name myResourceGroup --yes --no-wait
Webhooks allows developers to triggers jobs in CI server (such as Jenkins or Azure DevOps) for every code changes in SCM. In this article, we will learn how to trigger Azure Pipeline build jobs instantly for every code change in SCM.
Pre-requisites:
1. Azure Build pipeline is already configured. If you dont know how to create Azure build pipeline, click on this link.
2. SCM repo have been setup, either in GitHub or Bitbucket or any SCM
Watch Steps in YouTube
Steps to Enable Webhooks in Azure Build Pipeline
Go to Azure DevOps project dash board.
Go to Pipelines
Click on Pipelines
Click on Edit
Click on Triggers tab, Click Continuous Integration checkbox to enable Webhooks.
Click on Save the Job. You don't have to Queue the job.
Now go to your SCM and make a code change, you will see pipeline job will trigger immediately.
Microsoft has temporarily disabled the free grant of parallel jobs for public projects and for certain private projects in new organizations. However, you can request this grant by submitting a request. Submit a ticket using below url to request increased parallelism in Azure DevOps.