OpenSearch Domain that Refuses to Be Public
A VPC domain with fine-grained access control and the three encryption settings that cannot be added afterwards. Building a public endpoint takes an explicit opt-in, because a public domain with a permissive policy is how this service leaks databases.
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 "opensearch" {
source = "www.iac-bazaar.com/iac-bazaar/aws-opensearch/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-opensearch?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [OpenSearch Domain that Refuses to Be Public](https://www.iac-bazaar.com/catalog/aws-opensearch?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "opensearch" {
source = "www.iac-bazaar.com/iac-bazaar/aws-opensearch/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-opensearch
An Amazon OpenSearch Service domain, placed in a VPC, with fine-grained access
control and the three encryption settings that cannot be added later. Works with
Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
The failure mode this service is known for is a domain with a public endpoint and a permissive access policy. It has leaked medical records, voter rolls and customer databases, repeatedly, and every time the cause was those two settings together. So:
- Passing
subnet_idsplaces the domain in a VPC - Leaving them null builds a public endpoint, and a precondition refuses that
unless
allow_public_endpoint = truesays you meant it access_policiesdefaults to unset, so authorization is done by the fine-grained roles inside the domain rather than a policy with a wildcard principal
Three settings are not variables: encryption at rest, node-to-node encryption, and HTTPS enforcement. All three are settable only at creation or through a blue/green deployment, so a domain created without them stays without them.
Fine-grained access control uses an IAM principal (master_user_arn), not
the internal user database. An internal master means a password in the state
file and a second identity system to rotate.
Preconditions that catch what the API reports late or not at all:
instance_countmust divide evenly acrossavailability_zonesdedicated_master_countmust be 3 or 5 - an even number cannot break a tie, and 1 is not a quorumlog_typesset with nolog_group_arnmeans logs with nowhere to go
dedicated_master_enabled defaults to off, which runs cluster state on the
nodes that also serve queries - survivable on a small domain, and the reason the
default is cheap rather than safe. The example turns it on, because anything
carrying production traffic should.
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.