Ana içeriğe geç

Network Connection Matrix

This page provides detailed information about network connections and port requirements between Apinizer platform components. A port matrix is provided for Inbound, Outbound, and Internal traffic flows.

Network Traffic Categories​

Inbound Traffic

From External World

  • From Internet to Load Balancer
  • From Clients to API Gateway
Outbound Traffic

To External World

  • To Backend APIs
  • To External Services
  • To Internet
Internal Traffic

Between Components

  • Manager ↔ Worker
  • Manager → Integration
  • Worker ↔ Database
  • Worker ↔ Cache

Port Matrix - Detailed Table​

Inbound Traffic (Internet → Apinizer)​

SourceDestinationPortProtocolDescriptionRequired
InternetLoad Balancer443HTTPSAPI access (Production)Required
InternetLoad Balancer80HTTPHTTP → HTTPS redirectRequired
InternetLoad Balancer22SSHManagement access (recommended via VPN)Optional

Outbound Traffic (Apinizer → Internet)​

SourceDestinationPortProtocolDescriptionRequired
WorkerBackend API443HTTPSBackend API callsRequired
WorkerBackend API80HTTPHTTP Backend API callsOptional
WorkerExternal Services443HTTPSExternal service integrationsOptional
ManagerExternal Services443HTTPSMonitoring, webhooksOptional
ManagerSMTP Server25/587SMTPEmail sendingOptional
ManagerDNS Server53UDP/TCPDNS queriesRequired

Internal Traffic (Between Components)​

Manager ↔ Worker​

