A Graph Database that Has No Password
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.
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 "neptune" {
source = "www.iac-bazaar.com/iac-bazaar/aws-neptune/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-neptune?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [A Graph Database that Has No Password](https://www.iac-bazaar.com/catalog/aws-neptune?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "neptune" {
source = "www.iac-bazaar.com/iac-bazaar/aws-neptune/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-neptune
A Neptune graph cluster that requires an IAM identity to query, is encrypted,
and keeps a record of who queried it. Works with Terraform and OpenTofu
(>= 1.6), AWS provider >= 6.0, < 7.0.
Neptune has no password. No user, no password, no GRANT - nothing
resembling database authentication exists in the engine. Access control is IAM,
and iam_database_authentication_enabled defaults to false. With it off,
the only thing between a caller and the whole graph is whether they can reach
port 8182: anything inside the security group can read every edge, write new
ones, and drop the lot, and there is no second check behind the network. On
here, and iam_authentication_required is an output because it is the single
most useful thing to assert on for this service.
The audit log needs two settings in two different resources.
neptune_enable_audit_log in the cluster parameter group turns the log on
inside the engine; enable_cloudwatch_logs_exports on the cluster is what ships
it anywhere. Set one and you get no log and no error. One list - log_exports,
defaulting to ["audit"] - drives both, because either half alone is a
configuration that reports success and does nothing.
storage_encrypted defaults to false and cannot be changed afterwards.
Getting it wrong means a snapshot-and-restore migration later, so this module
hardcodes it to true rather than offering it as a choice. The key is yours
if you pass one; otherwise it is the AWS-managed aws/rds key, which is still
encryption but on a key you cannot scope with a policy or revoke.
Smaller things: neptune_enforce_ssl is set so a misconfigured client cannot
quietly fall back to plaintext; two instances by default, because a single
member turns a failure into a restore; and a precondition refuses the
combination skip_final_snapshot = false with no final_snapshot_identifier,
which otherwise fails at the very end of a destroy.
cluster_resource_id is an output because that - not the cluster name - is
what a neptune-db:connect policy is written against.
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-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.