Cost
You are responsible for the cost of the AWS services used while
running this solution. The total cost for running this solution
depends on the amount of data ingested, stored, and processed, the
amount of data scanned by Amazon Athena queries, and the number of
Amazon QuickSight readers and authors, along with their access time
to dashboards. We recommend creating a
budget
through
AWS Cost Explorer
The following tables are example cost breakdowns for running this solution in the US East (N. Virginia) Region (excludes free tier). Prices are subject to change. For full details, refer to the pricing page for each AWS service used in this solution.
Example 1: Turn on QuickSight without GitHub
AWS service | Dimensions/Month | Cost/Month [USD] |
---|---|---|
Amazon Athena | 100 queries, 10 GB data scanned per query | ~$5.00 |
Amazon Kinesis Data Firehose | 100 GB | ~$2.90 |
Amazon Simple Storage Service (Amazon S3) | 100 GB | ~$2.30 |
Amazon QuickSight | 1 author, 10 readers, access 2 times per month for each reader | ~$24.00 |
Amazon CloudWatch Metric Streams | 3,000,000 metric updates. $0.003 per 1,000 metric updates | ~$9.00 |
AWS Lambda | 128 MB: 12 functions, total of 1M invocations and average 500 millisecond duration per Lambda run | ~$1.05 |
Total: | ~$44.25 |
Example 2: Turn on QuickSight, GitHub with Secrets Manager
AWS service | Dimensions/Month | Cost/Month [USD] |
---|---|---|
Amazon Athena | 100 queries, 10 GB data scanned per query | ~$5.00 |
Amazon Kinesis Data Firehose | 100 GB | ~$2.90 |
Amazon Simple Storage Service (Amazon S3) | 100 GB | ~$2.30 |
Amazon QuickSight | 1 author, 10 readers, access 2 times per month for each reader | ~$24.00 |
Amazon CloudWatch Metric Streams | 3,000,000 metric updates. $0.003 per 1,000 metric updates | ~$9.00 |
AWS Lambda | 128 MB: 12 functions, total of 1M invocations and average 500 millisecond duration per Lambda run | ~$1.05 |
Amazon API Gateway | 1 million requests | ~$1.00 |
AWS Secrets Manager | 1 secret, 1 million API calls | ~$5.40 |
Total: | ~$50.65 |
Note
This solution implements data partition and parquet data storage for performance
optimization and cost reduction. When running your own queries, we recommend that you use
the created_at
(timestamp) partition key. For more information, refer to Performance
tuning in Athena