SSA Ops Platform – Mission Bus & Resilience Lab

This repository contains a compact but expressive Space Situational Awareness (SSA) operations platform that combines several aspects:

• Orbital conjunction analysis (SSA Conjunction Lab)
• SSA Operations Sandbox (jobs + results + tracks)
• Event-driven Mission Bus (Redis pub/sub) with HMAC-protected telemetry
• Security monitoring and basic cyber resilience / chaos injection
• Multi-sensor tracking of synthetic orbital objects
• Docker-based microservice architecture
• Example QEMU / ARM sensor node concept
• Minimal Kubernetes manifests for a cluster deployment

All orbital objects, sensor data and scenarios are synthetic and purely for educational / portfolio purposes. No real satellite, organisation or military actor is referenced.

Services (Docker Compose)

• api – FastAPI backend, REST API, DB access, metrics, HMAC-checked telemetry
• worker-conjunction – performs orbital conjunction analysis for jobs
• worker-tracking – consumes measurement events and updates tracks
• security-monitor – subscribes to security events (invalid HMAC etc.)
• chaos-injector – periodically sends bogus telemetry to test robustness
• db – PostgreSQL database
• bus – Redis-based mission bus (pub/sub)
• frontend – static web UI served by Nginx (for basic visualisation)
• qemu-node – conceptual ARM Linux sensor agent (not part of Compose)

Quickstart (Docker)

Requirements:

• Docker + Docker Compose (or docker compose)
• Internet access for base images (PostgreSQL, Redis, Nginx, Python)

From the project root:

docker compose up --build

Once everything is up, open:

• API docs: http://localhost:8000/docs
• Frontend UI: http://localhost:8080/

High-Level Workflow

1. A client submits an SSA scenario via POST /jobs (FastAPI).
2. The API stores the job in PostgreSQL and publishes a jobs.new event on Redis.
3. worker-conjunction subscribes to jobs.new, runs a simplified orbital conjunction analysis and writes results back to the database.
4. Synthetic sensor nodes (including a conceptual qemu-node) could send measurements to POST /measurements with an HMAC header.
5. The API validates the HMAC, writes measurements to the DB and updates tracks.
6. worker-tracking can perform asynchronous aggregation / future extensions.
7. Invalid HMAC or other security conditions trigger security.events on Redis, which are consumed and logged by security-monitor.
8. chaos-injector intentionally sends bogus or replayed telemetry to test detection and resilience.
9. The frontend polls /jobs, /tracks and /jobs/{id}/conjunctions and renders a simple operations dashboard.

Disclaimer

The platform is intentionally simplified:

• Orbital mechanics are approximate and for illustration only.
• Security mechanisms (HMAC, chaos injection) are minimal but show the idea.
• The goal is to demonstrate understanding of SSA concepts, distributed systems, containerisation, basic security monitoring and resilience patterns.