I am trying to setup a custom Quick Chat Agent that is utilizing a custom created Space. We want the chat to be accessed via the embedded url generated from the API for users in different namespaces. When we attempt to use the chat in our website, it loads fine and I am able to select our custom agent, but the agent claims to not have access to our data.
Here is the response:
“I don’t have access to any [abc] data in our current conversation. To help you identify alarms with the longest duration, I would need:
Access to a dataset containing [abc] information
Files uploaded with [abc] data
A Space with relevant [abc] records
A Dashboard or Topic with [abc] metrics
Could you please share the [abc] data you’d like me to analyze? You can:
Upload a file (CSV, Excel, etc.) with [abc] data
Point me to a specific Space containing [abc] information
Share which Dashboard or Topic has the [abc] duration metrics”
Our custom space has the association to the “abc” data and works for users in our default namespace. But if we generate a url for a user in another namespace, we get the above conflict.
We have granted permissions for the users in the namepace for the chat agent, topic and dashboards, the problem is, we cannot set permissions for a user in another namespace for Spaces in any way. There’s nothing in the API or Console to set permissions for Spaces for users in different namespaces. What are our options?
UPDATE: I actually see this error in the “Response events”:
”Failed to fetch details of space arn:aws:quicksight:us-east-1:xxxxxxx:space/my-space-id with error code ACCESS_DENIED”
I Think the Core Issue here is Namespace Isolation and Space Permissions
here’s what’s happening:
Namespaces are designed for user isolation, not resource sharing. Quick namespaces ensure that “users in one namespace can’t see or interact with users in another namespace” . However, the documentation explicitly states: “Namespaces are useful for isolating users and permissions, but not for sharing assets. Dashboards, datasets, and analyses can be shared with users in different namespaces” .
The problem is that Spaces don’t currently support cross-namespace sharing through the UI or API. While you can share chat agents, topics, and dashboards across namespaces, there’s no mechanism as far as i know to grant Space permissions to users in different namespaces .
Your Options may be:
Keep all users in the same namespace - This is the most straightforward solution. Users within the same namespace can share Spaces normally.
Use alternative knowledge sources - Instead of Spaces, consider:
Linking the chat agent to Topics or Dashboards that can be shared across namespaces
Using Knowledge Bases (if they support cross-namespace access)
Uploading files directly to the chat agent as reference documents
Duplicate the Space in each namespace - Create identical Spaces in each namespace where users need access. This is manual but would work within the current architecture.
I may also reach out to customer support for feature request.
Just checking back in since we haven’t heard from you in a bit. Were you able to see Deep’s reply and/or find a solution yourself in the meantime? If you still have any additional questions related to your initial post, please feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.