How to Configure SingleStore Backup User

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a singlestore backup user by creating an account with backup permissions. Then you scope that account to specific databases or the whole cluster. Many teams skip this step and use the root account for automated jobs. Broad roles create big risks if a script breaks or an attacker steals a key. A dedicated account keeps your daily data snapshots safe and limits blast radius. How a singlestore backup user works in practice SingleStore uses role-based rules to control who can export da

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 a singlestore backup user by creating an account with backup permissions. Then you scope that account to specific databases or the whole cluster. Many teams skip this step and use the root account for automated jobs. Broad roles create big risks if a script breaks or an attacker steals a key. A dedicated account keeps your daily data snapshots safe and limits blast radius.

How a singlestore backup user works in practice

SingleStore uses role-based rules to control who can export data and metadata. When a backup job runs, the aggregator node checks the account permissions first. The account needs rights to read cluster metadata and write snapshot files out. You can grant these rights directly to one user or through a group role.

First, an admin creates a dedicated account for the backup job or tool. Next, the admin assigns the backup permission to that account on target databases. If you run cluster-wide snapshots, you grant this permission across all databases instead. The user also needs permission to read system tables that track cluster state. Once set up, the backup tool logs in with this account on a schedule. The aggregator coordinates with leaf nodes to stream data to your storage bucket. The database engine blocks this account from dropping tables or changing app data.

Why you should avoid root accounts for backups

Using a root or admin account for automated tasks is a common mistake. Cron jobs and backup scripts often store login keys on disk or in text files. If an attacker reads that file, a root key gives them total control. They could delete production tables, alter user roles, or steal all customer data.

A scoped account limits what a stolen key can do on your cluster. Even if someone grabs the backup key, they cannot run delete or update commands. You also get cleaner audit logs when every tool uses its own name. Your team can see right away which service ran a heavy export query. Separating human admins from machine jobs is a basic rule for database safety.

User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Where native database permissions fall short

Native grants decide who can log in and start a backup job. They do not inspect what individual queries do once the session is active. A user with read rights for backups can often query raw tables directly. That means the account can read sensitive fields like emails, phone numbers, or card numbers.

Static keys for these accounts also tend to live forever without rotation. Teams rarely update passwords because changing them might break nightly backup scripts. Native database roles also cannot require a quick human check before a manual export. If an engineer logs in with the backup role, the database trusts them right away. You need extra controls to watch sessions, mask data in results, and remove static keys.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Can a backup account restore data to the cluster?

No, reading data for a snapshot and restoring a database use separate permissions. You must grant specific restore and write rights to load a snapshot back in. Many teams keep backup and restore roles separate to prevent accidental overwrites.

Should engineers share the backup account for data exports?

No, machine accounts should only run automated jobs from your scheduler or server. When humans share a service account, you lose track of who ran which query. Give each engineer their own login so audit logs stay clear and accurate.

How often should we rotate keys for backup jobs?

If you use static passwords, you should rotate them every thirty to ninety days. Test the new password in a staging setup first so nightly jobs do not fail. A better path is to remove static keys from scripts and use short-lived sessions.

The query runs. The emails stay hidden.