Verification and Access

On-prem Deployment Guide (AWS)

What Success Looks Like

Your deployment is complete when all of the following are verified:

• All VM containers show Up/healthy in docker ps

• Every endpoint tested in Step 2 returns a healthy response

• The Hivel UI loads at the address you access in Step 3

• At least one integration (Jira/GitHub/GitLab) is connected in the UI and shows data (check the next page to kick start your first integration).

Validation Checklist

Check	How to verify
Database connectivity	psql -h $DB_HOST -U <user> -d insightly connects from VM
Cache/queue (Redis)	docker exec -it insightly-redis redis-cli ping returns PONG
API readiness	curl http://localhost:80/health returns healthy on VM
UI access	UI loads at the address in Access Hivel Application with no console errors
Integration connectivity	Connected Jira/GitHub/GitLab shows a "connected" status inside the Hivel UI after sign up, see the next page on how to sign up and integrate.
First-data confirmation	Open the relevant dashboard in the Hivel UI for the integration you just connected (e.g. Jira/GitHub/GitLab) - records and metrics appearing there confirm data is flowing. This is the primary supported signal for on-prem/VPC deployments.

Step 1: Verify Services Are Running

On VM:

# Check all containers
docker ps

# Check service health
./deploy.sh --health

# Check specific service
./deploy.sh --health auth-svc

Expected result: All containers show Up/healthy status.

Step 2: Test Service Endpoints

On the VM, run each command and verify healthy responses:

# Test API Gateway
curl http://localhost:80/health

# Test Auth Service
curl http://localhost:8095/health

# Test Insightly Service
curl http://localhost:8082/hivelapi/health

# Test UI
curl http://localhost:3000

Step 3: Access Hivel Application

Choose one access method below based on your needs:

Option A: Direct EC2 IP (Quick testing only)

• No HTTPS; IP address changes if instance restarts without Elastic IP

• Web UI: http://<vm-public-ip>:3000

• API Gateway: http://<vm-public-ip>

Option B: Application Load Balancer (ALB)

• Stable access point; HTTPS not yet configured

1. Create ALB in AWS Console

2. Configure target group pointing to VM (ports 80, 3000)

3. Configure listener rules

4. Access via ALB DNS name

Option C: Route53 + ALB (Production recommended)

• Stable custom domain with HTTPS

1. Create ALB (as in Option B)

2. Create Route53 hosted zone for your domain

3. Create A record (alias) pointing to ALB

4. Configure SSL/TLS certificate in ALB for HTTPS

5. Access via: https://your-domain.com

Verify UI loads with no console errors.

Verify Data Integration.

Expected result: Connected integration shows "connected" status; data flows to the dashboard.

Troubleshooting

If any step fails, see Troubleshooting for help.

Back to Log Rotation Setup

Application Setup Guide