Documentation
PolicyCortex System Requirements for Multi-Cloud Environments
Before installing or integrating PolicyCortex, ensure your system and cloud environments meet the following minimum requirements. This ensures optimal performance, reliable data collection, and smooth compliance operations.
PolicyCortex Docs: Quick Start, Installation & System Requirements
Core Platform Requirements
- • Node.js >= 18.x
- • NPM or Yarn package manager
- • PostgreSQL >= 14.x
- • Redis (for caching and background tasks)
- • Docker (optional but recommended for containerized deployments)
Check Node and Postgres Versionsbash
# Verify Node.js version
node -v
# Verify PostgreSQL version
psql --version
# Optional: verify Docker installation
docker --versionCloud Environment Requirements
PolicyCortex integrates directly with your cloud infrastructure. Ensure you have proper permissions and configurations for your preferred providers.
AWS
- • IAM Role with read-only permissions
- • Access to CloudTrail, S3, EC2, IAM, and KMS APIs
- • Enabled CloudWatch metrics for event tracking
- • Cross-account role with external ID support
GCP / Azure / OCI
- • Service account with Viewer and Security Reviewer roles
- • Access to resource configuration APIs
- • Audit logging enabled in each project/subscription
- • Network access to PolicyCortex data collectors
Network and Security Requirements
- • Outbound HTTPS access (port 443)
- • Allowlist PolicyCortex API endpoint: api.policycortex.io
- • TLS 1.2 or higher required
- • WebSocket connections enabled (for real-time policy updates)
- • Firewall rules allowing internal agent communication
Example Firewall Rulebash
# Example UFW configuration for Ubuntu
sudo ufw allow out 443/tcp
sudo ufw allow from 10.0.0.0/8 to any port 443 proto tcp
sudo ufw reloadOptional Enhancements
Monitoring
- • Prometheus / Grafana integration
- • Audit log streaming to CloudWatch / Stackdriver
- • Real-time alert hooks for Slack or Teams
Performance
- • 4 CPU cores and 8GB RAM recommended
- • SSD-based storage for faster scans
- • Network latency under 200ms to API endpoint