Inference Public

AWS Quick guideChoosing your route

Build RAG, use Bedrock Managed Knowledge Base, or adopt AWS Quick?

Three AWS routes to AI over your own documents compared: custom RAG, Amazon Bedrock Managed Knowledge Base and AWS Quick, and which suits which need.

A team sketching a system design on a whiteboard

A public body that wants AI to answer from its own documents has three broad routes on AWS:

These are different levels of infrastructure and responsibility, and they can be combined. AWS supports linking a Bedrock Managed Knowledge Base into Quick in specified regions only, and that list currently does not include London. Verify that integration for your deployment region before designing around it.

The choice has become more pressing because AWS has changed its product line during 2026:

Existing customers of all of these remain supported. New designs face a narrower set of options.

This article explains the routes, where they differ, and how to choose between them. It builds on our article on treating RAG as a data product. Whichever route you take, the quality and safety of answers depend on the content behind them and on the controls around them.

The three routes

1. Build and operate retrieval yourself

There are two variants, with different constraints.

It gives the most control and carries the most engineering and operational responsibility. - A customer-managed Bedrock knowledge base. Bedrock provides ingestion and retrieval functions, while you choose and run a supported vector store. Applications can use Retrieve and RetrieveAndGenerate. Note the connector restriction above if your content is in SharePoint or Confluence.

2. Amazon Bedrock Managed Knowledge Base

AWS launched the managed service on 17 June 2026, and it is available in London. AWS runs:

The service supports native and custom connectors. Check availability, permission behaviour, authentication and region for each source you need.

It still involves design choices. At creation you either accept the service-managed embedding model (the default) or choose your own Bedrock embedding model, and you configure parsing, chunking, retrieval settings and metadata. Two choices have lasting consequences:

Applications query it with Retrieve, or with AgenticRetrieveStream for multi-step retrieval, with a generated answer and citations by default (the answer can be turned off). The API reference states that RetrieveAndGenerate is not supported for managed knowledge bases. It can also be exposed to agents through AgentCore Gateway.

AWS's documentation recommends the managed option for its combination of ease of use, accuracy and cost. That is AWS's own positioning, not an independent evaluation.

3. AWS Quick

AWS Quick is a workspace for licensed staff. It brings together:

Its own knowledge bases cover SharePoint, OneDrive, Confluence, S3 and other sources. Organisations configure Quick rather than build it, and pay per user plus an account fee.

Diagram: content owners feed one governance process; an internal permission-controlled collection feeds a custom pipeline, a Bedrock Managed Knowledge Base and AWS Quick; a separate public approval gate feeds a public collection and public-facing application
Figure 1. Shared content governance, separate internal and public collections, and three retrieval routes. The internal collection is a logical, governed content set: each route may keep its own index, copies and permission behaviour. The Quick integration with Bedrock Managed Knowledge Base is optional and region-dependent. Open full-size figure

How the routes compare

Fully custom pipelineCustomer-managed Bedrock KBBedrock Managed KBAWS Quick
LayerWhole stackRetrieval capability on your vector storeManaged retrieval capabilityStaff workspace
You buildEverythingVector store operation, application, interface, authenticationApplication, interface, authentication, actionsConfiguration, knowledge bases, guidance
Typical usersWhoever your application servesWhoever your application servesWhoever your application servesLicensed staff
Vector storeAnyA supported store you choose and operateAWS-operatedQuick's own; a Bedrock Managed KB only in supported regions (not London at present)
Parsing, chunking, metadataFull controlConfigurable within Bedrock's optionsConfigurable within the managed service's options; embedding type fixed at creationLimited
Retrieval APIsYour ownRetrieve, RetrieveAndGenerateRetrieve, AgenticRetrieveStream (generated answer by default); not RetrieveAndGenerateBuilt in
Who authenticates usersYour applicationYour applicationYour application; the service filters by the identity you passQuick, through the account's configured identity method
Document permissionsYou design themYou design them (for example metadata filters)ACL-aware filtering for supported connectors; behaviour varies by connectorEnforced for supported knowledge bases; real-time checks for some connectors
AgentsYou build themYou build themNative AgentCore Gateway targetChat agents, Flows, Automate
Main cost elementsInfrastructure, models, operationsVector store, models, operationsIndexed data and retrieval charges, plus models, gateways and logging where usedPer-user subscriptions, account fee, usage above allowances
SkillsEngineering, operations, data stewardship, evaluationEngineering, data stewardship, evaluationApplication engineering, data stewardship, evaluationAdministration, identity, information governance, evaluation

The table shows the principal delivery work for each route. Real timescales depend on identity integration, DPIA screening, source remediation, procurement, accessibility and evaluation, more than on the technology.

Who checks who the user is

Permissions are where the routes differ most, and where public-sector risk concentrates.

