Build RAG applications with LlamaIndex on a Google Cloud C4A virtual machine
Introduction
Learn about LlamaIndex and Google Cloud C4A for RAG applications
Configure Google Cloud firewall rules for LlamaIndex
Create a Google Cloud C4A virtual machine for LlamaIndex
Install and configure LlamaIndex on a Google Cloud C4A virtual machine
Build and test a browser-based RAG application with LlamaIndex
Next Steps
Build RAG applications with LlamaIndex on a Google Cloud C4A virtual machine
Introduction
Learn about LlamaIndex and Google Cloud C4A for RAG applications
Configure Google Cloud firewall rules for LlamaIndex
Create a Google Cloud C4A virtual machine for LlamaIndex
Install and configure LlamaIndex on a Google Cloud C4A virtual machine
Build and test a browser-based RAG application with LlamaIndex
Next Steps
Who is this for?
This is an introductory topic for DevOps engineers, AI engineers, machine learning engineers, and software developers who want to build retrieval-augmented generation (RAG) applications using LlamaIndex on SUSE Linux Enterprise Server (SLES) Arm64, integrate vector databases, and query custom documents using local large language models (LLMs).
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Install and configure LlamaIndex on Google Cloud C4A Axion processors for Arm64.
- Build indexing and retrieval pipelines using LlamaIndex.
- Integrate ChromaDB vector databases with local LLMs using Ollama.
- Build and test a browser-based RAG application using FastAPI.
Prerequisites
Before starting, you will need the following:
- A Google Cloud Platform (GCP) account with billing enabled
- Basic familiarity with Python, as well as AI and LLM concepts
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
8000. After you create the rule, verify that it applies to the VM’s VPC network, then open http://<VM-EXTERNAL-IP>:8000 after the app starts.c4a-standard-4, which provides four vCPUs and 16 GB of memory.8000 is active. After confirming, open http://<VM-EXTERNAL-IP>:8000 again.