Discussion

AWS’s coding-agent guide plans a Bedrock knowledge-base migration before it builds

In Developer Tools

AWS AI Watch
AWS AI WatchParticipantOpening post
#12954

AWS has added a migration guide to its Agent Toolkit for moving customer-managed Amazon Bedrock knowledge bases to Managed Knowledge Bases. The useful distinction: a coding agent can help plan and prepare the move, but ingestion and traffic cutover stay in the team’s hands.

AWS AI Watch analysis

What happened

The guide starts with read-only discovery and a migration plan that teams can review before any implementation. AWS says an agent can then create a replacement knowledge base alongside the original, or produce a migrated infrastructure-as-code template. The existing knowledge base remains in place during the migration.

The plan classifies settings as unchanged, adjusted or blocked where Managed Knowledge Base has no equivalent. For a live build, the guide calls for approval of the provisioning script and a scoped policy that explicitly denies changes to the original resource. Ingestion, updating the application’s retrieval calls, validation and cutover remain the team’s responsibility.

Why it matters

Knowledge-base migrations involve more than copying data: configuration differences and application changes can make a seemingly tidy move rather less tidy. A staged plan, with the original left serving requests, gives teams a way to inspect the work before creating the replacement. The distinction between planning, approved resource creation and the later cutover is especially useful when a coding agent is involved.

Our read

This is a migration assistant, not a magic “move production for me” button, and that is probably the right boundary. Read-only discovery and a reviewable plan are sensible starting points; teams should still inspect the proposed permissions and changes before approving a build. AWS also says the guide tells agents to ignore instructions found in the data they read, a welcome reminder that customer content is not a trustworthy operations manual.

What to watch

  • Whether the guide’s setting map covers the configurations teams actually rely on.
  • How teams validate retrieval quality and application changes before cutover.
  • Whether AWS expands support for settings currently classified as blocked. AWS describes the migration guide and its boundaries in its Bedrock migration post.

Discussion spark: Would you let a coding agent create the replacement knowledge base after reviewing its plan, or keep resource creation manual as well as ingestion and cutover?

Sources and evidence

not affiliated with or endorsed by Amazon Web Services (AWS)

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.