🚁 Fleet Management System

Overview

The Sauron Fleet Management System enables centralized control and coordination of multiple VPS instances. This distributed architecture provides scalability, redundancy, and enhanced operational security.

🎛️

Centralized Control

Single point of command for all VPS instances

📡

Real-time Communication

Live status updates and command execution

🔄

Auto-Scaling

Dynamic deployment and management

Architecture

Fleet Components

Fleet Master Controller

Central command and control server that manages all VPS instances in the fleet.

  • • VPS registration and heartbeat monitoring
  • • Command distribution and execution
  • • Fleet-wide analytics and reporting
  • • Emergency kill switch coordination

VPS Agents

Individual Sauron instances running on distributed VPS servers.

  • • Automatic registration with fleet master
  • • Periodic heartbeat and status reporting
  • • Command execution and response
  • • Local kill switch capabilities

Communication Protocol

Secure HTTPS-based communication with mutual authentication.

  • • TLS 1.3 encryption for all communications
  • • Admin key authentication
  • • Automatic failover and retry logic
  • • Steganographic command embedding

Setup and Configuration

Fleet Master Setup

# 1. Run interactive fleet master configuration
./scripts/fleet-master.sh

# 2. Configure domain and ports
Domain: admin.yourdomain.com
Admin Port: 8443
Fleet Port: 8444

# 3. Security settings
Admin Key: [auto-generated or custom]
SSL Email: admin@yourdomain.com

# 4. Fleet capacity
Max VPS Instances: 50
Heartbeat Timeout: 300 seconds

# 5. Deploy fleet master
sudo -E scripts/deploy-fleet-master.sh

The fleet master should be deployed on a dedicated server with high availability.

VPS Agent Setup

# 1. Run interactive fleet agent configuration
./scripts/fleet-agent.sh

# 2. Auto-discovery will detect:
Public IP: [auto-detected]
VPS Provider: DigitalOcean/AWS/Vultr/etc
System Specs: 4 cores, 8GB RAM, 160GB SSD

# 3. Fleet master connection
Master Host: admin.yourdomain.com
Master Port: 8444
Admin Key: [from fleet master]

# 4. Agent configuration
Agent ID: [auto-generated unique ID]
Agent Name: digitalocean-agent-1
Auto Updates: enabled
Heartbeat Interval: 60 seconds

# 5. Deploy fleet agent
sudo -E scripts/deploy-fleet-agent.sh

Fleet Operations

VPS Registration and Heartbeat

Registration Process:

  1. VPS agent starts and auto-detects configuration
  2. Generates unique VPS ID if not exists
  3. Registers with fleet master via HTTPS
  4. Receives confirmation and heartbeat schedule

Heartbeat Monitoring:

  • • Every 5 minutes by default
  • • Includes system status and metrics
  • • Automatic retry on failures
  • • Failover to backup masters
# Check fleet status
curl -H "X-Admin-Key: $ADMIN_KEY" \
     https://admin.yourdomain.com:8444/fleet/register

# Force VPS re-registration
systemctl restart sauron-fleet-agent

# View fleet logs
journalctl -u sauron-fleet-master -f

Command Distribution

Available Commands:

  • script - Deploy/update injection scripts
  • config - Update configuration files
  • restart - Restart services
  • status - Get detailed system status
  • killswitch - Emergency destruction

Execution Flow:

  1. Command sent via fleet master API
  2. Master validates and queues command
  3. Command delivered to target VPS(es)
  4. Agent executes and reports results
# Send command to specific VPS
curl -X POST https://admin.yourdomain.com:8444/fleet/command \
  -H "Content-Type: application/json" \
  -d '{
    
    "vps_id": "vps-abc123",
    "command": "status",
    "timeout": 30
  }'

# Broadcast command to all VPS instances
curl -X POST https://admin.yourdomain.com:8444/fleet/command \
  -H "Content-Type: application/json" \
  -d '{
    
    "vps_id": "*",
    "command": "script",
    "payload": {
      "script_type": "injection",
      "content": "base64_encoded_script"
    }
  }'

