Amazon Bedrock Knowledge Bases is designed specifically for managed retrieval-augmented generation. A knowledge base connects source repositories to an embedding model and vector store. During ingestion, source content is transformed into numerical vector embeddings. At retrieval time, the query is similarly represented so the knowledge base can compare semantic similarity and return passages that are conceptually relevant rather than depending exclusively on exact keyword matches.

Amazon Bedrock supports managed data-source connectors for multiple repositories. The AWS documentation lists Amazon S3, Confluence, Microsoft SharePoint, Salesforce, web crawling, and custom data sources among supported connection patterns. These connectors reduce the amount of ingestion, crawling, and synchronization code an organization needs to maintain.

For Atlassian Confluence specifically, Bedrock can crawl supported Confluence content and supports incremental synchronization for added, modified, or deleted material. Current managed Confluence integration also supports crawling pages, blog posts, and attachments, subject to the documented connector limitations.

This architecture supplies the retrieval layer needed to augment an FM with source-grounded context. It centralizes retrieval semantics while letting the application use Bedrock ' s managed ingestion and retrieval capabilities instead of implementing its own embedding pipelines.

B explicitly uses keyword-oriented mappings and therefore does not meet the semantic-search requirement. C could technically implement RAG, but Lambda-based embedding generation, synchronization, and custom retrieval logic create precisely the operational burden the company wants to avoid. D is not an appropriate semantic RAG architecture because ordinary DynamoDB queries do not automatically produce vector-based semantic retrieval from unstructured documentation.

For an internal wiki not covered by a built-in connector, the knowledge-base custom data-source capability can be used while keeping the overall retrieval interface centralized. Therefore, A provides the closest fit to every stated architectural requirement.

==========