Cloud & DevOps Practice & Chapter-wise Tutorials — WeBotApp Academy CodeLab

beginner Level • Chapter 01 of 15

Linux Foundations & Terminal Administration

Master production Linux systems, systemd service management, SSH keys, and bash automation scripts.

Why Linux Powers 90%+ of Cloud Infrastructure

Over 90% of public cloud workloads, container platforms (Docker, Kubernetes), and enterprise production servers run on Linux distributions such as Ubuntu Server, Debian, Alpine, and Red Hat Enterprise Linux (RHEL). As a DevOps or Site Reliability Engineer (SRE), mastering the headless command-line interface (CLI) is your core operating environment.

•Filesystem Hierarchy: /etc (system configurations), /var/log (application logs), /opt (third-party software), /home (user dirs), and /proc (virtual kernel process filesystem).
•Permissions (chmod & chown): Read (4), Write (2), Execute (1). Understanding User, Group, and Other ownership is vital for zero-trust security.
•Systemd Service Management: The modern Linux init system. Use systemctl start, restart, enable, and status to control background daemons.

Process Diagnostics, I/O Redirection & Stream Automation

Linux treats everything as a file and communicates via three standard streams: Standard Input (stdin / 0), Standard Output (stdout / 1), and Standard Error (stderr / 2).

•Pipes and Redirection: Command chaining (|) and redirecting output (> overwrites, >> appends, 2>&1 merges error with standard output).
•Resource Monitoring: Use top, htop, vmstat, and iostat to diagnose CPU spikes, memory leaks, and disk I/O bottlenecks in real time.
•Journalctl: Query systemd binary journal logs with journalctl -u nginx.service -f --since '1 hour ago'.

Infrastructure Blueprints & Production Configurations

2 Practical Examples

Systemd SpecProduction Systemd Service Unit File Specification

Context & Practical Application: Enterprise-grade systemd service definition for running a Node.js / Python application with auto-restart, security sandboxing, and log rotation.

# /etc/systemd/system/webotapp-api.service
[Unit]
Description=WeBotApp Production API Service
After=network.target postgresql.service
Wants=postgresql.service

[Service]
Type=simple
User=appuser
Group=appgroup
WorkingDirectory=/opt/webotapp/api
ExecStart=/usr/bin/node /opt/webotapp/api/server.js
Restart=always
RestartSec=5s

# Environment Variables
Environment=NODE_ENV=production
Environment=PORT=4000
EnvironmentFile=/etc/webotapp/api.env

# Linux Security Hardening & Sandboxing Directives
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
ReadWritePaths=/var/log/webotapp
PrivateTmp=true

# Resource Limits
LimitNOFILE=65535
StandardOutput=journal
StandardError=journal
SyslogIdentifier=webotapp-api

[Install]
WantedBy=multi-user.target

☁️ Infrastructure Spec: Production configuration for cloud servers, Docker containers & CI/CD pipelines.DevOps Playbook

Bash AutomationAutomated Production Health Check & Log Rotation Bash Script

Context & Practical Application: Production bash script featuring strict error handling (set -euo pipefail), automated service recovery, and Slack / Discord webhook alerts.

#!/usr/bin/env bash
# ==============================================================================
# Production Service Health Monitor & Auto-Recovery
# Runs via cron every 5 minutes: */5 * * * * /opt/scripts/health_check.sh
# ==============================================================================
set -euo pipefail

SERVICE_NAME="webotapp-api.service"
HEALTH_URL="http://127.0.0.1:4000/api/health"
LOG_FILE="/var/log/webotapp/health_monitor.log"
ALERT_WEBHOOK="https://hooks.slack.com/services/T00/B00/X00"

log_message() {
  echo "[$(date '+%Y-%m-%d %H:%M:%S')] $1" | tee -a "$LOG_FILE"
}

# Check HTTP 200 response from internal health check endpoint
HTTP_STATUS=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 "$HEALTH_URL" || echo "000")

if [ "$HTTP_STATUS" -ne 200 ]; then
  log_message "CRITICAL: Service $SERVICE_NAME returned HTTP $HTTP_STATUS. Initiating restart..."
  
  # Restart service via systemctl
  systemctl restart "$SERVICE_NAME"
  sleep 3
  
  NEW_STATUS=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 "$HEALTH_URL" || echo "000")
  if [ "$NEW_STATUS" -eq 200 ]; then
    log_message "RECOVERED: Service $SERVICE_NAME restarted successfully. HTTP 200 confirmed."
  else
    log_message "FATAL: Service restart failed to restore HTTP 200. Sending alert to on-call SRE!"
    curl -X POST -H 'Content-type: application/json' \
      --data "{\"text\":\"🚨 P1 Alert: $SERVICE_NAME is DOWN on $(hostname)! Immediate action required.\"}" \
      "$ALERT_WEBHOOK"
  fi
else
  log_message "OK: Service $SERVICE_NAME is healthy (HTTP 200)."
fi

☁️ Infrastructure Spec: Production configuration for cloud servers, Docker containers & CI/CD pipelines.DevOps Playbook

Industry Case Study

