Disk where /var is mounted should have 80GB as available disk space. ** All the Raga software is installed within this VM. After installation, only access to outside the VM, will be to LLMs (as per need) hosted on internal or external network.
Inbound Ports
Inbound port 22 (SSH)
Inbound port 80 (HTTP) (Needed only for initial setup)
Inbound port 443 (HTTPS) (If only HTTPS configuration is needed)
Outbound Ports
Outbound port 443 (HTTPS)
Outbound port 587 (SMTP)
Outbound port 80 (HTTP) (Needed only for initial setup)
Note: Close port 80 after Raga Catalyst installation
You must have an AWS account with 8 vCPUs available and Ec2 FullAccess in that region in the region where the instance will be created. The AWS user must have programmatic access.
Retrieve the PEM file raga-catalyst.pem from the current path. Copy the PEM file to another location as a precaution. If the PEM file is lost, you will not be able to SSH into the instances in the future
Save the security_group_id, as it will be required in the next steps.
Ensure you have a Google Cloud account with an active project.
Ensure you have a Google Cloud project with a sufficient quota to launch an instance with the t2a-standard-8 machine type (8 vCPUs and 32 GiB Memory).
Confirm the availability of the required resources (such as VPCs, subnets, and public IP addresses) in your chosen region. Use This Command
gcloudservicesenablecompute.googleapis.com
Alternatively, enable it via the Google Cloud Console: Navigate to APIs & Services > Library, search for "Compute Engine API," and click Enable. Navigate to APIs & Services > Library, search for "Compute Engine API," and click Enable:
The Gcloud user or service account used must have the following permissions:
Compute Admin: To create and manage instances, networks, and firewall rules.
Storage Admin: If additional storage operations are required.
Service Account User: To assign the service account to the instance.
Programmatic Access
Set up programmatic access using either gcloud auth or service account credentials.
Retrieve the PEM file raga_ssh_private_key.pem from the current path. Copy the PEM file to another location as a precaution. If the PEM file is lost, you will not be able to SSH into the instances in the future
Get the IP of the Instance
SSH into the instance:
ssh-iraga_ssh_private_key.pemubuntu@<VM-IP>
Install Raga Catalyst on VM
Install Raga Catalyst:
SSH into the instance and run the installation command.
If you face any issues accessing Raga Catalyst, run the command cat /var/log/ragastartup.log and share the output with the Raga team for quick assistance