# techiescamp/devops-projects: ten AWS folders and a coupon block in front of them

> techiescamp/devops-projects is a numbered set of AWS automation exercises for engineers who learn by provisioning real infrastructure. Its README sells Kubernetes exam vouchers and cloud credits harder than it explains the ten projects it indexes.

**techiescamp/devops-projects** — DevOps Real World Projects for Aspiring DevOps Engineers [Beginner to Advanced]

- Repository: https://github.com/techiescamp/devops-projects
- Website: https://devopscube.com/devops-projects/
- Stars: 2,392 · Forks: 1,615
- Language: HCL
- License: not declared
- Published: 2026-10-14 · Updated: 2026-10-14 · Language: en
- Canonical page: https://hysenlabs.com/projects/techiescamp-devops-projects

## A curriculum index on the main branch, not an installable package

The repository holds fifteen top level entries: a `.gitignore`, a README, ten numbered folders and two shared ones. Its default branch is main, and its primary language is HCL, the language Terraform writes, which fits a set of infrastructure exercises far better than an application would. The topic tags say as much, since devops-learning, devops-poc, devops-tools and practical-devops are all attached to it, and the poc tag does the honest work here.

Nothing in it installs. There is no package name, no dependency manifest, no container image and nothing to pull, so treat this as a reading list with working files attached rather than a tool. What it offers instead is a route through a single AWS account. Each numbered folder is a self contained exercise, and the guidance framing them is one sentence long: provision while you practise, destroy the resources when you finish, and you avoid unnecessary costs.

## Ten numbered folders, one misspelling, no per-folder guidance

Every exercise is a numbered directory, and the numbering runs 01 through 10: `01-jenkins-setup`, `02-consul-sevice-discovery`, `03-scalable-java-app`, `04-prometheus-observability-stack`, `05-aws-vpc-design-and-automation`, `06-aws-client-vpn-setup`, `07-pritunl-vpn-setup`, `08-fargate-app-deployment`, `09-github-action-oidc-aws` and `10-route53-private-hosted-zone`. One name in that list is misspelled, and the fault sits in the folder rather than in a link aimed at it: service discovery loses its r, and the README link carries the identical wrong spelling, so the link resolves while the name stays broken.

Past the title, the index stops. No entry names a file, a Terraform version, a provider block or an input variable, so a reader who wants the shape of any exercise has to open the folder and read it. The one place per project detail does surface is the video list, where the first exercise appears as a Jenkins HA setup on AWS using an autoscaling group built with Packer, Ansible and Terraform.

## Two shared folders and two projects that are not AWS at all

The index claims uniform scope. Every project listed includes automation scripts to provision infrastructure on AWS, with no exception written anywhere, yet two of the ten do not match that sentence. `04-prometheus-observability-stack` is named as Docker Compose work, which runs on a host you already hold rather than on an account you provision. `07-pritunl-vpn-setup` is stranger to the claim still, because Pritunl is a VPN server an operator installs and runs, not an AWS resource with an hourly price.

Two further folders sit at the top level outside the numbering entirely: `generic-infra-code` and `platform-tools`. Neither is described anywhere in the text, so a learner working strictly down the numbered list never finds out what they hold, or whether a given exercise depends on them. For a repository whose primary language is HCL, keeping two folders whose purpose it will not state is the sharpest thing here.

## There is no clone command, so the first step is manual

There is no installation path to write down. The project gives no clone command, no make target, no terraform init invocation and no version constraint for Terraform or any provider, and it hands over no credentials file. What it does offer is where the files live: each exercise sits in a numbered folder on the main branch, reachable directly by its repository URL, and the README points twice to a companion blog at `devopscube.com/devops-projects/` for project ideas that are planned rather than built.

So the honest first run is manual. Create an AWS account, fetch the repository yourself, open the folder you want and read what is inside before executing any of it, because a folder title is all the guidance you get. Two things are worth settling before the first apply. Confirm which provider credentials the exercise expects, since none are named anywhere in the text. Then locate the teardown path, because the promise that you can destroy resources after completion is the only cost control on offer.

## The Kubernetes voucher block outgrew the project list

Open the README and the first thing you meet is not a project. The opening block is a Kubernetes Certification Voucher advertisement for CKA, CKAD, CKS, KCNA and KCSA, pushed with the code `DCUBE30` at `kube.promo/devops` and credited as a limited-time offer from the Linux Foundation. It opens by telling learners in 2026 that building projects matters, though so does holding an industry recognised certificate.

