NotHarshhaa/DevOps-Projects

What it is

This is a learning repository of 41 real-world DevOps and cloud projects graded from beginner to advanced. Each entry points to a project directory with a README giving prerequisites, deployment steps, and validation, rather than shipping one runnable application. Typical work includes deploying a Java or Django app on AWS, building CI/CD pipelines with Jenkins or GitLab, provisioning infrastructure with Terraform, and running workloads on EKS, AKS, or GKE.

The table of projects lists the tools each one uses, so you can pick by tool instead of reading everything: AWS EC2/RDS/VPC, Docker, Kubernetes, Terraform, Jenkins, SonarQube, Prometheus/Grafana, Argo CD, Azure DevOps, and more. Scope covers automated deployment, CI/CD, infrastructure as code, monitoring and logging, security and compliance, and scaling, per the project scope section.

A companion site at projects.prodevopsguytech.com renders the same project list as a browsable Next.js + Tailwind interface, which is often faster than scrolling the README table.

Quick start

1. Open the project overview table and choose a project matching your current level and toolset. Beginner projects start with Linux fundamentals and simple AWS deployments; the Java 3-tier AWS deployment (project 01) and the EKS end-to-end project (project 08) are among the more commonly featured entries.
2. Enter that project's directory in the repository and read its README. The repository-level README intentionally does not restate per-project setup steps; prerequisites, commands, and validation live in each project README.
3. Prepare the accounts, credentials, and local tools named in that README (for AWS projects, an AWS account with the relevant permissions and CLI access; for Terraform projects, Terraform installed; for Kubernetes projects, a cluster plus kubectl).
4. Follow the deployment steps in order and compare results against the README's validation section.
5. Clean up cloud resources when finished, especially for projects that create EC2, RDS, EKS, or NAT Gateways that bill by time.

The repository itself does not include a single install or run command for all projects, so there is no universal command to copy here. Use the per-project README as the authoritative entry point.

Constraints and things to check

• These are guided labs that create real cloud resources. You need accounts and permissions on AWS, Azure, or GCP depending on the project, and costs may accrue while resources are running.
• Many projects assume a working knowledge of the named tools; the beginner tier lowers this bar but does not remove it. Check the project's own prerequisites before starting.
• The repository declares no license and the README states all rights reserved with unauthorized reproduction prohibited, so treat the guides as learning material and check with the author before redistributing or reusing content commercially.
• Validation steps are described in the READMEs; there is no included automated test suite that verifies your deployment succeeded.
• Contributions follow the contribution guide and code of conduct; security reporting goes through the security policy.

HotRepo's take

On the Java daily chart for 2026-11-01, the repository recorded 8 new stars and reached position 9, while carrying 5,440 stars and 4,905 forks in total. That fork-to-star ratio is unusually high and fits the repository's shape: much of its audience likely forks the guides to work through them or keep a personal copy, rather than following the project as a software dependency. The site has no all-language daily rank or long time series for this repository, so one snapshot is not enough to describe a trend. What it does support is the character of the project as a widely forked lab collection, which is the right frame for anyone deciding whether to use it as a study path.