Redis Cloud Terraform auto_minor_version_upgrade: Downtime, Maintenance Windows, and Rollback Behavior – Redis Knowledge Base

Automatic minor version upgrades help keep Redis Cloud databases on supported minor releases without requiring manual intervention. For eligible Redis 8.4 and later databases, upgrades occur during the subscription maintenance window and remain within the same major Redis version.

This article explains the operational behavior of automatic minor upgrades in Redis Cloud, including availability expectations, maintenance window behavior, Terraform ownership boundaries, rollback limitations, and common troubleshooting scenarios.

Quick Fix

Question	Short answer
Will `auto_minor_version_upgrade` cause downtime?	If replication is enabled, no downtime is expected, but brief latency spikes or short client disconnects can occur during failover and resync. Without replication, temporary downtime is expected while shards restart from persistence.
When does the upgrade run?	During the subscription maintenance window, as part of the Redis Cloud maintenance workflow.
Can I configure the maintenance window in Terraform on the database resource?	No. The maintenance window is managed at the subscription level, not on the `rediscloud_subscription_database` resource.
Does Redis Cloud roll back automatically if the upgrade fails?	No. Automatic rollback to the previous Redis version is not supported on Redis Cloud.
Which databases are affected?	Automatic minor upgrades apply to Redis 8.4 and later. Redis 8.2 and earlier are not auto-upgraded under this policy.
What should I do before enabling it in production?	Confirm replication status, verify the subscription maintenance window, review release notes, and make sure your Terraform provider version supports the new auto-minor behavior.

Prerequisites

Before relying on auto_minor_version_upgrade in Terraform, confirm the following:

Your database is running in Redis Cloud. This behavior is specific to Redis Cloud database version management and the Redis Cloud Terraform provider.
The database is running Redis 8.4 or later. Automatic minor version upgrades apply only to Redis 8.4+ databases.
You know your Redis Cloud plan type:
- Redis Cloud Pro allows customers to opt out of minor auto-upgrades per database.
- Redis Cloud Essentials keeps automatic minor upgrades always enabled and does not allow opt-out.
You know whether replication is enabled on the database. Upgrade impact differs significantly between replicated and non-replicated databases.
You know which maintenance window applies to the subscription:
- For Pro subscriptions, the maintenance window is configurable at the subscription level.
- For Essentials subscriptions, Redis Cloud uses the default maintenance window between 12 AM and 6 AM region time.
Your Terraform provider version has been reviewed before rollout. Older provider behavior can produce Terraform drift when the running Redis version advances ahead of the configured redis_version.

Step-by-step instructions

1. Confirm whether the setting applies to your database

Check the database Redis version in the Redis Cloud Console, API, or Terraform state.

Essentials minor auto-upgrades apply for all Redis versions, while Pro applies to Redis 8.4+ only. Databases on Redis 8.2, 7.x, or 6.x remain on their configured minor version unless manually upgraded or later impacted by a separate lifecycle policy event.

If you are using Terraform, treat auto_minor_version_upgrade as a policy toggle rather than a scheduling control. Upgrade timing is determined by the subscription maintenance window, not by the database resource block.

2. Determine the expected availability impact

Check whether replication is enabled.

For replicated databases, Redis Cloud performs controlled failovers between primary and replica shards during the upgrade process. Redis Cloud documents that no downtime is expected with replication enabled, although brief latency spikes or short client disconnects can still occur during failover and resync operations.

For non-replicated databases, temporary downtime is expected because shards restart from persistence during the upgrade.

If your application is sensitive to short failover interruptions, review client retry behavior and supported Smart Client Handoffs capabilities before rollout.

3. Confirm when the upgrade will run

Automatic minor upgrades run during the subscription maintenance window as part of the Redis Cloud maintenance workflow.

Use the Redis Cloud Console to review the subscription maintenance window settings.

For Pro subscriptions:

Configure the maintenance window at the subscription level.

For Essentials subscriptions:

Redis Cloud uses the standard maintenance window between 12 AM and 6 AM region time.

Do not expect database-level maintenance window fields in Terraform for this feature. Maintenance scheduling is subscription-scoped, not database-scoped.

4. Understand what Terraform controls

In Terraform, auto_minor_version_upgrade controls whether the database participates in automatic minor upgrades where the service policy allows it. It does not:

choose the maintenance date
choose the exact target minor version timing
force rollback behavior
replace the Redis Cloud lifecycle policy

Redis Cloud controls the actual execution timing, eligible target version, and maintenance workflow.

For Pro databases:

Customers can opt out per database.

For Essentials databases:

Automatic minor upgrades remain enabled and cannot be disabled.

5. Understand rollback behavior before rollout

Redis Cloud does not support automatic rollback to a previous Redis version after an upgrade.

If an issue occurs after the upgrade, the recovery approach is manual rather than in-place rollback. Recovery planning should be based on backup and restore procedures.

Before enabling automatic upgrades in production:

take a backup before the maintenance window
document the restore process
validate rollback expectations with your change-management process

6. Validate your Terraform provider strategy

This is the most important Terraform-specific operational check.

Once service-side auto minor upgrades are enabled, the running Redis version can advance ahead of the configured redis_version. Older provider behavior can interpret this as drift and may attempt to downgrade the version during a future terraform apply.

The Redis Cloud Terraform provider introduced the auto_minor_version_upgrade attribute in v2.7.0 for supported database resources.

Before rollout:

upgrade the Terraform provider
run terraform init -upgrade
review Terraform plans carefully if redis_version is pinned
validate behavior in non-production environments first

For Active-Active databases, review provider behavior carefully because version handling can be more sensitive for resources that treat version changes as ForceNew operations.

7. Set production expectations correctly

Use the following operational expectations when preparing production rollout or maintenance approvals:

Automatic minor version upgrades do not change the Redis major version.
Upgrades run only during maintenance windows.
Replicated databases should remain available, but brief latency spikes and short disconnects are still possible during failover.
Non-replicated databases will experience temporary downtime during restart from persistence.
Automatic rollback is not available.
The setting is database-scoped, but scheduling is subscription-scoped.

Troubleshooting

Terraform plan shows unexpected Redis version drift

This is a known operational risk area.

After Redis Cloud upgrades the running minor version, Terraform can detect a mismatch between the configured redis_version and the actual running version. Older provider behavior may attempt to downgrade the database version during apply operations.

Upgrade the Terraform provider before enabling automatic minor upgrades in production workflows.

You cannot find maintenance window settings in the Terraform database resource

That is expected.

The maintenance window is configured at the subscription level, not on the database resource itself. Use the Redis Cloud Console to review or configure the subscription maintenance window.

You expected Redis 8.2 to auto-upgrade to Redis 8.4 or later

That is not how the current policy works.

Automatic minor upgrades apply only to Redis 8.4 and later. Earlier versions require manual upgrade workflows.

Your application experienced brief disconnects during maintenance

That can still happen even with replication enabled.

Redis Cloud documents no expected downtime for replicated databases, but short failovers, reconnects, and latency spikes can still occur during maintenance events.

If this is operationally significant for your workload:

validate client retry behavior
review supported Smart Client Handoffs capabilities
test maintenance behavior in staging before production rollout

You need a rollback plan for change-management approval

Do not rely on automatic rollback.

Redis Cloud does not automatically revert database versions after upgrade. Build rollback procedures around backup and restore workflows instead.

You want tighter control over production rollout timing