1. Why SSL/TLS Matters
The Horizon dashboard provides administrative access to your OpenStack cloud—meaning any unencrypted traffic could expose:
-
User credentials
-
Keystone tokens
-
Sensitive API calls
-
Configuration data
Using SSL/TLS ensures:
-
π Encrypted communication
-
π‘οΈ Mitigation against MITM attacks
-
βοΈ Compliance with security standards (SOC2, ISO, CIS Benchmarks)
HTTPS is mandatory for any production OpenStack deployment.
2. Prerequisites
Before proceeding, ensure you have:
-
βοΈ A working OpenStack deployment with Horizon
-
βοΈ Apache web server (default for Horizon)
-
βοΈ A domain name pointing to the Horizon server
-
βοΈ Root or sudo access
-
βοΈ (Optional) Public IP for Let’s Encrypt
3. Option A: Secure With Let’s Encrypt (Recommended)
This is ideal for public-facing or internet-accessible dashboards.
Step-by-Step
What this does:
-
Automatically configures Apache HTTPS
-
Sets up 90-day certificates (auto-renewed)
-
Redirects all HTTP → HTTPS
4. Option B: Manual SSL/TLS Configuration (Self-Signed)
Use this for offline, internal, or air-gapped environments.
Step-by-Step
βοΈ Step 1: Generate a self-signed certificate
βοΈ Step 2: Update the Horizon Apache configuration
Add the HTTPS VirtualHost:
βοΈ Step 3: Enable SSL and restart Apache
5. Verification & Hardening
βοΈ Verify access
Open:
https://dashboard.rshnetwork.com
You should see a secure lock icon.
βοΈ Test SSL strength
Use SSL Labs or Nessus/SIEM security plugins.
βοΈ Recommended hardening (Apache SSL)
Disable weak protocols like TLS 1.0/1.1:
Reload Apache:
FAQs (0)
Sign in to ask a question. You can read FAQs without logging in.