From b4e12fb8fd6f5fd60563b9f228257dc5315fbff7 Mon Sep 17 00:00:00 2001 From: ishaan-jaff Date: Thu, 7 Mar 2024 21:01:28 -0800 Subject: [PATCH] (docs) litellm cloud formation stack --- docs/my-website/docs/proxy/deploy.md | 43 +++++++++++++++++++++++++++- 1 file changed, 42 insertions(+), 1 deletion(-) diff --git a/docs/my-website/docs/proxy/deploy.md b/docs/my-website/docs/proxy/deploy.md index 8ffc2adf5..6de8625d0 100644 --- a/docs/my-website/docs/proxy/deploy.md +++ b/docs/my-website/docs/proxy/deploy.md @@ -218,8 +218,49 @@ Provide an ssl certificate when starting litellm proxy server ## Platform-specific Guide - + + + +### AWS Cloud Formation Stack +LiteLLM AWS Cloudformation Stack - **Get the best LiteLLM AutoScaling Policy and Provision the DB for LiteLLM Proxy** + +This will provision: +- LiteLLMServer - EC2 Instance +- LiteLLMServerAutoScalingGroup +- LiteLLMServerScalingPolicy (autoscaling policy) +- LiteLLMDB - RDS::DBInstance + +#### Using AWS Cloud Formation Stack +**LiteLLM Cloudformation stack is located [here - litellm.yaml](https://github.com/BerriAI/litellm/blob/main/enterprise/cloudformation_stack/litellm.yaml)** + +#### 1. Create the CloudFormation Stack: +In the AWS Management Console, navigate to the CloudFormation service, and click on "Create Stack." + +On the "Create Stack" page, select "Upload a template file" and choose the litellm.yaml file + +Now monitor the stack was created successfully. + +#### 2. Get the Database URL: +Once the stack is created, get the DatabaseURL of the Database resource, copy this value + +#### 3. Connect to the EC2 Instance and deploy litellm on the EC2 container +From the EC2 console, connect to the instance created by the stack (e.g., using SSH). + +Run the following command, replacing with the value you copied in step 2 + +```shell +docker run --name litellm-proxy \ + -e DATABASE_URL= \ + -p 4000:4000 \ + ghcr.io/berriai/litellm-database:main-latest +``` + +#### 4. Access the Application: + +Once the container is running, you can access the application by going to `http://:4000` in your browser. + + ### Deploy on Google Cloud Run