Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

The advice I got from DO is the following:
" Remediation of this issue will take just a few minutes and is relatively straightforward. You will need to open /etc/redis/redis.conf and uncomment (remove the “#”) or modify the line beginning with:
#bind 127.0.0.1 ::1
Afterwards, restart redis with:
sudo systemctl restart redis
"
However, I did not install redis directly on the droplet itself. My droplet has docker installed and I use portainer to menage all my containers, so my redis, postgres, backend, pgadmin, redisinsight are all docker containers in the same network. So I am not sure how to secure my redis instance given that these instruction are for people who install redis directly in the droplet and not by containers.
Summary: How to protect my redis instance container from the outside world and only be accessible by localhost?
cooleb09
IsaacMvd
Leon Junior
hashembarret@gmail.com
JetForMe
24608ead89f046a8abab394f968f2c
Philipp Mayerhofer
enews
Brian Magnosi
jairunet
Nikolas Jakson