Chapter 7: Static Website Hosting (3 OSes × 2 Web Servers)

7.9 Combination 4 — Ubuntu + Apache

By Ravindra Bagale Last updated: 15 October 2026

On Ubuntu, Apache's helper commands come in handy – a2ensite turns a site on, a2dissite turns the default site off. No need to make symlinks by hand.

Ubuntu वर Apache चे helper कमांड्स कामाला येतात – a2ensite ने साइट on, a2dissite ने default साइट off. हाताने symlink करायची गरज नाही.

Ubuntu पर Apache की helper कमांड्स काम आती हैं – a2ensite से साइट on, a2dissite से default साइट off. हाथ से symlink बनाने की ज़रूरत नहीं.

sudo service nginx stop 2>/dev/null
sudo systemctl disable nginx 2>/dev/null
sudo apt update && sudo apt install -y apache2

sudo tee /etc/apache2/sites-available/mysite.conf > /dev/null <<'EOF'
<VirtualHost *:80>
    ServerName mysite.local
    DocumentRoot /var/www/mysite
    <Directory /var/www/mysite>
        Options -Indexes +FollowSymLinks
        AllowOverride All
        Require all granted
    </Directory>
    ErrorDocument 404 /404.html
    ErrorLog  ${APACHE_LOG_DIR}/mysite_error.log
    CustomLog ${APACHE_LOG_DIR}/mysite_access.log combined
</VirtualHost>
EOF

sudo a2ensite mysite.conf
sudo a2dissite 000-default.conf
sudo a2enmod rewrite                 # useful for .htaccess rules later
sudo apache2ctl configtest && sudo service apache2 reload
curl -s http://localhost | head -5

Ravindra Bagale's Tip

Many students write the log path /var/log/httpd/ on Ubuntu Apache, and Apache won't start. On Ubuntu, use ${APACHE_LOG_DIR}, which points to /var/log/apache2/. And don't forget to reload after a2ensite.

Ravindra Bagale's Tip – मराठी

खूप students Ubuntu Apache वर log path /var/log/httpd/ लिहितात, आणि Apache start होत नाही. Ubuntu वर ${APACHE_LOG_DIR} वापरा, जो /var/log/apache2/ कडे point करतो. आणि a2ensite नंतर reload विसरू नका.

Ravindra Bagale's Tip – हिंदी

बहुत students Ubuntu Apache पर log path /var/log/httpd/ लिखते हैं, और Apache start नहीं होता. Ubuntu पर ${APACHE_LOG_DIR} इस्तेमाल करो, जो /var/log/apache2/ की तरफ point करता है. और a2ensite के बाद reload मत भूलो.

Lab

Chala, Ubuntu var Combination 4 kara aani sudo apache2ctl -S chalva – default server mhanun tumchi mysite.conf disate ka te bagha. Mag ls /etc/apache2/sites-enabled/ madhe 000-default.conf nahi na te check kara.

Extended teaching notes

Why this lesson matters

Cloud security is mostly IAM, network exposure, logging and secure defaults. The shared responsibility model means the provider patches the metal; you patch what you configure.

No public databases or public admin panels.
Roles / OIDC instead of long-lived access keys.
CloudTrail / Activity Logs / Audit Logs on and retained.
S3/Blob/GCS: Block Public Access; encrypt; least privilege.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

Write the lesson title, date and the exact lab target you are allowed to use.
List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
Run one safe check from the lesson on a lab system only. Paste the command and output.
Write a two-sentence fix you would give a teammate.
Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

Control: a safeguard (patch, config, process, detection).
Finding: a weakness backed by evidence.
Remediation: the fix plus how you verified it.
Scope: systems you have written permission to touch.
Least privilege: only the access the task needs.
Defence in depth: several layers so one failure does not end the story.

Common mistakes

Skipping written permission "just for a quick scan".
Practising on hostel, office or public targets without authorisation.
Collecting tool output without writing the fix.
Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

Evidence, fix, owner, date.
Own lab only.
Fix > spectacle.