MariaDB That Ran Its Own Secure Installation
MariaDB bound to loopback (the package listens everywhere), with the mariadb-secure-installation steps applied by the role: anonymous users, the test database and remote root gone, LOAD DATA LOCAL off, reverse DNS off. Provisions an application database and a user that can see nothing else. Original role, live-tested on Rocky Linux 10.
Verification
Live-testedReally deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.
Conformance
- Static validation (yamllint · ansible-lint)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-09-19 · podman 4.9.3 · ansible 2.21.4 · how we verify
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 live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/ansible-mariadb-server?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [MariaDB That Ran Its Own Secure Installation](https://www.iac-bazaar.com/catalog/ansible-mariadb-server?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# MariaDB That Ran Its Own Secure Installation: https://www.iac-bazaar.com/catalog/ansible-mariadb-server (download from your IaC Bazaar account)
```Preview:
Documentation
mariadb-server
MariaDB server on Enterprise Linux, bound to loopback, with the steps of
mariadb-secure-installation applied by the role and an application database
and owner provisioned. Original role for EL 9 and 10, live-tested with podman on
Rocky Linux 10.
The package listens everywhere and keeps the leftovers. A fresh
mariadb-server sets no bind-address, so it accepts connections on every
interface; it ships a test database any user can write to and anonymous
accounts that can log in without a password; and LOAD DATA LOCAL is on, which
lets a hostile server read files from a connecting client. The interactive
mariadb-secure-installation script exists to undo the first three - and
nothing runs it for you. This role binds to 127.0.0.1, removes the anonymous
users, the test database and any root account that could log in from the
network, turns local_infile off, and turns skip_name_resolve on so grants
keyed by address mean what they say.
The application user gets its own database and nothing else. The verify
step logs in over TCP as that user and asserts it sees appdb and
information_schema only.
The password placeholder is refused when you ask. mariadb_server_password
ships as a placeholder so the live test can run; set
mariadb_server_refuse_placeholder_password: true in any real inventory and the
role stops before provisioning a user with it.
License
Commercial - IaC Bazaar EULA. (c) IaC Bazaar.
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.
- Variables
- Test
Related modules
ansible-clickhouse
ClickHouse on EL 10 from the upstream LTS release (sha512-verified), as a hardened systemd service on loopback with the default user behind a password; the live test creates a MergeTree table, inserts a row and selects it back over HTTP; a query without credentials is refused. Original role, live-tested on Rocky Linux 10.
ansible-dragonfly
Dragonfly on EL 10 from the vendor's release, pinned by a SHA-256 the role carries (the vendor publishes no checksum file), as a hardened systemd service on loopback behind a password kept in a flagfile; the live test speaks RESP itself: an unauthenticated PING and a wrong password are refused, AUTH + SET + GET round-trip. Original role, live-tested on Rocky Linux 10.
ansible-influxdb3
InfluxDB 3 Core on EL 10 from the vendor's release (checksum-verified), as a hardened systemd service on loopback with file object storage; the binary runs from its release directory (it links the Python it ships); the live test writes a point in line protocol and reads it back with SQL. Original role, live-tested on Rocky Linux 10.
ansible-meilisearch
Meilisearch on EL 10 from the vendor's release, pinned by a SHA-256 the role carries (the vendor publishes no checksum file), as a hardened systemd service on loopback in production mode behind a master key; the live test creates an index and documents, waits for the indexing task, searches and finds the one match, and sees a keyless request refused. Original role, live-tested on Rocky Linux 10.
ansible-mongodb
MongoDB Community 8.0 from MongoDB's repository, its key pinned by fingerprint: authorization on from the first start, the first administrator made through the localhost exception with a generated password, SCRAM-SHA-256 only, loopback. The live test writes as the administrator and is refused anonymously, with a wrong password and over SCRAM-SHA-1. Original role, live-tested on Rocky Linux 10.
ansible-opensearch
OpenSearch 3 (sha512-verified min distribution, bundled JDK), one node on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test reads the root document, indexes one document with a refresh, finds it by a search, deletes the index and checks the keystore belongs to the service; the release tree stays read-only. Original role, live-tested on Rocky Linux 10.