Building a Serverless Amazon QuickSight Dashboard Distribution Solution

Overview

Business dashboards are only valuable when they reach the right stakeholders at the right time. Amazon QuickSight simplifies this with its email scheduling feature, allowing dashboards to be delivered directly to registered QuickSight users. However, organizations often encounter two challenges as report distribution scales: licensing costs and operational overhead.

In many cases, the audience for a daily or weekly dashboard extends far beyond users who actively access QuickSight. Purchasing Reader licenses solely for email delivery is unnecessary, while manually forwarding reports every day is inefficient and error-prone.

This blog explores a serverless AWS solution that automates QuickSight report distribution. Instead of registering every recipient as a QuickSight user, the solution schedules reports to a small set of QuickSight users, retrieves the emailed report using IMAP, performs optional validation or preprocessing, and redistributes it through Amazon SES to a broader audience.

The Challenge

Amazon QuickSight’s scheduled email reports are sent only to registered QuickSight users. While this works well for analysts and dashboard owners, organizations often need to distribute the same report to project teams, business stakeholders, external partners, or management who do not require direct access to QuickSight.

The common alternatives have drawbacks:

• Purchasing Reader licenses for every recipient increases recurring costs.
• Manually forwarding dashboard emails consumes valuable time.
• Managing recipient lists across multiple dashboards becomes cumbersome.
• There is no opportunity to validate or customize reports before distribution.

A more scalable approach is to separate report generation from report distribution.

Solution Overview

The automation workflow leverages several AWS services together with a dedicated mailbox.

1. Amazon QuickSight generates the scheduled dashboard report and emails it to a registered QuickSight account.
2. An AWS Lambda function connects to the mailbox using IMAP.
3. The latest QuickSight email is identified based on sender, subject, and report date.
4. The PDF attachment is extracted and temporarily stored.
5. Business validations or preprocessing are performed on the report.
6. If validation succeeds, the report is redistributed using Amazon Simple Email Service (SES) to the required recipients.

This architecture allows a single scheduled report to reach hundreds of recipients without requiring every user to be licensed in QuickSight.

Architecture Flow

The solution follows a straightforward serverless workflow:

Amazon QuickSight
→ Scheduled Dashboard Email

↓

Dedicated Email Inbox

↓

AWS Lambda

• Retrieve email using IMAP
• Extract PDF attachment
• Validate report
• Perform preprocessing

↓

Amazon SES

↓

Business Users

Because the workflow is entirely event-driven and serverless, there are no servers to manage, and operational maintenance remains minimal.

Implementation Details

The automation is implemented using three primary Python modules.

1. Report Extraction

The first module establishes a secure IMAP connection to the mailbox that receives scheduled QuickSight reports.

Rather than processing every email, the automation filters messages using multiple criteria:

• Sender address
• Subject line
• Current report date

This ensures only the latest dashboard report is processed.

Once the correct email is identified, the Lambda function extracts the PDF attachment and stores it in temporary storage for downstream processing.

Using AWS Secrets Manager to securely retrieve the mailbox password eliminates the need to hardcode credentials inside the application.

2. Report Validation and Preprocessing

Before redistributing the report, the solution performs validation to ensure only meaningful dashboards are shared.

Using PyMuPDF, the PDF contents are parsed to extract key business metrics.

In this implementation, the automation verifies:

• Training statistics are successfully extracted.
• Values in the dashboard summary match the corresponding totals within the report.
• Today’s training numbers are greater than or equal to the previous day’s values.

The previous day’s metrics are stored in Amazon S3 as a lightweight JSON file, allowing the Lambda function to compare successive reports without maintaining a database.

If any validation fails, the report is skipped, preventing incorrect or stale dashboards from being distributed.

This validation layer is one of the biggest advantages over native QuickSight scheduling, where reports are sent immediately without business-specific quality checks.

3. Automated Email Distribution

Once validation succeeds, the report is redistributed using Amazon SES.

The automation constructs a professional HTML email, attaches the validated PDF, and sends it to the configured recipient list.

Since Amazon SES handles email delivery, the recipient list can easily scale from a handful of users to hundreds without changing the core workflow.

Additionally, the email body can be customized independently of the original QuickSight email, allowing organizations to include project-specific instructions, disclaimers, or branding.

Benefits of the Solution

This architecture provides several operational and financial advantages.

Reduced QuickSight Licensing Costs

Only a limited number of users require QuickSight Reader access to receive scheduled reports. All additional recipients receive the dashboard through SES without needing QuickSight licenses.

Eliminates Manual Forwarding

The entire workflow—from report retrieval to redistribution—is automated, removing repetitive daily tasks.

Business-Aware Validation

Reports are distributed only after passing predefined validation rules, reducing the risk of sharing incomplete or inconsistent information.

Customizable Distribution

Because SES generates a new email, organizations can modify the email template, recipient groups, attachment names, or include additional documents before delivery.

Scalable Architecture

The same automation can support multiple dashboards simply by updating the filtering logic or recipient configuration, making it suitable for enterprise reporting environments.

Security Considerations

The solution follows AWS security best practices:

• Email credentials are stored securely in AWS Secrets Manager.
• Temporary report files exist only during Lambda execution.
• Amazon SES controls outbound email delivery.
• Amazon S3 stores only lightweight validation metadata rather than sensitive report content.

The entire workflow operates within managed AWS services, minimizing infrastructure management while maintaining security.

Conclusion

By combining QuickSight with AWS Lambda, IMAP, Amazon S3, AWS Secrets Manager, and Amazon SES, organizations can build an intelligent report distribution pipeline that extends well beyond native scheduling capabilities.

This approach not only reduces QuickSight Reader licensing costs but also introduces validation, customization, and automated redistribution into the reporting process. The result is a scalable, serverless solution that delivers trusted dashboards to the right audience while significantly reducing manual effort and operational overhead.