Azure Marketplace Deployment
Last updated
Last updated
This guide walks you through deploying LightBeam from the Azure Marketplace after purchase.
This includes filing out some basic profile information to submit to Microsoft to install the application.
Visit the
Click "Get it Now" and complete the profile information
Select "LightBeam Software Package" plan and click "Create"
Subscription: Select your Azure subscription
Resource Group: Choose existing or create new (must be empty)
Region: Select Azure region for deployment
VM Name: Name for your JumpVM
Size: Choose from supported sizes:
Standard_DS1_v2
Standard_DS2_v2
Standard_DS3_v2
Standard_B1s
Username: JumpVM login username
Authentication: Choose SSH Public Key or Password
Access IP: Specify allowed IP range in CIDR format:
Corporate network: e.g., 10.0.0.0/16
Single user: your IP with /32 (e.g., 203.0.113.1/32)
Avoid using 0.0.0.0/0 for production environments
LightBeam Version: Software version to deploy
Network: Choose new or existing Azure VNET (/16) and Subnet (/20)
AKS Cluster Name: Default or custom name
Node Pool VM Size: Choose from supported sizes:
Standard_D8s_v3
Complete the configuration, review, and click "Create".
Deployment takes approximately 40 minutes.
After the LightBeam cluster is installed, use the below instructions to access the LightBeam Web Interface.
Find JumpVM's public IP in Azure Portal
SSH into JumpVM:
# For password authentication:
ssh username@public_IP
# For SSH key authentication:
chmod 400 your_key_file
ssh -i your_key_file username@public_IP
Switch to root on JumpVM:
sudo su
Get the web UI address:
kubectl get ingress -n lightbeam -o jsonpath='{.items[0].status.loadBalancer.ingress[0].ip}' && echo
Retrieve admin password:
kubectl exec deploy/lightbeam-api-gateway -- printenv 2>/dev/null | grep AUTH_PASSWORD | awk -F= '{print $2}'
Access LightBeam at http://<obtained_IP> using:
Username: admin
Password: <retrieved_password>
Connect to JumpVM as described above and check these log files:
Main handler log:
cat /var/log/azure/custom-script/handler.log
This is the primary log file for the Azure VM extension that runs custom scripts during deployment. It records overall extension execution status, including when scripts start and finish, and any high-level errors.
Deployment stdout/stderr:
cat /var/lib/waagent/custom-script/download/0/stdout
cat /var/lib/waagent/custom-script/download/0/stderr
These files contain the actual console output from the deployment scripts:
stdout shows the normal output of commands that ran successfully
stderr captures error messages and warnings from failed commands
These logs provide detailed information about what specific commands were executed and their results during the initial setup process.
Terraform and AKS deployment logs:
cat /root/lightbeam/lightbeam-tf-iac/aks/terraform_apply.log
This log specifically focuses on the infrastructure deployment stage using Terraform. It shows:
AKS (Azure Kubernetes Service) cluster creation
Node pool configuration and deployment
LightBeam application deployment logs:
cat /root/lightbeam/lightbeam-chart/lightbeam_install.log
This final log shows the deployment of the actual LightBeam application into the Kubernetes cluster.
Connect to JumpVM and switch to root:
sudo su
Clean up LightBeam cluster:
cd /root/lightbeam/lightbeam-chart
./installer/lb-cleanup
Remove AKS infrastructure:
cd /root/lightbeam/lightbeam-tf-iac/aks
export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
terraform destroy
Type "yes" when prompted and wait for completion
Complete cleanup:
Delete all resources from the Azure Resource Group
Remove JumpVM role assignments (Network Contributor and AKS Service Contributor)
Node Count: Number of nodes (contact for sizing recommendations)
Setup Token: Obtain from after purchase
License Key: Obtain from after purchase
