Several dashboards repeat the same aggregate within a short period.
When the result is still fresh, reuse the S3 result rather than paying for another scan.
Which approach is most appropriate?
Configure Athena query result reuse with an explicit freshness period, workgroup scope, and result-access policy.
Detailed explanation
Object retention rules do not decide Athena result reuse.
Object retention rules do not decide Athena result reuse.
Deleting results prevents reuse and increases scan cost and latency.
Deleting results prevents reuse and increases scan cost and latency.
Audit logs do not store SQL results.
Audit logs do not store SQL results.
The same query can reuse a result within its validity period and avoid another scan.
The same query can reuse a result within its validity period and avoid another scan.
Check official documentation
Compare the following points with the official documentation.
Amazon Athena query result reuse、workgroup、result locationの公式説明を確認する。
What to confirm
結果再利用とS3 Lifecycle・監査ログの役割を区別できる。
Key points
- Query result reuse
- Freshness
- Workgroup
- Scan reduction
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Reuse conditions
Query text, catalog state, source changes, and parameters affect whether reuse is safe.
Information control
Result S3 encryption, permissions, and retention must match data classification.