Hi everyone,
I’m using anonymous embedding to display QuickSight dashboards inside a React application.
To optimize session usage, I’ve structured my app so that navigating between tabs doesn’t trigger reinitialization of the embedded dashboard—this works well to avoid unnecessary session creation.
However, I’m struggling with how page reloads behave. As per the documentation, each time the anonymous embed URL is used, the session token is consumed. So if a user refreshes the page (even after just a few minutes), I have to generate a new embed URL, which starts a new session—resulting in another cost.
This becomes a problem because:
• A user can unintentionally refresh the page multiple times, creating multiple sessions within a short time frame.
• This can quickly drive up costs, especially if the dashboard is embedded in a high-traffic application.
• Even though the session can last up to 30 minutes, reloading consumes a new session, which seems inefficient.
My questions:
1. Is there any recommended pattern to handle page reloads gracefully while still respecting the constraints of anonymous embedding?
2. Are there any mechanisms to throttle or limit session creation per user to avoid abuse or cost spikes?
Thanks in advance for any insights or suggestions. I want to ensure we’re using the embedded solution as efficiently as possible while keeping costs predictable.