-
Notifications
You must be signed in to change notification settings - Fork 6
GCP Vertext AI #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
GCP Vertext AI #219
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
162 changes: 162 additions & 0 deletions
162
docs/tutorials/deploying-openai-apps-aws-bedrock-gcp-vertex.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,162 @@ | ||
--- | ||
title: Deploying your OpenAI Application to AWS Bedrock or GCP Vertex AI | ||
sidebar_position: 50 | ||
--- | ||
|
||
# Deploying your OpenAI Application to AWS Bedrock or GCP Vertex AI | ||
|
||
Let's assume you have an app that uses an OpenAI client library and you want to deploy it to the cloud, either on **AWS Bedrock** or **GCP Vertex AI**. | ||
|
||
This tutorial shows you how **Defang** makes it easy. | ||
|
||
Suppose you start with a compose file like this: | ||
|
||
```yaml | ||
services: | ||
app: | ||
build: | ||
context: . | ||
ports: | ||
- 3000:3000 | ||
environment: | ||
OPENAI_API_KEY: | ||
healthcheck: | ||
test: ["CMD", "curl", "-f", "http://localhost:3000/"] | ||
``` | ||
|
||
--- | ||
|
||
## Add an LLM Service to Your Compose File | ||
|
||
You need to add a new service that acts as a proxy between your app and the backend LLM provider (Bedrock or Vertex). | ||
|
||
Add **Defang's openai-access-gateway** service: | ||
|
||
```diff | ||
+ llm: | ||
+ image: defangio/openai-access-gateway | ||
+ x-defang-llm: true | ||
+ ports: | ||
+ - target: 80 | ||
+ published: 80 | ||
+ mode: host | ||
+ environment: | ||
+ - OPENAI_API_KEY | ||
+ - GCP_PROJECT_ID | ||
+ - GCP_REGION | ||
nullfunc marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
``` | ||
|
||
### Notes: | ||
|
||
- The container image is based on [aws-samples/bedrock-access-gateway](https://github.com/aws-samples/bedrock-access-gateway), with enhancements. | ||
- `x-defang-llm: true` signals to **Defang** that this service should be configured to use target platform AI services. | ||
- New environment variables: | ||
- `GCP_PROJECT_ID` and `GCP_REGION` are needed if using **Vertex AI**. (e.g.` GCP_PROJECT_ID` = my-project-456789 and `GCP_REGION` = us-central1) | ||
|
||
:::tip | ||
**OpenAI Key** | ||
|
||
You no longer need your original OpenAI API Key. | ||
We recommend generating a random secret for authentication with the gateway: | ||
|
||
```bash | ||
defang config set OPENAI_API_KEY --random | ||
``` | ||
::: | ||
|
||
--- | ||
|
||
## Redirect Application Traffic | ||
|
||
Modify your `app` service to send API calls to the `openai-access-gateway`: | ||
|
||
```diff | ||
services: | ||
app: | ||
ports: | ||
- 3000:3000 | ||
environment: | ||
OPENAI_API_KEY: | ||
+ OPENAI_BASE_URL: "http://llm/api/v1" | ||
healthcheck: | ||
test: ["CMD", "curl", "-f", "http://localhost:3000/"] | ||
``` | ||
|
||
Now, all OpenAI traffic will route through your gateway service. | ||
nullfunc marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
--- | ||
|
||
## Selecting a Model | ||
|
||
You should configure your application to specify the model you want to use. | ||
|
||
```diff | ||
services: | ||
app: | ||
ports: | ||
- 3000:3000 | ||
environment: | ||
OPENAI_API_KEY: | ||
OPENAI_BASE_URL: "http://llm/api/v1" | ||
+ MODEL: "anthropic.claude-3-sonnet-20240229-v1:0" # for Bedrock | ||
+ # MODEL: "google/gemini-2.5-pro-preview-03-25" # for Vertex AI | ||
healthcheck: | ||
test: ["CMD", "curl", "-f", "http://localhost:3000/"] | ||
``` | ||
|
||
Choose the correct `MODEL` depending on which cloud provider you are using. | ||
|
||
:::info | ||
**Choosing the Right Model** | ||
|
||
- For **AWS Bedrock**, use a Bedrock model ID (e.g., `anthropic.claude-3-sonnet-20240229-v1:0`). | ||
- For **GCP Vertex AI**, use a full model path (e.g., `google/gemini-2.5-pro-preview-03-25`). | ||
[See available Vertex models here.](https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/call-vertex-using-openai-library#client-setup) | ||
nullfunc marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
# Complete Example Compose File | ||
|
||
```yaml | ||
services: | ||
app: | ||
build: | ||
context: . | ||
ports: | ||
- 3000:3000 | ||
environment: | ||
OPENAI_API_KEY: | ||
OPENAI_BASE_URL: "http://llm/api/v1" | ||
MODEL: "anthropic.claude-3-sonnet-20240229-v1:0" # or your Vertex AI model path | ||
healthcheck: | ||
test: ["CMD", "curl", "-f", "http://localhost:3000/"] | ||
|
||
llm: | ||
image: defangio/openai-access-gateway | ||
x-defang-llm: true | ||
ports: | ||
- target: 80 | ||
published: 80 | ||
mode: host | ||
environment: | ||
- OPENAI_API_KEY | ||
- GCP_PROJECT_ID # required if using Vertex AI | ||
- GCP_REGION # required if using Vertex AI | ||
``` | ||
|
||
--- | ||
|
||
# Environment Variable Matrix | ||
|
||
| Variable | AWS Bedrock | GCP Vertex AI | | ||
|--------------------|-------------|---------------| | ||
| `GCP_PROJECT_ID` | _(not used)_| Required | | ||
| `GCP_REGION` | _(not used)_| Required | | ||
| `MODEL` | Bedrock model ID | Vertex model path | | ||
|
||
--- | ||
|
||
You now have a single app that can: | ||
|
||
- Talk to **AWS Bedrock** or **GCP Vertex AI** | ||
- Use the same OpenAI-compatible client code | ||
- Easily switch cloud providers by changing a few environment variables | ||
|
This file was deleted.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.