I am deploying dashboards via definition. The dashboards contain images. How can I have these images visible when the dashboards are deployed to higher/client environments.
Hi @alltej
Upload images to an S3 bucket configured for public read access (or use pre-signed URLs for added security). To ensure images remain visible when deploying Quick dashboards via definition, store the images externally in Amazon S3 and reference them via public or secure URLs in the dashboard definition’s custom content visuals or image components.
Please refer to the following documentation this might be helpful for you.
@Xclipse Thank you for your response! For the built-in images that are readily available by quicksight, can those just be made available by the quicksight service itself or by quicksight cloudfront so content/dashboard developers did not even have to think about this components when the dashboards are deployed to the target environment?
When deploying dashboards via template this does not seem to be a problem. The images are visible. Is there a way to do the same for definition deployment without the heavy-lifting of provisioning S3 buckets and cloudfront services?
Hi @alltej
Quick’s built in images (like default icons, shapes, or pre-loaded assets in visuals) are handled internally by the service and remain available across deployments without additional setup, as they reference Quick hosted resources rather than external URLs.
Custom images added via Add → Image or custom content visuals do not auto persist in definition based deployments (CreateDashboard with DashboardDefinition API). Unlike templates, which resolve assets at runtime, definitions embed explicit URLs direct uploads (<1 MB) may fail across accounts, requiring S3/CloudFront references for reliability.
The images are not custom images. They are the built-in images. So I am really hoping that deploying via template or via definition should not make a difference from the users end. I think definition should still handle it.
Hi @alltej
Quick’s built-in images, such as default icons, shapes, and pre-loaded visual assets, are service managed and persist seamlessly.
Hi @alltej,
Just checking back in since we haven’t heard from you in a bit. Were you able to see Xclipse’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.
Thank you!
Hi @alltej,
Since we haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.
Thanks!