The discount is stated twice and the two figures disagree. The prose says aspirants can save 30% today, then the bundle list says the same code saves up to 38% on three bundles, namely CKA plus CKAD, CKA plus CKS, and all three exams together. Registration also buys one year of validity to sit the exam. The block closes by pointing at a second repository, `techiescamp/linux-foundation-coupon`, for current bundle offers, and all of this sits above the project index rather than beside it.

## Every credit row is a link, and two of them carry referral codes

Below the projects, the second commercial stretch is a free-credit table covering six platforms: Google Kubernetes Engine at $300, AWS at $200, DigitalOcean at $200, Linode at $100, Vultr at $250 and Azure at $200. Two rows do not link to the provider. The DigitalOcean entry appends `ref=devopscube.com` together with a numeric code, refcode=8223070813, and the Linode row avoids the provider's own domain altogether, pointing at a tracking host on linode.gvw92c.net with the same referral parameter attached.

Read as a table of sign-up pages, those two rows mislead, and the AWS row matters most because every one of the ten exercises assumes an AWS account. The surrounding text does carry one real argument: browser based labs suit certification drills, but for work at this size a live account teaches networking, IAM permissions, troubleshooting and cost behaviour that a sandbox cannot.

## One published video for ten exercises, and it names the stack

A video section sits below all of this, and it is nearly empty. The heading promises that all project videos will be available on Youtube, then gives the published list, which holds exactly one entry: Jenkins HA setup on AWS using an autoscaling group with Packer, Ansible and Terraform.

That is one video for ten exercises. Nine projects have no video, no written walkthrough and no architecture diagram anywhere in the repository text. The single title also carries more stack detail than everything around it combined, because Packer and Ansible appear nowhere else in the whole README, which makes that one line the only dependable hint about how the first exercise is assembled.

## Reference layouts to read, not tutorials to run

So judge it as a set of reference layouts. What you get is ten realistic topologies, each small enough to read in an afternoon: a Jenkins controller behind an autoscaling group, Consul doing service discovery, a scalable Java application, a Prometheus stack on Docker Compose, VPC design and automation, a client VPN, Pritunl, a Fargate deployment, a GitHub Actions OIDC integration with AWS, and a private hosted zone in Route 53.

What you do not get is documentation. No folder is explained, no version is pinned anywhere in the text, the cost guidance amounts to one sentence about destroying what you built, and the scope claim in the index does not survive its own entries. Working through one of these means reading it the way an experienced engineer reads a stranger's Terraform, not following a tutorial from start to finish.

## Conclusion

Adopt it as a source of topologies, not as a product: ten small AWS exercises are worth an afternoon each for an engineer who already knows Terraform. Anyone needing runnable, documented automation should pass, because no folder ships a walkthrough and no teardown path is named. Check two things before copying files. Neither a LICENSE file nor a licence field appears among the top level entries, and the last push was on 2026-06-29, so ask the authors about reuse terms first, then confirm your pinned Terraform version still applies to the HCL inside the folder you picked.

## FAQ

### How do I start a project from techiescamp/devops-projects?

Each exercise is a numbered folder on the main branch and the project gives no clone command, so you fetch the repository yourself and open the folder you want. You need an AWS account, because the stated purpose of all ten is to provision infrastructure on AWS, and you should destroy what you created once you finish to avoid unnecessary costs.

### Is techiescamp/devops-projects a tool I can install?

No. There is no package, container image or install command anywhere in it; the repository is ten numbered exercise directories plus a README index, and its primary language is HCL because the exercises are written in Terraform. The documented way in is the folder URL on the main branch.

### Which cloud accounts do the projects need and how much free credit is offered?

The exercises target AWS, and the free-credit table covers six providers: Google Kubernetes Engine at $300, AWS at $200, DigitalOcean at $200, Linode at $100, Vultr at $250 and Azure at $200. The README argues that browser based labs suit certification drills while real accounts teach the networking, IAM and cost behaviour these projects touch.

### Are there video walkthroughs for all ten projects in techiescamp/devops-projects?

No, only the Jenkins HA setup on AWS project has a published video, titled as using an autoscaling group with Packer, Ansible and Terraform. The other nine exercises have no video and no written walkthrough in the repository text.

### Does techiescamp/devops-projects publish tagged releases for its exercises?

No, the repository has no GitHub releases and nothing to pin. The exercises live in numbered folders on the main branch, so a clone taken today is not the same tree as a clone taken next month.

## Sources

- [Issues](https://github.com/techiescamp/devops-projects/issues)
- [Project website](https://devopscube.com/devops-projects/)
- [README](https://github.com/techiescamp/devops-projects/blob/main/README.md)
- [techiescamp/devops-projects on GitHub](https://github.com/techiescamp/devops-projects)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/techiescamp-devops-projects