Enable Simple Knowledge Base Creation for Internal Wiki (w.amazon.com) Without Complex Authentication Setup

Description:

I would like to request a feature that allows non-technical users to easily create Knowledge Bases from frequently-updated internal wikis (w.amazon.com) without requiring complex XPath configuration or AWS CDK deployment.

Current Problem:

The My Assistant chat agent can access internal wiki content using DataSource, which works seamlessly without any authentication setup. However, when users try to create their own Custom Chat Agents or Spaces that reference the same internal wiki content, they face significant technical barriers:

  • Web Crawler requires XPath configuration for SAML authentication, but internal wikis use automatic SSO (no login form exists)

  • Alternative solutions like MindSync CDK require extensive AWS permissions and technical expertise

  • Spaces cannot directly reference wiki URLs

Requested Feature:

Provide the same seamless internal wiki access that My Assistant has to user-created Custom Chat Agents and Spaces. Specifically:

  • Allow users to add internal wiki URLs (w.amazon.com) as Knowledge Base sources without XPath configuration

  • Leverage the existing DataSource authentication mechanism that My Assistant uses

  • Enable automatic synchronization to keep Knowledge Base content up-to-date with wiki changes

Use Case:

Creating Slack chatbots that reference frequently-updated team wikis is a common need across Amazon. This feature would enable non-technical users to build these solutions without IT assistance, significantly improving productivity and reducing support burden.

Business Impact:

This is a high-demand use case that would benefit many teams across Amazon. The technical capability already exists (as demonstrated by My Assistant’s DataSource access), so extending this to user-created agents would provide immediate value to a large user base.

Hi @yhikone ,

That is an interesting situation that you’re experiencing with the differing behaviors of the default chat agent and a custom agent when interacting your internal wiki. Unfortunately, I do not have access to your internal wiki to try and test this out. With that said, I will leave the ‘feature-request’ tag attached to this post to help increase visibility to the Quick team.