Topline Docs

Data

Bedrock knowledge-base source

Create or attach an AWS-backed source, inspect ingestion, and distinguish deleting managed resources from detaching a reference.

Bedrock knowledge-base source

Create or attach an AWS-backed source, inspect ingestion, and distinguish deleting managed resources from detaching a reference.

Where to find it

Open Account > Data Sources, choose the connector when adding a source, or open its saved source detail.

Choose the right knowledge-base workflow

Choose Knowledge Base when adding a Data Source for an AWS Bedrock-backed web or S3 collection. This is different from Topline Knowledge Bases, which have Content, Quality, Connections, and reviewed releases. A source connector does not itself publish a Topline collection release.

Create or connect

Enter Source name. Expand Advanced source details for Short name, Description, and AWS region; a blank region uses the configured platform default. Choose Setup mode:

  • Create knowledge base: configure content and choose Create knowledge base to submit. Creation starts provider ingestion; inspect its progress on source detail.
  • Connect existing knowledge base: enter Knowledge base ID and choose Connect knowledge base. This records a local ready reference. Attachment alone does not start new ingestion or certify provider access/connectivity.

Under Data source, choose Web crawler or S3 bucket. For Web crawler, enter Seed URLs, one per line, optional Sitemap URLs, Crawl depth, Crawl scope, and applicable include/exclude patterns. Start with a bounded site scope. For S3 bucket, enter Bucket name, optional 12-digit Bucket owner account ID for cross-account content, Prefixes, and applicable object patterns. Review the shown access preview/checklist before submission.

Inspect and operate the source

On source detail, inspect the knowledge-base state and ingestion status. Refresh reloads status; it does not start ingestion. Sync now is available for eligible created-mode configurations with both knowledge-base and data-source IDs. An external attachment does not gain the same created-resource sync controls.

Resolve the displayed provider setup or access error through the account's authorized administrator. A local ready reference is not a successful retrieval or complete ingestion check.

Delete versus detach

For a created source with its provider service configured, Delete knowledge base deletes the managed AWS data source and knowledge base. For an existing external attachment, Detach knowledge base removes the Topline attachment without deleting the provider's base. The handler detaches locally when provider deletion is unavailable; inspect the reported outcome rather than assuming an AWS deletion.

Both successful paths archive the local source and configuration. Ordinary Restore source does not recreate AWS resources that were deleted. Review dependencies and the confirmation before choosing either action, and reconcile an uncertain provider outcome before retrying.