How yaya2devops/gopencti works
Main Components
• Cloud/Infrastructure Layer: Represent the Azure VM hosting the platform. Include network/firewall considerations (as specified with the port rules for Portainer, OpenCTI, SSH, HTTPS, etc.).
• Container Management & Orchestration: Show Docker Engine deployment, Docker Swarm initialization, and Portainer as the web interface for managing Docker stacks.
• Core Service Containers:
• OpenCTI: The main application container (running on port 8080) that provides the user interface and business logic.
• Worker: Multiple instances (replicated) responsible for running background tasks and asynchronous processing.
• Supporting or Data Layer Containers:
• Redis: Caching and message queuing service.
• Elasticsearch: Provides full-text search and indexing capabilities.
• MinIO: Object storage engine for files and attachments.
• RabbitMQ: Message broker for orchestrating asynchronous communication.
• Connector Containers: Various import/export connectors (like connector-import-document, connector-export-file-stix, connector-export-file-csv, connector-export-file-txt, and others for MITRE and Cybercrime Tracker). They integrate by communicating with the OpenCTI instance to either import data or export content in specific formats.
Component Relationships and Data Flows
• Infrastructure Layer: External clients (administrators/users) access the Azure VM via defined ports (e.g., 8080 for OpenCTI and 9900 for Portainer).
• Orchestration framework (Docker Swarm) that ties these components together, and indicate that Portainer is used for deployment and management.
Architectural Patterns and Technologies
• Containerization and Microservices: Emphasize separation of concerns among discrete containers, each handling specific tasks (application logic, caching, search, messaging, storage, connectors).
• Configuration and Environment Management: Note that environment variables (captured in the opencti.env file) are critical for secure, dynamic configuration of each container.
• Infrastructure as Code: The presence of Docker Compose YAML files and GitHub workflows (.github/workflows) indicates that deployment and CI/CD automation are part of the overall system design.