DevOps with AWS Training

• Git Fundamentals
• GitHub / GitLab
• Branching & Merging
• Pull / Merge Requests
• Conflict Resolution
• Git Workflows
• Git in a Team / Corporate Environment

• AWS Global Infrastructure
• IAM
• EC2
• EBS & AMI
• S3
• VPC
• Subnets & Route Tables
• Internet Gateway / NAT Gateway
• Security Groups & Network ACLs
• Load Balancer
• Auto Scaling
• Route 53
• CloudWatch

• Docker Architecture
• Images & Containers
• Dockerfile
• Docker Volumes
• Docker Networks
• Docker Compose
• Docker Registry / Docker Hub
• Multi-Stage Builds
• Container Security
• Docker on AWS

• CI/CD Concepts
• Jenkins
• Jenkins Pipeline
• Jenkins + Git
• Jenkins + Docker
• Webhooks
• Automated Build & Testing
• Deployment Pipelines
• Jenkins + AWS

• Terraform Fundamentals
• Providers & Resources
• Variables & Outputs
• Modules
• State Management
• Remote Backend
• Terraform + AWS
• Build AWS VPC / EC2 Using Terraform
• Terraform in CI/CD

• Ansible Fundamentals
• Inventory
• Modules
• Playbooks
• Roles
• Variables & Templates
• Ansible + AWS
• Ansible + Jenkins

• Kubernetes Architecture
• Pods
• Deployments
• ReplicaSets
• Services
• ConfigMaps & Secrets
• Namespaces
• Ingress
• Persistent Volumes
• Helm
• Kubernetes Troubleshooting

• EKS Architecture
• EKS Cluster Creation
• Node Groups
• IAM + EKS
• Deploy Applications on EKS
• Load Balancer + EKS
• Amazon ECR
• EKS + Jenkins
• EKS + Terraform
• Production EKS Architecture

• Security in CI/CD
• SonarQube
• SAST
• Dependency Scanning
• Trivy
• Container Security
• Secrets Management
• IAM Best Practices
• Security Gates in Jenkins

• Monitoring Fundamentals
• Prometheus
• Grafana
• Alertmanager
• Application Monitoring
• Infrastructure Monitoring
• Kubernetes Monitoring
• AWS CloudWatch
• Logs & Alerts

• Production Architecture
• High Availability
• Scalability
• Disaster Recovery
• Blue-Green Deployment
• Canary Deployment
• Rolling Deployment
• Zero-Downtime Deployment
• Secrets & Configuration Management
• Cost Optimization
• Security & Compliance
• Incident Management
• Production Troubleshooting
• Root Cause Analysis (RCA)
• Corporate Git Strategy
• CI/CD Governance
• DevOps Best Practices

Build and deploy a production-style application through an end-to-end DevOps pipeline.

The project connects source control, continuous integration, code quality, containerization, security scanning, cloud infrastructure, Kubernetes deployment, and monitoring.

Technology Flow:
GitLab → Jenkins → SonarQube → Docker → Trivy → Docker Registry / Amazon ECR → Terraform → AWS VPC → Amazon EKS → Kubernetes → Prometheus → Grafana → AWS CloudWatch

Corporate Workflow

1. Developer commits and pushes application code to GitLab.
2. Jenkins automatically triggers the CI/CD pipeline.
3. Jenkins builds and tests the application.
4. SonarQube performs code-quality and static-analysis checks.
5. Docker packages the application into a versioned container image.
6. Trivy scans the image for known vulnerabilities.
7. The approved image is pushed to Amazon ECR.
8. Terraform provisions or updates AWS infrastructure using Infrastructure as Code.
9. Kubernetes / Amazon EKS deploys and manages the application.
10. Prometheus, Grafana, and CloudWatch provide monitoring, dashboards, logs, and alerts.
11. DevOps engineers troubleshoot incidents, perform rollbacks, and continuously improve the delivery process.

Learning Outcome

By completing this roadmap and the final project, learners build an understanding of how modern DevOps teams move software from source code to a monitored cloud production environment. The emphasis is on practical integration between tools, automation, troubleshooting, security, and production operations— not on isolated tool commands.