A Cassandra Table that Can Be Restored
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.
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-13 · how we verify
Use it from the registry
terraform · opentofumodule "keyspaces" {
source = "www.iac-bazaar.com/iac-bazaar/aws-keyspaces/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-keyspaces?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [A Cassandra Table that Can Be Restored](https://www.iac-bazaar.com/catalog/aws-keyspaces?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "keyspaces" {
source = "www.iac-bazaar.com/iac-bazaar/aws-keyspaces/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-keyspaces
An Amazon Keyspaces keyspace and its tables, with recovery that exists and a key
you control. Works with Terraform and OpenTofu (>= 1.6), AWS provider
>= 6.0, < 7.0.
point_in_time_recovery defaults to DISABLED, and Keyspaces has no
snapshots. There is no other recovery mechanism - no automated backup, nothing
to restore from, no undo. With PITR off, a dropped table or a bad bulk write is
simply gone, and the first time anyone checks is the time they needed it. On
here, with a precondition that refuses to turn it off unless
accept_no_recovery states that the data is reproducible from somewhere else.
Encryption is always on; the choice is whose key. AWS defaults to an AWS-owned key, which cannot be scoped with a policy, cannot be revoked, and never appears in your CloudTrail. The module defaults to a customer-managed key and refuses to pretend otherwise: if you want the AWS-owned key, say so.
Two settings here are one-way doors, so they are named rather than set quietly. Client-side timestamps can be turned on and never off - with them, a conflicting write resolves by the timestamp the client stamped; without them, by whichever row happened to reach the server first, which is the behaviour that surprises people during a retry storm or across regions. TTL can likewise be turned on and never off, and it is a data-retention decision rather than a storage optimisation: the rows delete themselves.
Key names are checked against the column list. A partition or clustering key naming a column that does not exist fails at apply with an error that names neither the table nor the column, which is a slow way to find a typo. A precondition names both.
Smaller things: a precondition refuses PAY_PER_REQUEST with capacity units
set, which the API rejects, and PROVISIONED without them; and enum-valued
settings are exposed as the API's own strings rather than as booleans behind a
conditional, because a rendered conditional can read as unresolved to a
configuration scanner and make a control that is present look absent.
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-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.
aws-opensearch-serverless
A collection cannot exist without an encryption policy and the quickest one uses the AWS-owned key; the network policy decides whether the endpoint answers on the internet; without a data access policy nobody can read or write, with a wide one everyone can; indexes grow until a policy expires them. Private through VPC endpoints (public by name), your key when given, principals named.