Skip to content
Redis with Redis Commander product logo
  • AWSAvailable on Amazon Web Services
  • AzureAvailable on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

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
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. 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

LicensingRedis Open Source 8 (AGPL-3.0 option), no licence key required

Deploy anywhere

Redis with Redis Commander on AWS and Azure.

Google Cloud is 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
    Available

    Amazon Web Services

    AMI · v8.10.1

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    Released
    Root volume
    gp3 · 20 GiB
    Instance types
    • t3a.medium
    • t3.medium
    • t3a.large
    • m6a.large
    Regions34 regions· show all
    • us-east-1
    • af-south-1
    • ap-east-1
    • ap-east-2
    • ap-northeast-1
    • ap-northeast-2
    • ap-northeast-3
    • ap-south-1
    • ap-south-2
    • ap-southeast-1
    • ap-southeast-2
    • ap-southeast-3
    • ap-southeast-4
    • ap-southeast-5
    • ap-southeast-6
    • ap-southeast-7
    • ca-central-1
    • ca-west-1
    • eu-central-1
    • eu-central-2
    • eu-north-1
    • eu-south-1
    • eu-south-2
    • eu-west-1
    • eu-west-2
    • eu-west-3
    • il-central-1
    • me-central-1
    • me-south-1
    • mx-central-1
    • sa-east-1
    • us-east-2
    • us-west-1
    • us-west-2
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.02/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Available

    Microsoft Azure

    Compute Gallery image · v8.10.2

    Azure Compute Gallery image ID

    Selected for you when you create the VM from the Azure Marketplace listing.

    Released
    OS disk
    Premium_LRS · 30 GiB
    VM sizes
    • Standard_D2as_v7
    • Standard_D2as_v5
    • Standard_B2ms
    • Standard_D4as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Launch on Azure MarketplaceAzure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region 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 AWS 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.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22 and 8081 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match. Wait about two minutes for first boot.

  2. Open http://<vm-public-ip>:8081/ and sign in as admin.

  3. The password is your VM ID: in the Azure portal open the virtual machine, choose Properties and copy VM ID - a 36-character value such as 02aab8a4-74ef-476e-8182-f6d2ba4166a6, typed exactly as shown in lower case.

  4. Redis listens on 127.0.0.1:6379 only and has no password by design - it is not reachable from outside the VM. If you want to expose it, set a password first with sudo bash ~/iscripts/pass_redis.sh and only then open port 6379 to your own networks.

  5. SSH as ubuntu with your key.

Security posture

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

  • Clean-room build on Canonical's official Ubuntu image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • The Redis Commander password is set on first boot from your VM's own vmId.

  • Redis itself has no password because it is bound to loopback with protected mode on.

  • The pre-image cleanup proves the build's own credentials are rejected before capture, and first boot sets every password from the new VM's own vmId, read from Azure IMDS.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and cloud-init installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture.

  • Verified against Microsoft's documented Linux certification test cases on a VM deployed from this gallery version - 13 passed, 0 failures - with VM extension provisioning confirmed and every helper script executed rather than only reviewed.

  • Do not open port 6379 without setting a Redis password first.

  • Restrict port 22 to trusted IP ranges, and put the consoles behind HTTPS with your own certificate before exposing them to the internet.