ExoscalePlan-validated

Exoscale DBaaS

Managed PG/MySQL/Kafka with IP filters and TF-managed users.

terraformAlt & Specialty Cloudsexoscale

Compare Managed Relational Database across clouds →

exoscale-dbaasvizier v1.2.0

Verification

Plan-validated

Passed: module logic verified on a mocked plan - inputs, validation rules, conditional creation and outputs resolve (no real provider, no cloud).

Conformance

  • Static validation (fmt · validate · tflint)
  • No applicable security policies for this provider
  • Plan tests (mocked: validation rules · outputs)

Provenance

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-06-28 · how we verify

Verify this download

cosign · sha-256

Don'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 exoscale-dbaas-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/exoscale-dbaas/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle exoscale-dbaas-1.0.0.sigstore.json \
  exoscale-dbaas-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "3cfb32239999ec97eee73dd1184f0298551110c180911dbb74f8eaaa94121704  exoscale-dbaas-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "dbaas" {
  source  = "www.iac-bazaar.com/iac-bazaar/exoscale-dbaas/exoscale"
  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 · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads plan-validated because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: plan-validated](https://www.iac-bazaar.com/api/artifacts/exoscale-dbaas/badge)](https://www.iac-bazaar.com/catalog/exoscale-dbaas?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, plan-validated on IaC Bazaar: [Exoscale DBaaS](https://www.iac-bazaar.com/catalog/exoscale-dbaas?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "dbaas" {
  source  = "www.iac-bazaar.com/iac-bazaar/exoscale-dbaas/exoscale"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: plan-validated

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

exoscale-dbaas

An Exoscale DBaaS managed database — PostgreSQL, MySQL, or Kafka (Aiven-backed) — with a deny-by-default IP filter, termination protection, and, for PostgreSQL, declaratively-managed logical databases and users. Targets EU-sovereign zones (CH / AT / DE).

Status: static-validated, live-test pending. Validated with tofu validate + tflint + checkov against the exoscale/exoscale provider. Not yet applied against a live Exoscale account, so it ships under live-test quarantine.

Design & secure defaults

  • One engine, selected by type. Set type to pg, mysql, or kafka; the module renders the matching engine block (the blocks are mutually exclusive). Engine version, backup schedule, and raw engine settings are shared inputs applied to whichever engine is active.
  • Deny-by-default network exposure. ip_filter is empty by default, which denies all external sources. Add operator/app CIDRs explicitly; TLS is always required (the CA certificate is exported as a sensitive output).
  • Termination protection on to prevent accidental deletion / power-off.
  • Kafka enforces mTLS. kafka_enable_cert_auth = true by default; SASL is off unless explicitly enabled.
  • Managed PostgreSQL objects. pg_databases and pg_users create logical databases and users when type = "pg". User passwords are generated by the service and surfaced via the sensitive pg_user_passwords output — secrets are never used as for_each keys. A precondition rejects pg-only objects for non-pg engines.

Plan names drift. DBaaS plans are Aiven-backed and renamed over time. Confirm the current plan for your type/zone with exo dbaas type show <type> --plans before applying.

Provider

exoscale/exoscale ~> 0.69. Requires Terraform/OpenTofu >= 1.6.

License

Commercial — LicenseRef-IaCBazaar-Commercial. See the IaC Bazaar terms.

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
  • Key inputs
  • Outputs

Related modules

Static validatedLive test pending

civo-database

firewall_id is optional and a database without one answers to every address that can reach its endpoint; nodes = 1 is one node whose failure is downtime; and backups are the platform's, not configurable here. Firewall and network required, two nodes (one by name), the password as a sensitive output, and an output that says no backup schedule can be set.

View module
Static validatedLive test pending

vultr-database

A managed database gets a public hostname and trusted_ips is optional: left empty, any address on the internet may try the password; the backup hour is picked for you; and a plan with no replicas is one node whose failure is downtime. Trusted ranges required (a /0 refused unless accepted), a VPC attachment, one standby by default, both windows set, and the password as a sensitive output.

View module
Static validatedLive test pending

azure-sql-managed-instance

The public data endpoint turns a private database into one listening on the internet on port 3342; SQL logins put an administrator password in state when Entra-only authentication would remove them entirely; and zone redundancy is off by default. Private, Entra-only with SQL authentication accepted by name, Business Critical across zones, TLS 1.2, and geo-zone-redundant backups.

View module
Static validatedLive test pending

oci-postgresql

password_type PLAIN_TEXT writes the admin password into the Terraform state and every plan that shows it; storage that is not regionally durable dies with its availability domain; and a DB system created without a management policy takes no backups. Vault secret reference, regionally durable storage, daily backups optionally copied to another region, a read replica, and an NSG on port 5432.

View module
Live-tested

gcp-alloydb

AlloyDB cluster with primary + read-pool instances, PSC connectivity, automated backups and columnar/vector engine flags.

View module
Live-tested

aws-aurora

Aurora PostgreSQL/MySQL cluster with instances, parameter groups, Serverless v2 scaling, and enhanced monitoring.

View module