Increase External Image Timeout for Scheduled Snapshots

Q&A
, , , ,
1

Hi everyone,

I’m having a frustrating issue with scheduled email reports and hoping AWS can help. We have a dashboard with about 20 images served through CloudFront URLs (4 tables total), and here’s what’s happening:

  • When I open the dashboard in my browser, all images load perfectly within a few seconds

  • When the scheduled snapshot runs in the morning, it usually captures 0-1 images

  • If I manually view the dashboard first, then the next scheduled snapshot captures all the images that loaded

I’ve been doing a workaround where I schedule two snapshots a few minutes apart (the first one “primes” the images for the second), but this is not ideal or scalable.

It really seems like the snapshot renderer gives up on loading external images way faster than a regular browser does. The images aren’t slow - they load fine when I’m actually using the dashboard.

This is for a POC we need to launch soon. Would love to see AWS either increase the timeout for external resources during snapshot generation, or give us a setting to configure how long it waits?

Anyone else run into this? Any other workarounds besides the double snapshot thing?

Thanks!

2

Hi @caraf,

While I’ve had trouble finding documentation around this; I agree it sounds like a timeout issue but it doesn’t look like there’s a way for users to configure this.
As another work around to test out; what if you stored the images in a public S3 bucket? This may speed up the load times in your instance.

I noticed you created a similar post to this as well and noted that you had created a support ticket. There may be a way that AWS can configure your load time to account for this, which would be handled by connecting with the support team.

1 Like
3

Hi @caraf,

Following up here as it’s been awhile since last communication took place on this thread; did you have any additional questions regarding your initial post?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you

4

Hi @caraf,

Since we have not heard back further, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community.

Thank you!