Embedded QuickChat service account cannot access Space memory/context that interactive users can

Q&A
,
1

Hi team,

I have a registered user (pre_registered_agent_service_user) created as a dedicated service account for generating embedded URLs via GenerateEmbedUrlForRegisteredUser for a
QuickChat agent. All internal users access the chat agent through this embedded experience.

When users interact with the agent directly through QuickSight, I’ve noticed they all seem to share access to the memory/context of the associated Space. For example, if
User A tells the chat agent to remember the definition of a term, the agent can later provide the correct definition to User B. This suggests the knowledge is tied to the
Space rather than individual user memory.

However, this does not work when users ask the same questions via the embedded QuickChat agent. The dedicated service account I created for embedding appears to not have
proper access to this shared memory/context.

What I’ve verified:

  • The service account has access to the Space and Topics linked to the agent
  • It can successfully run queries against the Topics and return dataset results
  • The service account is ADMIN_PRO, Active, and in the same groups as interactive users

What doesn’t work:

  • Definitions and domain knowledge that interactive users can access through the Space’s memory/context are not available to the embedded service account
  • I cannot find where to validate or grant permissions for this Space-level memory/context

Questions:

  1. Where is the Space memory/context stored, and how can I verify that my service account has proper access to it?
  2. Is there a permission layer beyond Space membership that controls access to this shared knowledge?
  3. Does a user created via register-user API (that has never logged in interactively) have any limitations accessing Space memory/context compared to users who log in
    through the console?

Any guidance would be appreciated. Thanks

2

Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!