URLs lose "https://" prefix in Amazon Q output within Quick Suite Flows

Q&A
,
1

Issue

When using Amazon Q in QuickSight (Quick Suite) Flows, URLs in the AI-generated output lose their https:// prefix.

For example, a dataset field contains image URLs like:

https://example.com/media/image123.webp

But when Amazon Q outputs this URL (e.g., in a Chat Agent step or General Knowledge step), the result becomes:

example.com/media/image123.webp

This breaks Markdown image rendering (![alt](url)) because the URL is no longer absolute.

Steps to Reproduce

  1. Create a Quick Suite Flow
  2. Add a QuickSight Output step that retrieves data containing URLs with https:// prefix
  3. In a subsequent Chat Agent or General Knowledge step, reference the output and ask Amazon Q to include the URLs in its response
  4. The URLs in the output will have their https:// stripped

What I’ve Tried

  • Adding explicit instructions in the prompt: “Always include https:// in URLs” — does not work
  • Adding URL preservation instructions in the QuickSight Output step — does not work
  • The dashboard data correctly shows https:// prefix, so the issue occurs during AI output generation

Expected Behavior

URLs should be output exactly as they appear in the source data, preserving the https:// protocol prefix.

Environment

  • Region: us-west-2
  • Feature: Quick Suite Flows (Amazon Q in QuickSight)
2

Hi @sho_miyahara,

Welcome to the Quick Community! I remember another user faced a similar issue, discussed in this post here. For this issue as well, I think if you play with the wording of the instructions, such as saying “for every output concatenate “https://” at the very beginning and list them out for me.” Keep trying prompts like that or different variations to see if you can get different behavior.

Hope this helps!

3

Hi @sho_miyahara

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

4

Hi @sho_miyahara

Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.

Thank you!