diff --git a/docs/my-website/docs/proxy/configs.md b/docs/my-website/docs/proxy/configs.md
index db737f75af..77b2153d78 100644
--- a/docs/my-website/docs/proxy/configs.md
+++ b/docs/my-website/docs/proxy/configs.md
@@ -626,6 +626,12 @@ Use this if you cannot mount a config file on your deployment service (example -
 
 LiteLLM Proxy will read your config.yaml from an s3 Bucket or GCS Bucket 
 
+:::info
+
+The config.yaml will be fetched from the S3 Bucket or GCS Bucket every 10 seconds. Keep this in mind as pricing may vary based on the number of requests or data transfer out of bucket.
+
+:::
+
 <Tabs>
 <TabItem value="gcs" label="GCS Bucket">
 
@@ -668,5 +674,20 @@ docker run --name litellm-proxy \
    -p 4000:4000 \
    ghcr.io/berriai/litellm-database:main-latest
 ```
+
+If you need to set the AWS credentials, the following env vars can be used:
+
+```shell
+AWS_ACCESS_KEY_ID
+AWS_SECRET_ACCESS_KEY
+AWS_SESSION_TOKEN
+AWS_REGION_NAME
+AWS_SESSION_NAME
+AWS_PROFILE_NAME
+AWS_ROLE_NAME
+AWS_WEB_IDENTITY_TOKEN
+AWS_STS_ENDPOINT
+```
+
 </TabItem>
 </Tabs>
diff --git a/docs/my-website/docs/proxy/team_logging.md b/docs/my-website/docs/proxy/team_logging.md
index 779a6516b4..9e54b16dfe 100644
--- a/docs/my-website/docs/proxy/team_logging.md
+++ b/docs/my-website/docs/proxy/team_logging.md
@@ -30,12 +30,14 @@ litellm_settings:
   default_team_settings: 
     - team_id: "dbe2f686-a686-4896-864a-4c3924458709"
       success_callback: ["langfuse"]
+      langfuse_host: os.environ/LANGFUSE_HOST
       langfuse_public_key: os.environ/LANGFUSE_PUB_KEY_1 # Project 1
       langfuse_secret: os.environ/LANGFUSE_PRIVATE_KEY_1 # Project 1
     - team_id: "06ed1e01-3fa7-4b9e-95bc-f2e59b74f3a8"
       success_callback: ["langfuse"]
+      langfuse_host: os.environ/LANGFUSE_HOST
       langfuse_public_key: os.environ/LANGFUSE_PUB_KEY_2 # Project 2
-      langfuse_secret: os.environ/LANGFUSE_SECRET_2 # Project 2
+      langfuse_secret: os.environ/LANGFUSE_PRIVATE_KEY_2 # Project 2
 ```
 
 Now, when you [generate keys](./virtual_keys.md) for this team-id 
@@ -49,6 +51,28 @@ curl -X POST 'http://0.0.0.0:4000/key/generate' \
 
 All requests made with these keys will log data to their team-specific logging. -->
 
+### Setting Team Logging via UI
+
+You can also achieve this via the UI, by setting the Team metadata to the following:
+
+```json
+{
+  "callback_settings": {
+    "callback_vars": {
+      "langfuse_host": "<your host>",
+      "langfuse_public_key": "os.environ/LANGFUSE_PUB_KEY_1",
+      "langfuse_secret_key": "os.environ/LANGFUSE_PRIVATE_KEY_1"
+    },
+    "failure_callback": [],
+    "success_callback": [
+      "langfuse"
+    ]
+  }
+}
+```
+
+Environment Variables can be used.
+
 ## [BETA] Team Logging via API 
 
 :::info