Bedrock Managed Knowledge Base filters on an identity your application supplies. AWS describes its document-level access control as ACL-aware filtering, not a security boundary. The service does not authenticate users: your application must authenticate them and pass a verified identity. Users are matched by email, which must match the email in each source exactly. Behaviour also varies by connector:

Where a knowledge base combines sources with and without permissions, content from the sources without permissions may be returned to any caller.

AWS Quick authenticates licensed staff through the account's configured identity method. It then enforces document permissions for supported knowledge bases, with real-time checks for some connectors. That covers retrieval. Exports, downstream actions and files uploaded directly into Spaces need their own controls. Our AWS Quick FAQ covers these, along with the account-level decisions that cannot be changed later.

In a custom pipeline or customer-managed knowledge base, you design access control yourself. The data product approach linked above describes the pattern:

Which route suits which need

Staff need answers from documents they already hold

Consider AWS Quick and Microsoft 365 Copilot side by side.

Copilot deserves equal consideration for staff who work mainly in Microsoft 365, particularly where the organisation already uses Microsoft Graph, Purview and the Office applications. Its connectors and agents can extend beyond Microsoft 365. Quick may suit organisations with an AWS relationship, knowledge across several systems, or a need for its research, reporting or automation features.

Compare the two on:

See our use cases for councils, central government and health.

A service needs to answer the public, or to sit inside a business process

Usually an application you build, backed by managed or customer-managed retrieval.

Examples:

These need:

Quick is principally a licensed workplace environment. AWS documents public Quick Apps, but they are available only on Free and Plus accounts, and cannot use connectors, embedded chat or Spaces. That rules them out as a basis for a citizen-facing service grounded in departmental source systems.

You need control the managed services do not give

A customer-managed knowledge base or a fully custom pipeline.

This applies when you need:

Check the connector restriction first. The trade-off is engineering and operational effort, which public bodies often underestimate.

Staff and the public rely on overlapping guidance

Share the governance, and keep the collections separate.

Where staff and the public depend on overlapping guidance, share the process that establishes what is authoritative, current and suitable for each audience:

An internal assistant can then retrieve from a permission-controlled collection, while a public service retrieves from a separately approved public collection.

A common managed knowledge base can sometimes serve several authenticated applications, but only where identity, authorisation, content admission and information boundaries have been designed and tested. Connecting a Bedrock Managed Knowledge Base to Quick also requires the integration to be supported in your region. At present that means US East (N. Virginia), US West (Oregon), Europe (Ireland) and Asia Pacific (Sydney), with up to two managed knowledge bases per Quick instance in the same region. London is not listed.

What every route still needs

The route decides who builds and runs the machinery. It does not decide whether answers are right or whether the service is accountable. Every route needs:

If you are moving from Amazon Kendra or Amazon Q Business

Treat the move as a new deployment:

Questions to settle before choosing

  1. Users. Who are they: staff, the public, or both?
  2. Destination. Where does an answer go: to a person who checks it, into a workflow, or straight to a member of the public?
  3. Authority. Who authenticates users, who enforces permissions, and who authorises actions?
  4. Content. Where is it, and are those systems supported with the permission behaviour you need, in your region?
  5. Control. How much do you need over parsing, metadata, withdrawal and evidence?
  6. Capacity. Can you operate what you build for years, rather than just build it?
  7. Cost. How will it scale across subscriptions, storage and retrieval, including combined Quick and Bedrock charges?

How Inference Public can help

Before recommending a route, Inference Public looks at the information, security, integration and operating requirements involved. If we are engaged to implement a particular AWS product, the scope and commercial arrangements are made explicit.

If you choose AWS Quick, our AWS Quick Readiness, Implementation & Assurance service covers the decisions and testing involved, and what public bodies need to check before switching on AWS Quick sets them out in order.

If your concern is the state of your content more broadly, our AI-ready data assessment looks at documents, metadata and permissions for any AI assistant.


Further reading

Bedrock Managed Knowledge Base GA (17 June 2026)

Managed versus customer-managed knowledge bases

Create a managed knowledge base (connectors and embedding model)

RetrieveAndGenerate API reference

RetrieveAndGenerateStream API reference

AgentCore Gateway managed KB target

Managed KB ACL support

Managed KB ACL query behaviour

Quick BYO Bedrock KB limitations

Quick BYO Bedrock KB billing

Bedrock pricing

Customer-managed KB connector restriction (30 September 2026)

Kendra availability change

Amazon Q Business document history

Quick public Apps

Microsoft 365 Copilot privacy and connectors

ICO, FOI and AI

NCSC, prompt injection is not SQL injection

Managed knowledge base regions

AWS service availability changes (June 2026)

ICO, right of access

All insights

Start a conversation

Let’s talk about what you need to build.

Bring the service, the constraint or the engineering question. We’ll work through a sensible starting point.

Discuss a project