SourceDestinationPortProtocolDescriptionDirection
ManagerWorker8091 (HTTPS: 8443)HTTP/HTTPSDeployment operations (/apinizer/deployment/*)Manager → Worker
ManagerWorker8091 (HTTPS: 8443)HTTP/HTTPSHealth check and management (/apinizer/management/*)Manager → Worker

The Manager reaches the Worker at the Gateway Management API URL defined on the Environment (for example http://worker-management-api-http-service.<namespace>.svc.cluster.local:8091). The Worker does not open connections to the Manager.

Manager → Integration​

SourceDestinationPortProtocolDescriptionDirection
ManagerIntegration8092HTTPTask flow scheduling and execution (/api/integration/execute) and health check (/apinizer/management/health)Manager → Integration

The Manager reaches the Integration module at the API Integration (Task Flow) Module URL defined in the general settings (for example http://integration-http-service.<namespace>.svc.cluster.local:8092). Open this port only if you use task flows.

Worker ↔ Database (MongoDB)​

SourceDestinationPortProtocolDescriptionDirection
WorkerMongoDB25080TCPData read/writeWorker → MongoDB
ManagerMongoDB25080TCPConfiguration managementManager → MongoDB
IntegrationMongoDB25080TCPConfiguration read and Quartz job storeIntegration → MongoDB
MongoDBMongoDB25080TCPReplica set communicationMongoDB ↔ MongoDB

Worker ↔ Elasticsearch​

SourceDestinationPortProtocolDescriptionDirection
WorkerElasticsearch9200HTTPLog sendingWorker → Elasticsearch
ManagerElasticsearch9200HTTPAnalytics queriesManager → Elasticsearch
ElasticsearchElasticsearch9300TCPCluster communicationElasticsearch ↔ Elasticsearch

Worker ↔ Cache (Hazelcast)​

SourceDestinationPortProtocolDescriptionDirection
WorkerCache8090HTTPCache REST APIWorker → Cache
ManagerCache8090HTTPCache management (REST)Manager → Cache
CacheCache5701TCPCluster communicationCache ↔ Cache

Kubernetes Communication​

SourceDestinationPortProtocolDescriptionDirection
KubeletAPI Server6443HTTPSAPI accessKubelet → API Server
Kube-proxyAPI Server6443HTTPSAPI accessKube-proxy → API Server
PodPodDynamicTCP/UDPPod-to-Pod communicationPod ↔ Pod

Network Topology Based Port Requirements​

DMZ Zone Ports​

Worker Nodes:

  • 443/80: Client access (from Load Balancer)
  • 8091 / 8443: Gateway listener and deployment operations from Manager (Kubernetes NodePort: 30080 by default)
  • 8090: Cache REST API access (from LAN)
  • 25080: MongoDB access (from LAN)
  • 9200: Elasticsearch access (from LAN)

Load Balancer:

  • 443/80: Internet access
  • 8091 / 8443 (Kubernetes NodePort: 30080): Traffic routing to Workers

LAN Zone Ports​

Manager Module:

  • 8080: Web Manager and Management API
  • 25080: MongoDB access
  • 9200: Elasticsearch access
  • 8090: Cache access (REST)
  • 8092: Integration access (task flows)

Integration Module:

  • 8092: Task flow API (from Manager)
  • 25080: MongoDB access

MongoDB:

  • 25080: Database access (from Worker, Manager and Integration)

Elasticsearch:

  • 9200: HTTP API (from Worker and Manager)
  • 9300: Transport protocol (intra-cluster)

Cache (Hazelcast):

  • 8090: Cache REST API (from Worker and Manager)
  • 5701: Hazelcast cluster communication (between Cache nodes)

Firewall Rules Summary​

DMZ Firewall Rules​

Inbound:

Internet → Load Balancer: 443, 80
VPN → Load Balancer: 22 (optional)

Outbound:

Load Balancer → Worker: 8091 / 8443 (Kubernetes NodePort: 30080)
Worker → MongoDB: 25080
Worker → Elasticsearch: 9200
Worker → Cache: 8090
Worker → Backend API: 443, 80

LAN Firewall Rules​

Inbound:

DMZ → MongoDB: 25080
DMZ → Elasticsearch: 9200
DMZ → Cache: 8090
VPN → Manager: 22, 8080

Outbound:

Manager → Worker: 8091 / 8443
Manager → MongoDB: 25080
Manager → Elasticsearch: 9200
Manager → Cache: 8090
Manager → Integration: 8092
Manager → External Services: 443, 25, 587

Port Requirements - Component Based​

Worker Node Ports​

Client-Facing Ports
  • 443: HTTPS API access
  • 80: HTTP API access (for redirect)
  • 8091 / 8443: Gateway HTTP/HTTPS and Management API (from Manager)
Backend Communication Ports
  • 443/80: Backend API calls (outbound)
  • 25080: MongoDB access (outbound)
  • 9200: Elasticsearch log sending (outbound)
  • 8090: Cache access (outbound)
Internal Ports
  • 8091 / 8443: Communication with Manager (Manager → Worker)
  • Dynamic: Kubernetes service discovery

Manager Node Ports​

Web Interface Ports
  • 8080: Web Manager UI
  • 8080: Management API
Database Ports
  • 25080: MongoDB access (outbound)
  • 9200: Elasticsearch access (outbound)
  • 8090: Cache access (outbound)
  • 8092: Integration access (outbound, task flows)
External Service Ports
  • 443: External API calls (webhook, monitoring)
  • 25/587: SMTP (email sending)
  • 53: DNS queries

Network Security Best Practices​

Warning

Security Rules:

  1. Never expose MongoDB and Elasticsearch ports to the Internet
  2. Never expose Manager port (8080) to the Internet
  3. Always use TLS/SSL (in production)
  4. Always configure firewall rules with least privilege principle
  5. Always implement network segmentation (DMZ/LAN)

Port Opening Checklist​

  • Only necessary ports are opened
  • DMZ and LAN separation is implemented
  • Firewall rules are configured with least privilege principle
  • TLS/SSL certificates are configured
  • Network segmentation is implemented
  • Port scanning tests are performed
  • Monitoring and alerting are configured

Traffic Flow Diagram​

Internet
│
▼ (443/80)
┌──────────────┐
│Load Balancer │
└──────┬───────┘
│ (8091 / 30080)
▼
┌──────────────┐
│ Worker Node │
└──────┬───────┘
│
├───► (25080) MongoDB
├───► (9200) Elasticsearch
├───► (8090) Cache
└───► (443) Backend API
Note

Important: This port matrix is valid for standard installations. Port numbers may vary for custom configurations and custom port usage. Network security audit must be performed for production environments.