Skip to content

BDA + Knowledge Bases feature request for enterprise doc processing

0

We are building an enterprise intelligent document processing + RAG workflow on Amazon Bedrock. I am trying to sanity-check whether others will benefit from the following ideas:

BDA: choose the parsing model: Today BDA’s PDF to Markdown normalization feels fixed. For enterprise docs with scans, handwritten notes, dense tables, nested lists, fidelity is everything.

BDA: promptable parsing / output shaping: We need basic “instructions” during parsing, for example: drop headers/footers/page numbers/TOC pages, translate DE/FR to EN but preserve domain terms, product codes, formulas, convert charts/graphs into Markdown tables or concise text, enforce consistent terminology/formatting for regulatory terms.

Preserving structured: A big pain point is content that spans pages (tables continuing, headings separated from body, procedures split across pages). I would love an option to parse with overlapping page windows (e.g., 1–3, 3–5, 5–7) so a VLM can “see” structure across boundaries in one invocation. Anyone doing something equivalent today?

Configurable Knowledge Bases: For example, Cohere Embed v4: it is available via InvokeModel, but not selectable in KB creation as of today. Would be great to be able to configure a knowledge base with every possible configuration.

1 Answer
0

Your feature requests for Amazon Bedrock Data Automation (BDA) and Knowledge Bases highlight important considerations for enterprise document processing workflows.

Regarding BDA model selection, you're right that currently there are limited options. Amazon Bedrock offers three parsing strategies when creating a knowledge base: the Bedrock default parser (for text-only content), Bedrock Data Automation (BDA) for multimodal content, and the Foundation model parser for complex document structures. The Foundation model parser might address some of your concerns as it provides advanced parsing capabilities specifically designed for complex document structures, including PDFs with tables and visually rich content.

For promptable parsing and output shaping, the Foundation model parser does offer some customization options. When using this parser, you can customize the default prompt used for data extraction, which could potentially address some of your requirements like handling headers/footers or enforcing terminology consistency.

Regarding preserving structure across page boundaries, this is a known limitation in traditional RAG systems. When documents are divided into chunks, context can be lost between sections. Amazon Bedrock offers several chunking strategies that might help with this issue:

  1. Semantic chunking - This divides text into meaningful segments based on semantic similarity rather than arbitrary character counts, which helps preserve context and meaning.

  2. Hierarchical chunking - Particularly useful for complex documents with nested structures like technical documents or academic papers with complex formatting and nested tables.

For configurable Knowledge Bases, Amazon Bedrock does allow some customization through custom AWS Lambda functions. You can use these to customize the chunking process to align with your specific RAG application requirements.

Another approach worth considering is contextual retrieval, which adds explanatory context to each chunk before generating embeddings. This enriches the vector representation with relevant contextual information, enabling more accurate retrieval of semantically related content.

These features and approaches can help address some of your concerns, though not all of your specific feature requests are currently available in the service.
Sources
Revolutionizing drug data analysis using Amazon Bedrock multimodal RAG capabilities | Artificial Intelligence
Improve search results and accurate in Amazon Bedrock | AWS re:Post
Contextual retrieval in Anthropic using Amazon Bedrock Knowledge Bases | AWS Machine Learning Blog
Create a knowledge base for multimodal content - Amazon Bedrock

answered 5 days ago
AWS
SUPPORT ENGINEER
reviewed 3 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.