How to Configure Make MariaDB Read Only Access

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make mariadb read only access by creating a restricted database user. Then you put those user credentials into your Make automation module. Many teams use their main admin account to link Make to MariaDB at first. This fast shortcut gives every automated workflow the power to change or delete live data. A single bad module setting can wipe out a whole table by mistake. How to set up make mariadb read only access First, an admin logs into the MariaDB server to make a dedicated accou

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up make mariadb read only access by creating a restricted database user. Then you put those user credentials into your Make automation module. Many teams use their main admin account to link Make to MariaDB at first. This fast shortcut gives every automated workflow the power to change or delete live data. A single bad module setting can wipe out a whole table by mistake.

How to set up make mariadb read only access

First, an admin logs into the MariaDB server to make a dedicated account. This account is just for your Make workflows. You set the host rules on this user to match the IP addresses Make uses. If you allow any host to log in, outside attackers might try to guess the password.

Next, you grant read permissions to this new database user. In MariaDB, this means giving the user permission to select rows from specific tables. You should never grant permission to insert, update, or drop tables to this role. You can also limit the user to one database schema instead of the whole server. If your workflow uses database views, the user needs permission to view those too. Once you save the permissions, MariaDB checks them every time Make runs a query.

Finally, you open Make and create a new MariaDB connection in your scenario. You enter your server host address, port, database name, and the new read-only user credentials. It is to turn on encrypted transport so passwords do not travel in plain text. After you test the link, your Make modules can pull data without risking accidental writes.

Where native database roles fall short for automation

Native database permissions are a great first step for safety. They stop your Make scenarios from changing rows or dropping tables. They also help you separate automation traffic from human admin traffic in basic server logs.

Still, static database roles only check who logs in at the start. They do not inspect what individual queries do while they run. A read-only user can still run a huge query that locks up your MariaDB server. Worse, a read-only account can pull sensitive customer rows into third-party tools.

Auditor Read-Only Access + Customer Support Access to Production: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

If a Make scenario reads a customer table, it pulls all columns in that table. Raw emails, phone numbers, card numbers, and national IDs flow straight into the Make execution history. Anyone on your team who can view the Make scenario logs can see that private data. Native MariaDB roles cannot rewrite matched fields in query results on the fly. You also have to store long-lived database passwords inside the Make platform. Rotating those static passwords means updating both MariaDB and every Make connection by hand.

Managing query risks in third-party workflows

To keep live data safe, teams need controls that work at the query level. You should limit which columns an automation tool can read in plain text. When a workflow only needs order totals, it should not receive raw card numbers or emails. Masking those fields before they leave your network keeps private data out of cloud logs.

You also need clear audit logs for every query that Make sends to MariaDB. Standard database logs often miss context when many workflows share one read-only account. Tracking each query with full timestamps helps you spot slow runs and data leaks fast.

Add wire guardrails and masking beside MySQL

Database grants and TLS setup decide who can reach MySQL. Even so, an open session can run broad updates or read raw personal data from allowed tables. In practice, hoop.dev runs beside the database as a sidecar for your MySQL. It keeps your login setup and drivers as they are while checking queries on the wire.

With hoop.dev MySQL support, guardrails refuse bad queries before they run and return a readable MySQL error. Data masking rewrites matched sensitive values in result rows in memory. Furthermore, hoop.dev holds SOC 2 Type II and generates evidence for GDPR, HIPAA, and PCI DSS programs. Read the docs and source on GitHub.

Frequently asked questions

Can a MariaDB read-only user still slow down my database?

Yes, a read-only user can run heavy select queries that join many large tables. These big reads use up memory and CPU, which slows down your main app.

Why should Make have its own MariaDB user account?

A separate account lets you limit Make to specific tables and read-only actions. It also lets you revoke credentials for Make without breaking your other apps.

Does read-only permission hide sensitive data from Make logs?

No, read-only permission lets Make read all text in the allowed tables. Sensitive fields like emails and phone numbers will still show up in Make run logs.

The query runs. The emails stay hidden.