Deploy reNgine on Azure

Overview

This tutorial guides you through deploying reNgine Cloud on Microsoft Azure using our pre-built ARM (Azure Resource Manager) template. The deployment creates all necessary resources including Azure VM, Azure Database for PostgreSQL, Azure Cache for Redis, and docker-compose orchestration for reconnaissance services.

Step 1: Access Azure Portal

Log into the Azure Portal and create a new Resource Group for your reNgine deployment.

Step 2: Deploy ARM Template

Use our ARM template to deploy reNgine infrastructure:

# Using Azure CLI
az deployment group create \
  --resource-group rg-rengine-prod \
  --template-uri https://hailbytes.com/templates/rengine-arm-template.json \
  --parameters \
    vmSize=Standard_D4s_v3 \
    adminUsername=azureuser \
    postgresqlSku=GP_Gen5_2 \
    redisSku=Premium

# Or click this button in the portal:
# Deploy to Azure button links to template

Alternatively, in the Azure Portal: go to "Create a resource" → "Template deployment" → "Build your own template" → paste the ARM template JSON.

Step 3: Configure Deployment Parameters

Fill in the required parameters for your deployment:

Step 4: Review and Create

Validate your configuration and deploy the resources.

Step 5: Access Your reNgine Dashboard

Once deployment completes, retrieve your connection information:

# Get public IP address
az vm show -d -g rg-rengine-prod -n vm-rengine-prod \
  --query publicIps -o tsv

# Get deployment outputs
az deployment group show \
  -g rg-rengine-prod \
  -n rengine-deployment \
  --query properties.outputs

# Outputs will include:
# - webURL: https://:8000
# - databaseFQDN: rengine-db.postgres.database.azure.com
# - redisFQDN: rengine-cache.redis.cache.windows.net
# - sshCommand: ssh azureuser@

Navigate to the Web URL and log in with default credentials (sent to your admin email or available in deployment outputs).

Understanding the Architecture

reNgine on Azure uses managed services for scalability and reliability:

# SSH into your VM to view running containers
ssh azureuser@

# View docker-compose services
cd /opt/rengine
sudo docker-compose ps

# Expected output:
NAME                STATUS              PORTS
rengine-web        Up 5 minutes        0.0.0.0:8000->8000/tcp
rengine-celery     Up 5 minutes
rengine-celery-beat Up 5 minutes
rengine-proxy      Up 5 minutes        0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp

Post-Deployment Configuration

Configure SSL with Let's Encrypt

Set up free SSL certificates for your reNgine instance:

# SSH into Azure VM
ssh azureuser@

# Update domain in NGINX configuration
sudo nano /opt/rengine/nginx/rengine.conf

# Update server_name directive
server_name rengine.yourcompany.com;

# Install certbot
sudo apt-get update
sudo apt-get install -y certbot python3-certbot-nginx

# Generate certificate
sudo certbot --nginx -d rengine.yourcompany.com

# Follow prompts to complete setup
# Certbot will automatically configure NGINX and set up auto-renewal

# Restart nginx container
cd /opt/rengine
sudo docker-compose restart proxy

Ensure your domain's DNS A record points to your Public IP before running certbot.

Configure Azure Database Firewall

Allow the VM to connect to Azure Database for PostgreSQL:

# Get VM's private IP
az vm show -g rg-rengine-prod -n vm-rengine-prod \
  --query "privateIps" -o tsv

# Add firewall rule to PostgreSQL
az postgres flexible-server firewall-rule create \
  -g rg-rengine-prod \
  -n rengine-db \
  -r allow-vm \
  --start-ip-address 10.0.0.4 \
  --end-ip-address 10.0.0.4

# Or allow Azure services
az postgres flexible-server firewall-rule create \
  -g rg-rengine-prod \
  -n rengine-db \
  -r allow-azure \
  --start-ip-address 0.0.0.0 \
  --end-ip-address 0.0.0.0

Troubleshooting

Scaling and Performance

Scale your reNgine deployment as your needs grow:

Cost Estimation

Monthly Azure costs for typical reNgine deployment:

Next Steps