Single Redis Instance
Use this guide when users need Redis for cache, queue, session, or lightweight data access as one standalone instance.
Recommended deployment mode: Single Database. This is ideal for simple Redis-backed workloads that do not require clustered resilience.
Provisioning Flow
Open the Database Deployment Flow
Choose the database path in Autonomous instead of a source-code project.
Select Redis
Configure version, memory and storage expectations if persistence is enabled, credentials if used, and the target environment.
Choose Single Instance
Select the standalone topology so one Redis workload is provisioned for the environment.
Validate Connectivity
Confirm internal access, readiness, and application connection settings after deployment finishes.
Common User Mistakes
- Treating a single Redis instance as highly available
- Not planning for persistence strategy
- Application clients still using local development endpoints