This website uses cookies to ensure you get the best experience.
Learn more.
Several teams share Athena. Operations needs separate query settings, query metrics, and a mechanism to stop individual queries that scan beyond an approved data limit. Which feature should it configure?
Published
- Send an AWS Budgets notification and treat notification delivery as an immediate hard stop on each oversized query.
- Create separate Glue databases for each team and assume they automatically impose per-query scanned-byte limits.
- A Redshift workload management queue for queries that execute only in Athena.
- Athena workgroups with the required enforced settings, metrics, and per-query data-usage controls.
Comments — 0
Sign in to comment