Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Quicksight Chat agent

0

I created a Space for AURA quicksight Dashboard named AURA Space. Then created a chatbot named AURA Chatbot. It accessed the Dashboard and gave me correct answers to the questions I asked. But today it is saying that it is not able to access the Dashboard. Below is the response from the Chatbot.

You're absolutely right to ask about this - nothing has changed on your end, and you don't need to do anything to give me access to the Dashboard. I apologize for the confusion in my previous response.

The issue is that my access to the AURA Dashboard query capabilities has become temporarily unavailable during our conversation. This is a technical limitation on my side, not something you can control or fix. When I provided you the Audio Ad Type data earlier, I had access to the dashboard querying functionality, but that access is currently not available to me.

What this means:

The AURA Dashboard and its data are still there and accessible My ability to query it directly has temporarily changed This is not something you caused or can fix from your end Your options:

Wait and try again later - My dashboard access may be restored Access the AURA Dashboard directly through your normal interface to get the Display Ad Type data Try refreshing our conversation - Sometimes starting a new conversation can restore access to capabilities I understand this is frustrating, especially since I was able to help you with the Audio data just moments ago. The technical infrastructure that allows me to access dashboards can sometimes have intermittent availability issues.

What's preventing access: The error indicates that the QuickSight querying service is temporarily failing for this specific request. This is different from not having access to the dashboard itself - I can see the AURA Dashboard is available and I successfully queried it earlier for Audio Ad Type data.

Technical details:

✅ Dashboard visibility: I can see the AURA Dashboard in the space

✅ Dashboard access: The dashboard is accessible and linkable

❌ Query execution: The QuickSight query service is experiencing intermittent failures for Display Ad Type requests

What this means: This appears to be a temporary service issue with the specific query execution, not a permissions or access problem. The same query mechanism that worked for Audio Ad Type data is currently failing for Display Ad Type data.

Topics
AnalyticsMachine Learning & AI
Tags
Amazon Quick SightChat Bots
Language
English

asked a year ago422 views

1 Answer
-1

When a QuickSight chatbot suddenly loses access to a dashboard it was previously able to query, there are several potential causes:

  1. Dashboard permissions may have changed. The chatbot needs specific permissions to access the dashboard. If these permissions were modified or revoked, the chatbot would lose access.

  2. Network policy issues could be preventing access. If you're using OpenSearch Serverless (which might be powering some of your dashboard data), you may need to check if "Access to OpenSearch Dashboards" is enabled in your network settings.

  3. Authentication tokens may have expired. The chatbot uses authentication credentials that can expire, requiring renewal.

  4. Dashboard sharing settings might have changed. If the dashboard was previously shared with the chatbot but the sharing configuration was altered, this would cause access issues.

To resolve this issue, you should:

  1. Check the dashboard permissions to ensure the chatbot still has the necessary access rights.

  2. Verify that any network policies are properly configured if your dashboard relies on OpenSearch.

  3. Try refreshing the session or restarting the chatbot as suggested.

  4. If you're an administrator, you might need to use the DescribeDashboardPermissions API operation to check the current permissions and update them if necessary.

The intermittent nature of the access suggests this could be a temporary authentication or service availability issue that might resolve on its own, but checking permissions would be a good first step.
Sources
Getting a 401 when trying to access OpenSearch serverless dashboard | AWS re:Post
DescribeDashboardPermissions - Amazon QuickSight

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content