Grafana With Its Own Secret Key
Grafana on loopback with a secret key of yours: every install that never set one shares the package's, which encrypts the data-source credentials in its database. Secure cookies and HSTS for the TLS proxy in front; public snapshots, plugin update checks, feedback links and Gravatar switched off. Settings verified through the API, not the file. 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-grafana-server?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [Grafana With Its Own Secret Key](https://www.iac-bazaar.com/catalog/ansible-grafana-server?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# Grafana With Its Own Secret Key: https://www.iac-bazaar.com/catalog/ansible-grafana-server (download from your IaC Bazaar account)
```Preview:
Documentation
grafana-server
Grafana on loopback, with its own secret key, Secure cookies and HSTS for the TLS proxy in front of it, and every default that talks to the outside switched off. Original role for EL 10, live-tested with podman on Rocky Linux 10.
Every unconfigured Grafana shares one secret key. secret_key encrypts
data-source credentials in Grafana's database, and the package default
(SW2YcwTIb9zpOOhoPsMm, in defaults.ini) is the same on every install that
never set it - anyone with a copy of the database and that string reads every
stored password. This role requires a key of yours and the live test greps the
package's out of the rendered file.
The real defaults are not in /etc/grafana/grafana.ini. That file is a
commented sample; /usr/share/grafana/conf/defaults.ini is what applies. The
role writes a short grafana.ini in which every line is a decision, and the
live test reads the settings back through /api/admin/settings - what Grafana
runs with, not what a file says.
Off here, on in Grafana: publishing dashboard snapshots to Grafana Labs' public service, plugin update checks, feedback links, Gravatar lookups. Usage reporting and update checks are already off in the EL packaging (upstream ships them on); the role pins them so a package from elsewhere cannot turn them back on.
Loopback and Secure. Grafana speaks plain HTTP, so it listens on
127.0.0.1 for a TLS proxy (this catalogue's haproxy-tls or caddy-https),
marks its cookies Secure and sends HSTS. On plain HTTP a browser will not keep
the session cookie; the API still answers, which is what the live test uses.
The admin password seeds a new database. admin_password in the ini
applies when Grafana creates its database; for an existing one run
grafana cli admin reset-admin-password <new>. Placeholders are refused
with grafana_server_refuse_placeholders: true.
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-victoria-logs
VictoriaLogs from the upstream release as a hardened service on loopback. Its JSON-lines endpoint answers 200 and stores nothing when the content type is wrong, so the README names the one it needs. The live test ingests two lines, gets the right one back from LogsQL, and sees an unwritten stream come back empty and bad LogsQL refused. Original role, live-tested on Rocky Linux 10.
ansible-alertmanager
Prometheus Alertmanager from the upstream release (sha256-verified) as a hardened system service on loopback, its cluster gossip listener switched off and its configuration checked by amtool before it lands. The live test posts an alert through the API and reads it back active, held by the default receiver, and expects no 9094 listener at all. Original role, live-tested on Rocky Linux 10.
ansible-alloy
Grafana Alloy from the upstream release (sha256-verified) as a hardened system service on loopback with --disable-reporting, a self-scrape pipeline that proves the collector runs, and its configuration checked by alloy validate before it lands. The live test reads Alloy's own metrics and asks the component API for the scrape component's health. Original role, live-tested on Rocky Linux 10.
ansible-blackbox-exporter
Prometheus Blackbox exporter from the upstream release (sha256-verified) as a hardened system service on loopback with HTTP and TCP modules, checked by --config.check before the file lands. The live test has it probe itself over HTTP and TCP (probe_success 1) and a port with nothing behind it (probe_success 0): it measures, not only answers. Original role, live-tested on Rocky Linux 10.
ansible-cockpit
Cockpit from BaseOS bound to loopback, with logins limited to an admin group through PAM and root refused outright. The live test sees an administrator log in while an ordinary account, a wrong password and root, placed in the admin group to isolate its own rule, are refused, and reads the login banner. Original role, live-tested on Rocky Linux 10.
ansible-fluent-bit
fluent-bit from EPEL, following a log-file glob it re-reads every few seconds and shipping over the Forward protocol, with retries unlimited instead of the default single retry. Its config is checked with --dry-run before it lands. The live test writes a line to a new file and watches it arrive at an aggregator it started. Original role, live-tested on Rocky Linux 10.