Iceberg Tables That Say How Far Back They Go
Amazon S3 Tables: a table bucket, its namespaces and Iceberg tables. Three maintenance jobs run by default and together they set how long history survives - snapshots expire at 120 hours, unreferenced objects are deleted permanently 13 days later, compaction targets 512 MB. This module makes each an input and returns the resulting window, and validates the numbers the provider does not.
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-17 · how we verify
Use it from the registry
terraform · opentofumodule "s3_tables" {
source = "www.iac-bazaar.com/iac-bazaar/aws-s3-tables/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.
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-s3-tables
Amazon S3 Tables: a table bucket, its namespaces and Apache Iceberg tables.
Works with Terraform and OpenTofu (>= 1.6), aws provider >= 6.0, < 7.0.
The defaults decide how far back you can look. S3 Tables runs three maintenance jobs, all on by default:
| Job | AWS default | What it decides |
|---|---|---|
| Snapshot management | keep 1, expire past 120 hours | the table's time travel and rollback window |
| Unreferenced file removal | 3 days, then 10 | when unreferenced objects are permanently deleted |
| Compaction | on, 512 MB target | query speed, and a per-run bill |
Five days of history is a reasonable default for a working table and the wrong
one for a table someone may need to restore from. Nothing in a plan says which
you have, so this module makes each number an input with AWS's own value as the
default, and returns time_travel_hours and days_until_data_is_unrecoverable
so the answer is in the output rather than in a console tab. AWS is explicit
about the end of that road: "Deletes of noncurrent objects are permanent with no
way to recover these objects" - the only recourse is AWS Support.
The provider does not check these numbers. Both aws_s3tables_table_bucket
and aws_s3tables_table carry a TODO saying the validations are still missing,
so a 600 MB target file size or a zero-day retention plans cleanly and fails at
apply. This module validates them itself.
Encryption. Every table bucket is encrypted; SSE-S3 (AES256) is the default and the module keeps it unless you pass a key. S3 Tables accepts customer managed KMS keys only - an AWS managed key is refused, and the module says so before the API does. A table can carry its own key, but changing that key later REPLACES the table, because the provider marks the attribute RequiresReplace.
Two things not worth doing here. A bucket policy denying plain HTTP, because
S3 Tables always requires TLS 1.2 or above; and choosing a compaction strategy
(auto, binpack, sort, z-order), because the API has them and the provider does
not expose them yet, so every table gets auto.
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-datasync
preserve_deleted_files = REMOVE deletes files at the DESTINATION that are absent from the source, so an unmounted share or a renamed path empties the destination on schedule and the task reports success. PRESERVE here, with verification on, a bandwidth ceiling so it cannot take the whole Direct Connect, and a per-file report of what failed.
aws-s3-bucket
Private S3 bucket with encryption, versioning, public-access block, and TLS-only policy.
aws-backup
A vault, its plans and what they protect, with the service role that can restore as well as back up. Vault Lock is stated rather than defaulted: COMPLIANCE mode cannot be removed by anybody once its window elapses, which is the point and is irreversible.
aws-efs
An EFS file system with mount targets, a least-privilege NFS security group, lifecycle tiering, automatic backups, and a resource policy that enforces encryption in transit.
aws-ebs-volume
Volumes that are always encrypted, optional attachment, and a DLM snapshot schedule in the same module - because a volume with no schedule is one copy of your data on hardware that can fail, and leaving snapshots to somebody else usually means nobody.
aws-fsx-lustre
A Lustre file system with the S3 link, root squash and compression set deliberately. SCRATCH deployments are not replicated - a lost file server loses the data - so this defaults to PERSISTENT_2 and refuses the combinations FSx accepts quietly.