AWS S3 Bucket (hardened)
Private S3 bucket with encryption, versioning, public-access block, and TLS-only policy.
Compare Object Storage across clouds →
Part of: AWS Production Landing Zone
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-11 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o aws-s3-bucket-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-s3-bucket/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-s3-bucket-1.0.0.sigstore.json \
aws-s3-bucket-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "71945eec9c5ed169dbb7f8109fe474f90fff405b4eb0203466febf0d0f027685 aws-s3-bucket-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "s3_bucket" {
source = "www.iac-bazaar.com/iac-bazaar/aws-s3-bucket/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 live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-s3-bucket?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [AWS S3 Bucket (hardened)](https://www.iac-bazaar.com/catalog/aws-s3-bucket?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "s3_bucket" {
source = "www.iac-bazaar.com/iac-bazaar/aws-s3-bucket/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-s3-bucket
A hardened-by-default private AWS S3 bucket module. Works with Terraform and
OpenTofu (>= 1.6), AWS provider >= 5.0, < 7.0.
Secure defaults:
- Server-side encryption (AES256, or SSE-KMS when
kms_key_arnis set) - Object versioning (on by default)
- Full public-access block
- Bucket policy denying any non-TLS (
aws:SecureTransport = false) access - Default lifecycle rule aborting incomplete multipart uploads after 7 days
(set
abort_incomplete_multipart_upload_days = nullto manage lifecycle configuration outside the module) - Optional server access logging into a buyer-owned bucket via
access_log_bucket
Upgrade note
Since 2026-08 the module creates a default aws_s3_bucket_lifecycle_configuration
with a single rule that aborts incomplete multipart uploads after
abort_incomplete_multipart_upload_days (7) days — a cost-hygiene rule that
never touches completed objects. Existing buckets gain the rule on the next
apply. S3 allows only one lifecycle configuration per bucket, so if you manage
lifecycle rules outside the module, set
abort_incomplete_multipart_upload_days = null.
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
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
- Inputs
- Outputs
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-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.
aws-s3-tables
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.