Skip to main content
Version: Next

Configure Halo EC2 instance

## Health Check

  • Once the EC2 instance is launched and started, Give 15 minutes for the instance to start the Halo services.
  • Visit https://<ip-address> from a browser to access Glasswall Halo portal. This is a health check to make sure services are up and running.
  • Halo APIs can be accessed using the Swagger portal at https://<ip-address>/swagger/index.html
  • You are now ready to use the Glasswall Halo Portal and API.

## License Management

## Troubleshooting

Halo Portal and the API is not accessible, What should I do?​

  • If you receive timeout errors, make sure the instance security groups are allowing the inbound ports you are accessing.
  • For any other errors, ssh to the instance using the username glasswall and private key selected during the creation of the instance.
  • Run below commands and verify all pods are running.
kubectl get pods

The number of engine pods are not running as expected​

The cloud-init config present in the machine, runs a shell script to configure the number of engine pods running based on the CPU cores available on the VM. For some reason, if the cloud-init script does not complete within expected time, run the below commands so the VM will retry

sudo cloud-init clean
sudo reboot now