Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-12 · how we verify
Use it from the registry
terraform · opentofumodule "athena" {
source = "www.iac-bazaar.com/iac-bazaar/aws-athena/aws"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads static-verified because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-athena?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [A Workgroup whose Settings Are Binding](https://www.iac-bazaar.com/catalog/aws-athena?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "athena" {
source = "www.iac-bazaar.com/iac-bazaar/aws-athena/aws"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
aws-athena
An Athena workgroup: where the queries run, what they may cost, and where the
answers land. Works with Terraform and OpenTofu (>= 1.6), AWS provider
>= 6.0, < 7.0.
Query results are a copy of the data. Every query writes its result set to S3, and that bucket is usually not the carefully-governed one holding the source. A workgroup pointed at a shared scratch bucket quietly builds a second, ungoverned copy of whatever anybody has ever selected. That is why the result location and its encryption are the substance of this module rather than the SQL.
enforce_workgroup_configuration is what makes any of it real. Off - the
AWS default - the workgroup's settings are a suggestion: a client may send its
own output location and its own encryption setting, and Athena uses theirs.
Every control here becomes advisory. It defaults to on, and
settings_are_binding is an output so the answer is visible.
bytes_scanned_cutoff_per_query is the only thing between a typo and a bill.
Athena charges per byte scanned; a missing partition predicate on a large table
is one query that scans everything, and nothing stops it by default. This module
sets 10 GiB and a precondition refuses null unless you say you meant it.
Two smaller things it handles:
enable_minimum_encryption_configurationrefuses a query whose results would be unencrypted even when enforcement is off - a second, independent flooracl_configurationwithBUCKET_OWNER_FULL_CONTROLwhen writing into another account's bucket. Without it the objects stay owned by this account and the bucket owner cannot read their own data
Note that a client which does not pass the workgroup name runs in primary,
where none of this applies. Grant athena:StartQueryExecution scoped to this
workgroup.
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test, so it is published as statically
validated with its live test pending and does not carry the live-tested mark.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
Related modules
aws-keyspaces
point_in_time_recovery defaults to DISABLED and Keyspaces has no snapshots or automated backups, so off means a dropped table is simply gone. PITR on, a customer-managed key, and the two one-way doors - client-side timestamps and TTL - named rather than set quietly.
aws-database-proxy
Amazon RDS Proxy in front of an RDS instance or Aurora cluster: TLS required, clients authenticate with IAM tokens while the proxy reads the password from Secrets Manager, through a role limited to those secrets. Debug logging writes SQL statement text to the logs, so it is off unless that is accepted. End-to-end IAM removes the stored password entirely.
aws-dax-cache
DynamoDB Accelerator with TLS and encryption at rest. DAX leaves both off by default, and neither can be turned on for an existing cluster, so a fix means a new cluster. This module also creates its own security group (DAX otherwise uses the VPC default), a service role limited to the named tables and their indexes, and states that writes bypassing DAX leave stale reads until the TTL.
aws-neptune
Neptune has no user, no password and no GRANT. Authorization is IAM and it defaults to OFF, so anything that can reach port 8182 can read every edge and drop the lot. IAM auth on, storage encrypted, and the audit log driven from one variable because its two halves live in different resources and either alone logs nothing.
aws-dms
ssl_mode defaults to none in AWS, so a task reads your entire production database and writes it elsewhere unencrypted. This defaults to require, refuses none unless stated, and pushes the credential into Secrets Manager rather than state.
aws-quicksight
A QuickSight subscription on Enterprise edition through IAM Identity Center, with admin, author and reader groups, termination protection on because unsubscribing deletes every dashboard, and a VPC connection with its own role so a private database stays private. The authentication method is permanent; Standard edition and QuickSight-managed users are accepted by name.