DigitalOcean Managed Database
Managed PG/MySQL/Valkey cluster with firewall trust list, users, DBs, and replicas.
Verification
Plan-validatedPassed: 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
- SHA-256 checksum
- Cosign signature
Functional
- Live test pending (no cloud run yet)
Last verified 2026-06-28 · 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 do-managed-database-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/do-managed-database/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle do-managed-database-1.0.0.sigstore.json \
do-managed-database-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "13337bdb6a90d3074bccec70c15a32f2dd57990ff05724846d8944641b749ddd do-managed-database-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "managed_database" {
source = "www.iac-bazaar.com/iac-bazaar/do-managed-database/digitalocean"
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 plan-validated because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/do-managed-database?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [DigitalOcean Managed Database](https://www.iac-bazaar.com/catalog/do-managed-database?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "managed_database" {
source = "www.iac-bazaar.com/iac-bazaar/do-managed-database/digitalocean"
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
do-managed-database
Managed PG/MySQL/Valkey cluster with firewall trust list, users, DBs, and
replicas. One module call provisions the cluster (single-node to 3-node HA),
locks inbound access to an explicit trust list, creates additional users and
logical databases, and stamps out read replicas — with engine-conditional
arguments (sql_mode, eviction_policy) wired automatically so a single
interface covers all three engines. Works with Terraform and OpenTofu
(>= 1.6), DigitalOcean provider >= 2.0, < 3.0.
Opinionated defaults:
- Explicit weekly maintenance window (Sunday 04:00 UTC)
- Engine-conditional preconditions fail fast at plan time (users/DBs/replicas on Valkey are rejected before any API call)
- Credentials only leave the module through
sensitiveoutputs
Requirements
- Terraform or OpenTofu
>= 1.6 digitalocean/digitaloceanprovider>= 2.0, < 3.0(thevalkeyengine needs a recent 2.x — latest recommended)
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
- Notes
Related modules
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.
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.
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.
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.
gcp-alloydb
AlloyDB cluster with primary + read-pool instances, PSC connectivity, automated backups and columnar/vector engine flags.
aws-aurora
Aurora PostgreSQL/MySQL cluster with instances, parameter groups, Serverless v2 scaling, and enhanced monitoring.