What problem does it solve? Setting up a Redis-compatible store on Render involves several decisions that are easy to get wrong: choosing the right maxmemory policy, wiring connection strings into services, configuring the required ipAllowList in Blueprints, and understanding internal versus external URLs. This Skill guides you through provisioning and configuring Render Key Value (Valkey 8) instances correctly the first time. ## Core Features & Use Cases - Blueprint Configuration: Generate valid render.yaml Key Value services with the mandatory ipAllowList field and correct maxmemoryPolicy for your workload. - Connection Wiring: Wire REDIS_URL into web services and workers using fromService with type: keyvalue and the connectionString property. - Policy Selection: Choose between allkeys-lru for caches and noeviction for job queues so queued jobs are never silently evicted. - Use Case: You are deploying a Node.js API with a BullMQ background worker on Render. Use this Skill to create a Key Value instance with noeviction, wire REDIS_URL to both services via Blueprint, and connect with ioredis using the internal URL. ## Quick Start Ask the assistant to create a Render Blueprint with a Key Value instance named cache using the allkeys-lru policy and wire its connection string to your web service as REDIS_URL.