🚨 Emergency Procedures

Fleet-wide Kill Switch

⚠️ WARNING: This procedure permanently destroys all fleet data and systems.

# Emergency fleet destruction
curl -X POST https://admin.yourdomain.com:8443/admin/killswitch \
  -H "Content-Type: application/json" \
  -d '{
    
    "vps_id": "",
    "destruction_level": 5,
    "delay_seconds": 0,
    "reason": "Law enforcement detected",
    "confirmation_code": "OMEGA-DESTROY"
  }'

# Alternative: Script-based emergency kill
./scripts/emergency-kill.sh --fleet --level 5 --confirm OMEGA-DESTROY

Dead Man's Switch

Automatic fleet destruction if operator fails to send heartbeat within configured timeframe.

# Configure dead man's switch (24 hour timeout)
curl -X POST https://admin.yourdomain.com:8443/admin/deadmans \
  -H "Content-Type: application/json" \
  -d '{
    
    "action": "configure",
    "timeout_hours": 24,
    "destruction_level": 4,
    "enabled": true
  }'

# Send operator heartbeat
curl -X POST https://admin.yourdomain.com:8443/admin/deadmans/heartbeat \
  -H "Content-Type: application/json" \
  -d '{
    
  }'

# Check dead man's switch status
curl -H "X-Admin-Key: your_admin_key" \
     https://admin.yourdomain.com:8443/admin/deadmans

📊 Monitoring and Analytics

Fleet Dashboard

Real-time Metrics:

  • • Active VPS instances
  • • Total fleet capacity
  • • Geographic distribution
  • • Performance metrics
  • • Security alerts

Historical Analytics:

  • • Fleet growth over time
  • • Regional performance comparison
  • • Uptime and reliability stats
  • • Command execution history
  • • Incident response times
# Access fleet dashboard
https://admin.yourdomain.com:8443/dashboard

# Get fleet metrics via API
curl -H "X-Admin-Key: your_admin_key" \
     https://admin.yourdomain.com:8443/api/metrics/fleet

# Generate fleet report
./scripts/fleet-report.sh --period 7d --format json

Security Monitoring

Threat Detection

  • • Law enforcement IP detection
  • • Honeypot identification
  • • Behavioral analysis
  • • Geographic anomalies

Fleet Security

  • • Inter-VPS communication monitoring
  • • Command authentication logs
  • • Heartbeat anomaly detection
  • • Unauthorized access attempts

Automated Response

  • • Automatic VPS isolation
  • • Progressive kill switch activation
  • • Evidence destruction protocols
  • • Emergency communication channels

Best Practices

✅ Recommended Practices

  • • Deploy fleet master on high-availability infrastructure
  • • Use geographically distributed VPS providers
  • • Implement automated backup and recovery procedures
  • • Regular security audits and penetration testing
  • • Maintain multiple communication channels
  • • Configure dead man's switch with appropriate timeouts
  • • Monitor fleet health and performance continuously
  • • Use unique admin keys for each deployment

⚠️ Security Considerations

  • • Never use fleet management on shared hosting
  • • Avoid predictable VPS provider patterns
  • • Implement network-level access controls
  • • Regular admin key rotation (weekly/bi-weekly)
  • • Monitor for law enforcement infrastructure
  • • Maintain operational security protocols
  • • Test kill switch procedures regularly
  • • Use secure communication channels only

Troubleshooting

Common Issues

VPS Not Registering

  • • Check network connectivity to fleet master
  • • Verify admin key configuration
  • • Confirm DNS resolution for fleet master domain
  • • Check firewall rules on both ends
  • • Review VPS agent logs: journalctl -u sauron-fleet-agent

Commands Not Executing

  • • Verify VPS is registered and active
  • • Check command authentication
  • • Review command payload format
  • • Monitor fleet master logs for errors
  • • Test with simple status command first

Fleet Master Unreachable

  • • Check fleet master server status
  • • Verify SSL certificate validity
  • • Test DNS resolution and routing
  • • Review load balancer configuration
  • • Implement backup fleet master if needed