Skip to content
Redis with Redis Commander product logo
  • AWS· soonComing soon on Amazon Web Services
  • Azure· nextMicrosoft Azure is next on the roadmap
  • GCP· nextGoogle Cloud is next on the roadmap
Coming soon

Redis with Redis Commander

Redis Open Source 8.10.1 with its five bundled modules - RedisJSON, RediSearch, RedisBloom, RedisTimeSeries and vector sets - plus the Redis Commander web UI. Redis stays loopback-only with no password so redis-cli just works, the UI is protected with a per-instance login, and a daily snapshot backup keeps seven days.

Version
v8.10.1
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Community

What's installed

Every package and version on the image. Nothing else is installed.

  • Redis Open Source 8.10.1
  • RedisJSON
  • RediSearch
  • RedisBloom
  • RedisTimeSeries
  • Redis vector sets
  • Redis Commander 0.9.0
  • Node.js 24.20.0 LTS

Licensing — Redis Open Source 8 (AGPL-3.0 option), no licence key required

Deploy anywhere

Redis with Redis Commander on AWS.

Microsoft Azure and Google Cloud are next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS

    Amazon Web Services

    AMI · v8.10.1

    Coming soon

    AWS AMI ID

    ami-0a67e7dac2b882ccb
    Released
    September 6, 2026
    Root volume
    gp3 · 20 GiB

    Instance types

    • t3a.medium
    • t3.medium
    • t3a.large
    • m6a.large

    Regions

    • us-east-1
    AWS launch steps

Getting started

From launch to signed in, step by step.

  1. Launch in us-east-1 with TCP 22 and 8081 open; wait about two minutes. Port 6379 never needs opening.

  2. Open http://<instance-public-ip>:8081 and sign in to Redis Commander with username admin and your EC2 Instance ID as the password, exactly as the console shows it (for example i-0123456789abcdef0).

  3. SSH as ubuntu with your key pair. redis-cli and redis-cli info work directly; Redis listens on 127.0.0.1 only.

  4. Backups run daily at 00:00 UTC into /home/ubuntu/backups/redis (seven days kept). Run one now with sudo /usr/local/bin/redis-backup.sh.

  5. Want a Redis password? sudo bash /home/ubuntu/iscripts/pass_redis.sh sets, changes or removes it and keeps the UI and backup working. Change the UI login with pass_rediscommander.sh; redis_status.sh gives a health summary.

Security posture

What this image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official repository or release, nothing is copied from any third-party image, and the finished image was scanned for third-party vendor strings before capture.

  • No usable credential ships in the image; passwords are set on your instance at first boot from EC2 instance metadata (IMDSv2) and the scripts that set them delete themselves afterwards.

  • SSH is key-only, root login over SSH is refused, and build-time SSH keys, shell history and logs were removed before imaging.

  • Redis is bound to 127.0.0.1 and ::1 with protected mode on and is never exposed to the network.

  • Redis Commander - a read/write data browser - requires a sign-in issuing a JWT session; anonymous API calls return 401, the password is unique per instance from first boot, and the build-time password was randomised before imaging.

  • The UI runs as a dedicated system user under a hardened unit (ProtectSystem=strict, ProtectHome, NoNewPrivileges, PrivateTmp).

  • The image ships an empty dataset and an empty backups directory.

  • Redis packages come from the official packages.redis.io repository.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges in your security group.