Migrating Legacy Cron Jobs to Hardened Systemd Services

Scenario: A financial analytics platform in Guwahati ran 14 background cron jobs that silently failed when servers experienced memory pressure.

⚠️ Challenge / Problem:Engineers had no logs, no automatic restart mechanism, and no notification when worker processes died, causing missed daily financial reports.

✅ Solution & Strategy:Refactored all background workers into systemd unit files with Restart=always, set strict memory limits (MemoryMax=2G), and directed outputs to systemd journald with central log aggregation.

📈 Measurable Impact & Outcome:Zero silent failures over 12 months, automated self-healing within 5 seconds of transient OOM spikes, and instant visibility into service health.

Implementation Checklist & Operational Guardrails

Disable root SSH login (PermitRootLogin no) and enforce SSH key authentication in /etc/ssh/sshd_config

Set strict file permissions (chmod 600 for private keys, 644 for public configs, 700 for .ssh)

Wrap long-running background services in systemd unit files rather than raw nohup scripts

Use set -euo pipefail in all production bash scripts to ensure immediate failure on errors

Key Concepts • Chapter 01

•Mastering Linux terminal diagnostics and systemd is the foundational bedrock of all modern cloud engineering.
•Automate everything: replace manual server interventions with robust, idempotent shell scripts.

🎯 Chapter Practice Challenge

Write a bash script that inspects current memory usage using free -m and prints an alert if available memory is below 15%.

Hands-On Activity

Ready for the BEGINNER Assessment?

10 randomized questions with automated score & retake. Score 70% to pass!

# /etc/systemd/system/webotapp-api.service [Unit] Description=WeBotApp Production API Service After=network.target postgresql.service Wants=postgresql.service [Service] Type=simple User=appuser Group=appgroup WorkingDirectory=/opt/webotapp/api ExecStart=/usr/bin/node /opt/webotapp/api/server.js Restart=always RestartSec=5s # Environment Variables Environment=NODE_ENV=production Environment=PORT=4000 EnvironmentFile=/etc/webotapp/api.env # Linux Security Hardening & Sandboxing Directives NoNewPrivileges=true ProtectSystem=strict ProtectHome=true ReadWritePaths=/var/log/webotapp PrivateTmp=true # Resource Limits LimitNOFILE=65535 StandardOutput=journal StandardError=journal SyslogIdentifier=webotapp-api [Install] WantedBy=multi-user.target

#!/usr/bin/env bash # ============================================================================== # Production Service Health Monitor & Auto-Recovery # Runs via cron every 5 minutes: */5 * * * * /opt/scripts/health_check.sh # ============================================================================== set -euo pipefail SERVICE_NAME="webotapp-api.service" HEALTH_URL="http://127.0.0.1:4000/api/health" LOG_FILE="/var/log/webotapp/health_monitor.log" ALERT_WEBHOOK="https://hooks.slack.com/services/T00/B00/X00" log_message() { echo "[$(date '+%Y-%m-%d %H:%M:%S')] $1" | tee -a "$LOG_FILE" } # Check HTTP 200 response from internal health check endpoint HTTP_STATUS=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 "$HEALTH_URL" || echo "000") if [ "$HTTP_STATUS" -ne 200 ]; then log_message "CRITICAL: Service $SERVICE_NAME returned HTTP $HTTP_STATUS. Initiating restart..." # Restart service via systemctl systemctl restart "$SERVICE_NAME" sleep 3 NEW_STATUS=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 "$HEALTH_URL" || echo "000") if [ "$NEW_STATUS" -eq 200 ]; then log_message "RECOVERED: Service $SERVICE_NAME restarted successfully. HTTP 200 confirmed." else log_message "FATAL: Service restart failed to restore HTTP 200. Sending alert to on-call SRE!" curl -X POST -H 'Content-type: application/json' \ --data "{\"text\":\"🚨 P1 Alert: $SERVICE_NAME is DOWN on $(hostname)! Immediate action required.\"}" \ "$ALERT_WEBHOOK" fi else log_message "OK: Service $SERVICE_NAME is healthy (HTTP 200)." fi

Cloud Computing & DevOps Engineering

Linux Foundations & Terminal Administration

Why Linux Powers 90%+ of Cloud Infrastructure

Process Diagnostics, I/O Redirection & Stream Automation

Infrastructure Blueprints & Production Configurations

Migrating Legacy Cron Jobs to Hardened Systemd Services

Implementation Checklist & Operational Guardrails

Key Concepts • Chapter 01

🎯 Chapter Practice Challenge

Ready for the BEGINNER Assessment?

Practice Other Programming Languages:

Cloud Computing & DevOps Engineering

Linux Foundations & Terminal Administration

Why Linux Powers 90%+ of Cloud Infrastructure

Process Diagnostics, I/O Redirection & Stream Automation

Infrastructure Blueprints & Production Configurations

Migrating Legacy Cron Jobs to Hardened Systemd Services

Implementation Checklist & Operational Guardrails

Key Concepts • Chapter 01

🎯 Chapter Practice Challenge

Ready for the BEGINNER Assessment?

Practice Other Programming Languages: