7. Apache and Nginx: Install and Understand

7.4 Installing Nginx and Apache on Ubuntu

By Ravindra Bagale Last updated: 15 October 2026

Also in the AWS course: this lesson is the same as 6.5 Ubuntu 22.04 / 24.04 in the AWS course, which is the main version of this page.

Ubuntu var apt install kelyavar service aapoaap start hote – pan enable karun ghene changli savay.

sudo apt update
sudo apt install -y nginx
sudo service nginx start
sudo systemctl enable nginx          # already started by apt, this makes sure
sudo service nginx status
sudo nginx -t
curl -I http://localhost
ls /var/www/html                           # contains index.nginx-debian.html
ls -l /etc/nginx/sites-enabled/            # 'default' -> ../sites-available/default

Apache on Ubuntu

sudo apt update
sudo apt install -y apache2
sudo service apache2 start
sudo systemctl enable apache2
sudo service apache2 status
sudo apache2ctl configtest
curl -I http://localhost

Useful Ubuntu-only Apache helpers:

Command	Purpose
`sudo a2ensite mysite.conf` / `a2dissite`	Enable / disable a virtual host
`sudo a2enmod rewrite proxy proxy_http` / `a2dismod`	Enable / disable modules
`sudo a2enconf` / `a2disconf`	Enable / disable extra config snippets

Ubuntu firewall (ufw)

ufw is inactive by default on Ubuntu EC2 AMIs — the AWS security group is your firewall. If you enable ufw, allow SSH first or you will lock yourself out: sudo ufw allow OpenSSH && sudo ufw allow 'Nginx Full' && sudo ufw enable (use 'Apache Full' for Apache).

Ravindra Bagale's Tip

If you run ufw enable on Ubuntu without allowing SSH first, you lock yourself out of the server – many students have done this. First sudo ufw allow OpenSSH, then the web rule, then enable. Remember the order.

Ravindra Bagale's Tip – मराठी

Ubuntu वर ufw enable केलं आणि आधी SSH allow केलं नाही तर तुम्ही स्वतःलाच server मधून बाहेर काढता – बऱ्याच students नी असं केलं आहे. आधी sudo ufw allow OpenSSH, मग web rule, मग enable. क्रम लक्षात ठेवा.

Ravindra Bagale's Tip – हिंदी

Ubuntu पर ufw enable किया और पहले SSH allow नहीं किया तो तुम ख़ुद को ही server से बाहर कर देते हो – बहुत से students ने ऐसा किया है. पहले sudo ufw allow OpenSSH, फिर web rule, फिर enable. क्रम याद रखो.

Lab

On your Ubuntu instance install Nginx, check the symlink in sites-enabled, then install Apache on a second Ubuntu instance (or after stopping Nginx) and list enabled sites with ls /etc/apache2/sites-enabled.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

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.