Athena scan and Glue execution costs are beginning to exceed the budget.
Attribute cost per unit of work to services and teams.
Which analysis approach is most appropriate?
Combine Cost Explorer, Budgets, cost-allocation tags, and technical usage metrics to calculate unit cost and identify spikes.
Detailed explanation
API count does not equal Athena bytes scanned or Glue compute time.
API count does not equal Athena bytes scanned or Glue compute time.
A total alone does not support early detection or root-cause attribution.
A total alone does not support early detection or root-cause attribution.
Deleting evidence can hide the cause and may violate audit or replay requirements.
Deleting evidence can hide the cause and may violate audit or replay requirements.
Billing data and technical volume identify which service or team drove the increase.
Billing data and technical volume identify which service or team drove the increase.
Check official documentation
Compare the following points with the official documentation.
AWS Cost Explorer、AWS Budgets、cost allocation tags、Athena/Glue pricingの公式説明を確認する。
What to confirm
請求総額だけでなく処理量あたりのコストを分析する方法を説明できる。
Key points
- Cost Explorer
- Budgets
- Cost allocation tag
- Unit cost
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Cost model
Separate scan, compute, storage, transfer, and log-ingestion components.
Optimization loop
Partitioning, columnar formats, reuse, and incremental processing lower cost without hiding quality issues.