AWS DevOps Project | Maven + Jenkins CI/CD Pipeline | Deploy WAR to Tomcat on EC2 Using AWS SSM

*End-to-End AWS DevOps Project: Maven + Jenkins + Tomcat Deployment Using AWS Systems Manager (SSM)* In this hands-on DevOps project, we build a CI/CD pipeline using Jenkins and Maven to package a Java web application into a WAR file, store the artifact in Amazon S3, and deploy it to an Apache Tomcat server running on an AWS EC2 instance. A key part of this project is using **AWS Systems Manager (SSM) to deploy the application without requiring an SSH PEM key**. 🎯 *What You Will Learn:* ✅ Create and configure AWS EC2 instances for Jenkins and Tomcat ✅ Set up a Java Maven web application ✅ Configure Maven to build a WAR artifact ✅ Configure Jenkins to automate the build and deployment process ✅ Upload the WAR artifact to Amazon S3 ✅ Configure IAM roles and permissions for secure AWS access ✅ Use AWS Systems Manager Run Command to deploy the WAR to Tomcat ✅ Deploy a Java web application on Apache Tomcat ✅ Troubleshoot SSM connectivity and IAM permission errors ✅ Verify the deployed application using a browser or curl 🏗️ *Project Architecture:* GitHub → Jenkins → Maven Build → WAR Artifact → Amazon S3 → AWS Systems Manager (SSM) → Tomcat on EC2 🛠️ *Technologies Used:* AWS EC2 AWS IAM AWS Systems Manager (SSM) Amazon S3 Jenkins Apache Maven Java Apache Tomcat Git and GitHub Linux 💡 *Real-Time DevOps Scenario:* What happens when you lose the SSH private key for your application server? In this project, we explore how AWS Systems Manager can provide an alternative deployment method, provided the instance is properly configured and authorized. This project is useful for beginners learning AWS DevOps, CI/CD pipelines, Java application deployment, and real-world infrastructure troubleshooting.