Securing your RedisMonitor

RedisMonitor works by connecting to your Redis server from one of several monitoring servers in Amazon's us-east-1 EC2 Region and recording details on your server's performance. Basic functionality requires only the PING, SLOWLOG, and INFO commands, Memory scanning and other features require broader command access.

RedisMonitor connects from any one of the following IPs:


If your network configuration requires CIDR notation, append a mask of/32 for each IP address, e.g.

Find the set of instructions below most appropriate for your setup to allow RedisMonitor to access your Redis server.

Questions? We're happy to help by email or the in-app support system.

AWS EC2 VPC Security Group

You can add the following rules to your Security Group to allow RedisMonitor to connect, using the port of your Redis database:


Allow the each of the IPs above to access your Redis port in your ACL's "Inbound Rules" tab, by specifying the CIDR address of each IP (e.g.

You might need to configure your VPC Security Groups with the instructions above also.

Heroku Private Spaces

Heroku Private Spaces do not allow external connections for data services by default, but they can be enabled using Trusted IP ranges for data services. Once that feature is enabled, you can add each of RedisMonitor's IPs (listed at the top of this page) with a /32 CIDR suffix, e.g.

AWS ElastiCache

Due to AWS restrictions, we do not currently support ElastiCache directly.

That said, you can create a NAT instance inside your VPC that can forward RedisMonitor traffic to your ElastiCache servers. See AWS's "Accessing ElastiCache Resources from Outside AWS" page for more information. Once your NAT instance is running, you can use Security Groups, Network ACLs, firewall rules, or iptables rules to restrict access to RedisMonitor.


To allow RedisMonitor access to your server through a firewall, you'll want to allow access to the IP list above through to your Redis server's port (6379 by default). The specific steps will vary depending on your setup, but we've included two of the most common options (ufw and iptables) below:


ufw (Uncomplicated Firewall) is the default firewall tool for Ubuntu. Run the following to allow RedisMonitor to connect to your server, changing "6379" to the correct port for your Redis server:

sudo ufw allow proto tcp from to any port 6379
sudo ufw allow proto tcp from to any port 6379
sudo ufw allow proto tcp from to any port 6379
sudo ufw allow proto tcp from to any port 6379
sudo ufw allow proto tcp from to any port 6379


iptables and its successor nft can be tricky, and we're reluctant to provide instructions that might be copy-pasted and cause more problems than they solve.

The short answer here is that you need to Accept Input TCP on the port used by your Redis server (default 6379) from each of the Sources listed at the top of this document (using CIDR notation, e.g.

We like these docs on iptables:

Explore Your Redis Memory Usage with an Interactive Map

RedisMonitor shows you large keys, memory leaks, old keys, and other potential problems quickly. Try it today without a credit card.

← Back to docs