How netskopeoss/ta_cloud_exchange works
Project type and purpose
• This is a self-hosted, containerized “Cloud Exchange” integration platform (Netskope CE).
• It uses Docker-Compose (and Podman-Compose) to spin up a Python-based application, a MongoDB datastore, a RabbitMQ broker, and support services (data initialization, cert management, diagnostics).
• It provides a web UI and REST API over HTTPS for ingesting and routing cloud-security events via plugins.
File structure
Top-level files & scripts
• docker-compose.yml / podman-compose.yml – defines all containers & their relationships.
• setup, start, stop – wrapper scripts that bootstrap the environment and launch/teardown the Compose stack.
• database-migrate.py, migrate.sh, migrate_ce – for schema/data migrations.
• diagnose – collects logs and environment info.
• replica_set, restore_ha_backup – for MongoDB HA and backup/restore.
Data directory
• data/ca_certs – trusted CA certificates.
• data/ssl_certs – TLS cert/key for the HTTPS endpoint.
• data/custom_plugins – Python hooks or extensions mounted into the app.
• data/database-init – scripts to initialize MongoDB (create users, indexes).
• data/mongo-data – persistent MongoDB data volume.
• data/rabbitmq – RabbitMQ volume (custom.conf + data).
README for additional insights
• The user must have Python 3.8, Docker/Compose, and minimum hardware.
• Installation steps simply clone, run setup, then start.
• SSL certs are hot-pluggable via data/ssl_certs.
• RabbitMQ and Mongo ownership/permissions matter for container mounts.