Network Requirements
Configure the following network rules for your deployment. Apply Azure rules to your VM's Network Security Groups and AWS rules as outbound connections from your VM to Hivel's AWS account.
Direction
Port/Destination
Purpose
Inbound
22
Used for secure remote access to the server via SSH.
Inbound
80
API Gateway
Inbound
5432
Database access from application server only (no public or external access permitted)
Inbound
3000
Hivel UI (only for direct-IP or ALB access)
Inbound
4317
Required only while integrating Claude Code.
Outbound
443
Pull Hivel's Docker images from AWS ECR
Outbound (optional)
Your Jira/GitHub/GitLab instance
Integration connectivity
Proxy Configuration Outbound traffic to Hivel's container registry (ECR) can route through a standard corporate proxy without additional configuration on Hivel's side. If your organization requires outbound traffic to other destinations (package repositories, Jira/GitHub/GitLab instances) to route through a proxy, contact your Hivel representative to confirm support before finalizing firewall rules.
Last updated