What problem does it solve? Setting up a Redis-compatible store on Render involves decisions about maxmemory policies, IP allow lists, internal versus external URLs, and Blueprint wiring that are easy to get wrong, leading to dropped queue jobs, auth failures, or connection errors. ## Core Features & Use Cases - Blueprint Configuration: Generates valid render.yaml Key Value services with the required ipAllowList field and correct maxmemoryPolicy for caches, session stores, or job queues. - Connection Wiring: Wires REDIS_URL to services via fromService with type: keyvalue and provides client code for Node.js, Python, Ruby, and Go. - Troubleshooting: Diagnoses common failures such as IP allowlist auth errors, WRONGPASS after enabling internal auth, OOM errors under noeviction, and data loss on Free tier upgrades. - Use Case: You are adding a BullMQ job queue to a Render web service and need a Key Value instance with noeviction policy, internal-only access, and the connection string injected as an environment variable. ## Quick Start Ask the assistant to create a Render Key Value instance for a job queue and wire its connection string into your web service Blueprint.
