Fully Managed, Secured, and Optimized Jenkins

1. Launch an Instance

   From AWS Marketplace, click Continue to Subscribe and then Continue to Configuration to launch the AMI.

2. Choose the Recommended Instance Type

   Select t2.medium or higher for stable performance and smooth Jenkins pipeline execution.

3. Configure Security Group

   Allow inbound traffic on the following ports:

   • 22 (SSH) - For secure terminal access

   • 80 (HTTP) - Required temporarily during SSL validation

   • 443 (HTTPS) - To securely access the Jenkins web UI

4. Connect to the Instance

   ssh -i <your-key.pem> ubuntu@<public-ip>

5. First-Boot Setup

   On first run, the AMI performs an automatic guided setup:

   • Detects your server's public IP
   • Prompts for the domain name to be mapped to Jenkins (e.g., jenkins.example.com)
   • Validates DNS to confirm the domain points to this instance
   • Requests admin email (used for SSL & notifications)
   • Configures Apache as a reverse proxy for secure HTTPS access
   • Automatically requests and installs a Let's Encrypt SSL certificate
   • Creates the initial Jenkins root user with a securely generated password

   After setup completes, Jenkins starts automatically and becomes accessible via HTTPS.

6. Configure DNS

   Before or during setup, create this DNS A record:

   your-domain.com <your-instance-public-IP>

   The setup script will automatically detect DNS propagation and continue once the mapping is correct.

7. Automatic SSL Setup

   Once DNS resolves correctly:

   • A free SSL certificate is issued from Let's Encrypt
   • HTTPS is enabled and enforced
   • All traffic is securely routed to Jenkins

8. Start or Restart Jenkins Manually (if needed)

   cd /opt/app docker compose ps docker compose restart

9. Access Jenkins Web UI

   Open your browser and visit:

   https://<your-domain>

10. Login Credentials

Your Jenkins login credentials are stored in:

cat /opt/app/.env

This file includes:

• JENKINS_EMAIL
• JENKINS_PASSWORD
• DOMAIN