fix: added instructions for AWS Bedrock API key setup
Browse files
README.md
CHANGED
|
@@ -17,13 +17,15 @@ This is the code repository for the DEval project "Durchführung und Unterstütz
|
|
| 17 |
## Get started
|
| 18 |
|
| 19 |
### Set up `.env` file
|
| 20 |
-
To run, the project expects secret keys from a `.env` file. Locally set up this `.env` file. You require connection to
|
| 21 |
|
| 22 |
Here how the `.env` file should look like:
|
| 23 |
|
| 24 |
```
|
| 25 |
# .env
|
| 26 |
-
|
|
|
|
|
|
|
| 27 |
|
| 28 |
# Langfuse credentials
|
| 29 |
LANGFUSE_PUBLIC_API_KEY= # Your Langfuse public API key
|
|
|
|
| 17 |
## Get started
|
| 18 |
|
| 19 |
### Set up `.env` file
|
| 20 |
+
To run, the project expects secret keys from a `.env` file. Locally set up this `.env` file. You require an `AWS_ACCESS_KEY_ID` and an `AWS_SECRET_ACCESS_KEY` to make connection to Amazon Bedrock LLMs and embedding models. Furthermore, API keys for the Langfuse integration are needed. The latter you can acquire after setting up a Langfuse project in the Langfuse GUI, either through a local setup or via Langfuse Cloud.
|
| 21 |
|
| 22 |
Here how the `.env` file should look like:
|
| 23 |
|
| 24 |
```
|
| 25 |
# .env
|
| 26 |
+
# AWS keys
|
| 27 |
+
AWS_ACCESS_KEY_ID= # Your AWS access key
|
| 28 |
+
AWS_SECRET_ACCESS_KEY= # Your AWS secret access key
|
| 29 |
|
| 30 |
# Langfuse credentials
|
| 31 |
LANGFUSE_PUBLIC_API_KEY= # Your Langfuse public API key
|