# Ensure production Key Value instances have persistence enabled

- Source: https://support.icompaas.com/support/solutions/articles/a_1793876669865807-ensure-production-key-value-instances-have-persistence-enabled
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Render Cloud](https://support.icompaas.com/support/solutions/c_1793875953948152) › [Checks](https://support.icompaas.com/support/solutions/folders/f_1793875960840493)
- Last updated: 2026-11-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure production Key Value instances used for job queues, sessions, or other data that must not be lost have their Persistence Mode set to Journal + Snapshot (or at least Snapshot only), so data is saved to disk and survives restarts. Instances used only as caches can keep persistence off.

**Rationale**

With persistence off, all data is lost whenever the instance restarts, is upgraded, or fails. For queues and sessions, that means lost jobs and logged-out users. Persistence writes data to disk, encrypted at rest with AES-256, so it can be recovered after a restart.

**Impact**

-   Queue and session data survives restarts
    
-   Reduces data loss during maintenance
    
-   Changing the mode restarts the instance, and switching to or from Off clears its data
    

**Default Value**

Paid Key Value instances support disk-backed persistence and enable it by default. Free instances do not support persistence.

**Pre-Requisites**

-   Admin or Developer role (Admin for protected environments)
    
-   A paid Key Value plan
    

**Remediation**

**Test Plan**

1.  Sign in to the Render Dashboard at [https://dashboard.render.com](https://dashboard.render.com/).
    
2.  From your workspace home (or project), click the Key Value instance to open it.
    
3.  On the Info page, check the Persistence Mode.
    
4.  If a production instance used for queues or sessions shows Off, or is on the Free plan, follow the implementation steps.
    

**Implementation Steps**

1.  Sign in to the Render Dashboard at [https://dashboard.render.com](https://dashboard.render.com/).
    
2.  From your workspace home (or project), click the Key Value instance to open it.
    
3.  If the instance is on the Free plan, upgrade it from the Key Value Instance section (Compute Plan > Update). Data on Free instances is lost during the upgrade.
    
4.  Set the Persistence Mode to Journal + Snapshot and save. The instance restarts, and data is cleared when switching from Off.
    

**Backout Plan**

1.  Sign in to the Render Dashboard at [https://dashboard.render.com](https://dashboard.render.com/).
    
2.  From your workspace home (or project), click the Key Value instance to open it.
    
3.  Set the Persistence Mode back to its previous value and save.
    

**Reference**

-   [https://render.com/docs/key-value](https://render.com/docs/key-value)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.