The course runs four modules over 16 weeks. Every week has a lab, and every module ends with something you have built and can show.

Module 01, Linux and Networking Foundations (weeks 1 to 4)

• Week 1: The Linux command line. Installing a Linux VM, the shell, navigation, files and directories, editors, reading man pages, getting help without a search engine.
• Week 2: Users, permissions and processes. Users and groups, sudo, file permissions and ownership, process management, systemd services, logs and journalctl.
• Week 3: Networking for engineers. IP addressing and subnets, DNS, ports, TCP and HTTP basics, SSH keys and hardening, firewalls, diagnosing connectivity with common tools.
• Week 4: Shell scripting and package management. Bash scripting, variables, loops and conditions, cron, package managers, storage and mounts, and a scripted server setup as the module lab.

Module 02, Containers with Docker (weeks 5 to 8)

• Week 5: Docker from first principles. Images versus containers, the Docker CLI, running and inspecting containers, container lifecycle, why containers exist.
• Week 6: Building images. Dockerfiles, layers and caching, multi-stage builds, image size, tagging, pushing to a registry.
• Week 7: Networking, volumes and Compose. Container networking, persistent data with volumes, environment configuration, Docker Compose for multi-container applications.
• Week 8: A containerised application stack. Packaging a web application with a database and reverse proxy in Compose, health checks, logging, and the module lab: a stack you can start with one command.

Module 03, CI/CD and Automation (weeks 9 to 12)

• Week 9: Git the way teams use it. Branching, pull requests, merge conflicts, code review flow, tagging releases, keeping a clean history.
• Week 10: Jenkins. Installing and securing Jenkins, pipelines as code with Jenkinsfile, build agents, credentials, artefacts, triggering builds from Git.
• Week 11: GitHub Actions. Workflows, jobs and runners, secrets, matrix builds, building and pushing Docker images from a workflow, reusable actions.
• Week 12: Deployment strategies. Automated testing in the pipeline, environments, rolling and blue-green deployments, rollbacks, and the module lab: a pipeline that takes a commit to a running container.

Module 04, AWS Cloud and Infrastructure as Code (weeks 13 to 16)

• Week 13: Compute and networking on AWS. The AWS console and CLI, IAM users and roles, launching and sizing EC2, designing a VPC with public and private subnets, route tables and security groups.
• Week 14: Load balancing, databases and storage. Application Load Balancer with target groups and health checks, RDS for the database tier, S3 for object storage, backups and static assets.
• Week 15: Security and monitoring. Least-privilege IAM policies, instance roles instead of keys, CloudWatch metrics, logs and alarms, cost awareness and budgets.
• Week 16: Terraform. Providers, resources, variables and state; rebuilding the week 13 to 15 infrastructure as code; plan, apply and destroy; and the final lab: a version-controlled AWS environment deployed from Terraform.

Module 04 is where this becomes an AWS course. You work in real AWS accounts, not on slides, and the services you touch are the ones a job posting means when it asks for AWS experience.

• EC2. Launching, sizing, connecting and managing instances, with instance roles rather than access keys.
• VPC. A network you design yourself: public and private subnets, route tables, internet and NAT gateways, security groups that mirror a production layout.
• ALB. An Application Load Balancer in front of your instances, so traffic distribution and health checks stop being theory.
• RDS. A managed database tier in a private subnet, with backups and parameter basics.
• S3. Object storage for backups, static assets and artefacts, with bucket policies and lifecycle rules.
• IAM. Least-privilege policies, roles for services, and why nobody should be using root.
• CloudWatch. Metrics, logs and alarms, so you can tell whether what you deployed is healthy.
• Terraform. The same infrastructure expressed as code you can version, review and rebuild.

Core AWS services plus Infrastructure as Code is the combination employers look for. If you plan to sit an AWS certification afterwards, AWS exam vouchers are available through Techcake.

There are no formal prerequisites. Basic comfort with a computer is enough; the course starts from the Linux command line and builds up. Any degree or diploma background is fine, and you do not need programming experience.

If you would like a stronger Linux base before starting, the three-month Linux System Administration course is the usual bridge. If you are unsure, the free counsellor call will help you assess fit.

You receive a Techcake course completion certificate that documents the curriculum and the duration. It is not a vendor certification. The Career Program additionally includes a training completion certificate for the project phase.