Choose a tier and lock a connection
What each tier allows, and how Read-only and Enabled protect a server.
In short
A connection's tier says how much a mistake on that server would cost. Production never allows writes, deletes or flushes; Read-only locks writes on any tier, and unticking Enabled pauses the connection altogether. Reading, scanning and tests work on every tier.
Before you start
- Who: raising protection is open to anyone who can edit the connection. Lowering it needs the owner of a personal connection or, in an organization, an organization administrator.
- Plan: every plan.
- First: set the tier to what the server really is, not what it is called.
Set a tier or lock a connection
- Open "Connections" at the foot of the rail and edit the connection.
- Choose its "Tier": Local, Development, QA, Custom, Preprod, Staging or Production.
- Tick "Read-only" to refuse every write, or untick "Enabled" to pause the connection: browsing its keys, running commands and running its tests all stop until you tick it again. The connection and its tests are kept.
- Press "Save and test".
What each tier allows
Good to know
- The tier is kept apart from the name, so a connection called prod is protected only when its tier is Production.
- A read-only or Production connection says it is read-only on the Keys tab and hides the edit controls.
- The screen hides write controls as a courtesy. The server tests every request again, and a refused attempt is recorded in the audit trail with the reason.
- Raising protection is open to anyone who can edit the connection. Lowering it needs the owner of a personal connection or, on an organization connection, an organization administrator. Lowering means leaving Preprod, Staging or Production for a tier with fewer rules, or unticking Read-only.
If something goes wrong
- "Only an organization administrator can lower this connection's tier or make it writable."
- "Production connections are read-only: nothing is written, deleted or flushed there."
- "Connection … is read-only." / "Connection … is disabled.": change it under "Connections" if you may.
Related
- /help/cache-tester/delete-keys
- /help/cache-tester/read-the-audit-trail
- /help/cache-tester/start-here