mirror of
https://github.com/LibreChat-AI/librechat.ai.git
synced 2026-03-27 10:48:32 +07:00
🪨 docs: Update 'Upload to Provider' docs for AWS Bedrock Support (#512)
* docs: update upload to provider docs with bedrock support * docs: update for other file formats
This commit is contained in:
@@ -22,6 +22,7 @@ There are 8 main fields under `fileConfig`:
|
||||
|
||||
- At the time of writing, the Assistants endpoint [supports filetypes from this list](https://platform.openai.com/docs/assistants/tools/file-search#supported-files).
|
||||
- OpenAI, Azure OpenAI, Google, and Custom endpoints support files through the [RAG API.](../../rag_api.mdx)
|
||||
- OpenAI, Azure OpenAI, Anthropic, Google, and AWS Bedrock endpoints support direct file uploads via [Upload to Provider](/docs/features/ocr#5-upload-files-to-provider-direct).
|
||||
- The `ocr`, `text`, and `stt` sections control file processing for features like [Upload as Text](/docs/features/upload_as_text) and [OCR](/docs/features/ocr)
|
||||
- Any other endpoints not mentioned, like Plugins, do not support file uploads (yet).
|
||||
- The Assistants endpoint has a defined endpoint value of `assistants`. All other endpoints use the defined value `default`
|
||||
@@ -32,6 +33,7 @@ There are 8 main fields under `fileConfig`:
|
||||
- `openAI`
|
||||
- `azureOpenAI`
|
||||
- `google`
|
||||
- `bedrock`
|
||||
- `YourCustomEndpointName`
|
||||
- You can omit values, in which case, the app will use the default values as defined per endpoint type listed below.
|
||||
- LibreChat counts 1 megabyte as follows: `1 x 1024 x 1024`
|
||||
|
||||
@@ -98,6 +98,18 @@ For the full guide on creating profiles, configuring LibreChat, setting up loggi
|
||||
|
||||
For the YAML field reference, see **[AWS Bedrock Object Structure](/docs/configuration/librechat_yaml/object_structure/aws_bedrock#inferenceprofiles)**.
|
||||
|
||||
## Document Uploads
|
||||
|
||||
Bedrock supports uploading documents directly to the provider via the `Upload to Provider` option in the file attachment dropdown menu. Documents are sent to the Bedrock Converse API as native document attachments.
|
||||
|
||||
**Supported formats:** PDF, CSV, DOC, DOCX, XLS, XLSX, HTML, TXT, and Markdown (.md)
|
||||
|
||||
**Limitations:**
|
||||
- Maximum file size per document: **4.5 MB**
|
||||
- File names are automatically sanitized to conform to Bedrock's naming requirements (alphanumeric, spaces, hyphens, parentheses, square brackets; max 200 characters)
|
||||
|
||||
For more information on file upload options, see the [OCR for Documents](/docs/features/ocr#5-upload-files-to-provider-direct) documentation.
|
||||
|
||||
## Notes
|
||||
|
||||
- The following models are not supported due to lack of streaming capability:
|
||||
|
||||
@@ -169,10 +169,10 @@ Support for custom OCR providers and user-defined strategies is planned for futu
|
||||
|
||||
### 5. Upload Files to Provider (Direct)
|
||||
|
||||
For supported LLM Providers (**OpenAI, AzureOpenAI, Anthropic, and Google**) and their respective models, files can now be sent directly to the provider APIs as message attachments,
|
||||
For supported LLM Providers (**OpenAI, AzureOpenAI, Anthropic, Google, and AWS Bedrock**) and their respective models, files can now be sent directly to the provider APIs as message attachments,
|
||||
allowing the provider to use their own native OCR implementations to parse files using the `Upload to Provider` option in the file attachment dropdown menu.
|
||||
|
||||
Currently all four of the aforementioned providers offer support for images and PDFs, with Google also including support for audio and video files when used in conjunction with compatible multimodal models.
|
||||
Currently all five of the aforementioned providers offer support for images and PDFs, with Google also including support for audio and video files when used in conjunction with compatible multimodal models. AWS Bedrock additionally supports CSV, DOC, DOCX, XLS, XLSX, HTML, TXT, and Markdown documents.
|
||||
|
||||
<Callout type="note" title="Azure OpenAI PDF Upload Caveat" emoji='✏️'>
|
||||
For **Azure OpenAI** endpoints, the Upload to Provider option for PDF files is only available when using the Responses API. Azure OpenAI's Chat Completions API supports images but does not support PDF file attachments.
|
||||
@@ -182,6 +182,17 @@ If you do not see 'Upload to Provider' as an option for PDFs in your chat's atta
|
||||
Note: Standard OpenAI endpoints support PDF uploads in both Chat Completions and Responses APIs.
|
||||
</Callout>
|
||||
|
||||
<Callout type="note" title="AWS Bedrock Document Upload Limits" emoji='🪨'>
|
||||
**AWS Bedrock** supports document uploads via the Converse API for the following formats:
|
||||
**PDF, CSV, DOC, DOCX, XLS, XLSX, HTML, TXT, and Markdown (.md)**
|
||||
|
||||
Constraints:
|
||||
- Maximum file size per document: **4.5 MB**
|
||||
- File names are sanitized to conform to Bedrock's naming requirements (alphanumeric, spaces, hyphens, parentheses, square brackets; max 200 characters)
|
||||
|
||||
For more details on Bedrock configuration, see the [AWS Bedrock setup guide](/docs/configuration/pre_configured_ai/bedrock).
|
||||
</Callout>
|
||||
|
||||
## Detailed Configuration
|
||||
|
||||
For additional, detailed configuration options, see the [OCR Config Object Structure](/docs/configuration/librechat_yaml/object_structure/ocr).
|
||||
|
||||
Reference in New Issue
Block a user