[Feature Request]: Commercial Cloud Deployment Example #129

New Issue

2026-02-16T01:15:54-05:00

yindo commented

2026-02-16 01:15:54 -05:00

Originally created by @brycecf on GitHub (Oct 24, 2024).

Features like AWS SQS support and #154 suggest the possibility of using llama-deploy in commercial clouds.

For developers whom are largely reliant on those services, an example of using llama-deploy on services in AWS, Azure, or (to a lesser extent) GCP would help provide more clarity on possible use cases.

At first glance, the Quick Start's configuration file looks like it could compete with IaC solutions like Terraform, which also complicates what a commercial cloud deployment would look like.

Originally created by @brycecf on GitHub (Oct 24, 2024). Features like AWS SQS support and #154 suggest the possibility of using `llama-deploy` in commercial clouds. For developers whom are largely reliant on those services, an example of using `llama-deploy` on services in AWS, Azure, or (to a lesser extent) GCP would help provide more clarity on possible use cases. At first glance, the Quick Start's configuration file looks like it could compete with IaC solutions like Terraform, which also complicates what a commercial cloud deployment would look like.

yindo added the enhancement example labels 2026-02-16 01:15:54 -05:00

yindo commented

2026-02-16 01:15:54 -05:00

@masci commented on GitHub (Oct 24, 2024):

Hey @brycecf thanks for the feedback, that's indeed something we should do, I'll set aside some time to work on it.

Regarding quick start configuration, that's not inteded to compete with IaC. While terraform code would dictate how to build the infrastructure powering the app, the deployment.yml file is meant to define the workflows that will run on top of that infra. Moreover, Llama Deploy is designed so that you can completely bypass the higer level (we call it API Server) with the relative configuration files and operate at the lower level (see Manual Orchestration in the docs).

Having a cloud deployment example will definitely make more clear these concepts, I'll figure something out!

@masci commented on GitHub (Oct 24, 2024): Hey @brycecf thanks for the feedback, that's indeed something we should do, I'll set aside some time to work on it. Regarding quick start configuration, that's not inteded to compete with IaC. While terraform code would dictate how to build the infrastructure powering the app, the deployment.yml file is meant to define the workflows that will run on top of that infra. Moreover, Llama Deploy is designed so that you can completely bypass the higer level (we call it [API Server](https://docs.llamaindex.ai/en/stable/module_guides/llama_deploy/)) with the relative configuration files and operate at the lower level (see [Manual Orchestration](https://docs.llamaindex.ai/en/stable/module_guides/llama_deploy/30_manual_orchestration/) in the docs). Having a cloud deployment example will definitely make more clear these concepts, I'll figure something out!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: run-llama/llama_deploy#129