Hello,
We are thinking to activate Pixel-Perfect Reports in quicksight. But I would like to be sure to not increase exponentially the cost of the service.
We want to send report by email to many users. As I understood I can create schedules for each report in the dashboard and share it with all the users shared in the dashboard. How will this be counted in the pricing?
1 for each email that we send to each memebr of each group that have access to the dashboard or 1 in total?
Also I would like to build a report that has many orders. The user need to dwonload all the information relative to 1 report (which I will build). how will this process be priced? 1 for each download or 1 in total?
Thank you
pixel-perfect reports are priced per report-unit, a report unit measures the sizeof the report being generated. One report unit is equivalent to 100 pages or 100MB in size.
The report consumes a report unit when it’s being generated and the consumption is not based on the number of recipients.
Please be aware of the fact that if your underlying dataset has a row-level security applied then for each recipient 1 report unit will be considered since the engine goes through determining their access to data and possibly the content of the report is different for each user.
I have RSL for many dataset that I want to share. what if I have group (with more people within the same group)? 1 report for each group or one for each person withtin the group?
Each email delivered will be counted as 1 report unit though all users in the group had the same RLS setting. This was our experience a couple of months back.
I suggest you pose this specific question with your case with AWS. It may otherwise be a costly affair.
@Giridhar.Prabhu from what @dnegre said, each group should count 1. since the people from the same group should receive the same report. and he is from AWS team….
I wonder if this sort of thing is showing up in AWS analysis of the uptake of this product. I have a strong hunch that one of the stronger potential features of QS is being hamstrung by the very un-AWS approach to pricing (i.e. higher fixed cost to start using, let alone no free tier, plus hard to predict actual usage). We would definitely try it, but not as a $500 a month gamble, potentially a lot more if we get it wrong.