Amazon Athena Workgroup
Does ZopNight manage Amazon Athena Workgroup?
Amazon Athena bills per TB of data scanned by each query, with a 10 MB minimum per query. The table's layout, not the result size, sets the cost. ZopNight attributes query spend per workgroup from Cost Explorer or CUR 2.0 and recommends scan-efficiency fixes and workgroup data limits.
Rules that fire on Amazon Athena Workgroup
No active rule family targets Amazon Athena Workgroup today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery, cost tracking, and recommendations only. |
Amazon Athena runs serverless SQL over data in S3, billed per TB of data scanned, organized into workgroups for isolation and cost control. Unpartitioned tables and unbounded queries make scanned-data charges balloon quickly.
You pay for what is read, not what is returned
Athena’s meter is bytes scanned: per TB of S3 data each query reads, with a 10 MB minimum per query. A query returning 5 rows can scan the entire table to find them. Layout is destiny: partitioned data lets the engine skip irrelevant files, columnar formats like Parquet let it skip irrelevant columns, and compression shrinks what remains. The same logical query can differ in cost by orders of magnitude across layouts.
Where scan charges balloon
Unpartitioned tables force full scans on every query, so each dashboard refresh re-reads all of history. Raw JSON or CSV makes every query read every column. And scheduled queries multiply whatever inefficiency exists. An unbounded select over an unpartitioned table, refreshed every 15 minutes by a BI tool, bills the whole dataset 96 times a day without anyone running a query by hand.
Workgroups are the guardrail
A workgroup can enforce a per-query scanned-data limit, cutting off the accidental full-table scan at a chosen ceiling, and it is also the unit cost is attributed to, which turns a shapeless Athena line item into per-team numbers someone can own.
Attribution and recommendations
Workgroups are discovered on the 6-hour cycle, with per-workgroup query cost from Cost Explorer or CUR 2.0. Recommendations target scan efficiency (partitioning and format candidates) and missing workgroup data limits. There is nothing to stop: Athena has no provisioned capacity, so all cost lives in query behavior.
Workgroup settings in the console
Athena console, then Administration, then Workgroups. The per-query data usage control sits in each workgroup’s settings, and blank means unlimited; that is the default, and the finding.