This section describes additional configuration options for Redis Enterprise Software installation.

    Configure AWS EC2 instances for Redis Enterprise Software

    There are some special considerations that are important when installing and running Redis Enterprise Software on Amazon Web Services (AWS), whether Amazon Electric Cloud Compute (EC2) AWS Outposts. These include: Storage considerations Instance types Security group configuration Storage considerations AWS EC2 instances are ephemeral, but your persistent database storage should not be. If you require a persistent storage location for your database, the storage must be located outside of the instance.

    Configure CentOS/RHEL firewall

    CentOS/RHEL7 distributions have, by default, a restrictive firewall mechanism based on firewalld that in turn configures the standard iptables system. The default configuration assigns the network interfaces to the public zone and blocks all ports, except 22 (SSH). Redis Enterprise Software (RS) installation on CentOS/RHEL 7 automatically creates two firewalld system services: A service named redislabs, which includes all ports and protocols needed for communications between cluster nodes. A service named redislabs-clients, which includes the ports and protocols needed for communications external to the cluster.

    Configure Swap for Linux

    Swap space is used by the Linux OS to help manage memory (pages) by copying pages from RAM to disk and the OS is configured by default to be fairly aggressive. For Redis Enterprise Software (RS) with the way it utilizes and manages memory, it is best to eliminate the likelihood of the OS swapping. If you would like to understand why, please read more on how RS manages memory for best functionality and performance.

    Change socket file locations

    There are two default locations for the socket files in Redis Enterprise Software (RS): /tmp - In clean installations of RS version lower than 5.2.2 /var/opt/redislabs/run - In clean installations of RS version 5.2.2 and higher We made this change because some customers have maintenance procedures that delete the /tmp directory. When you upgrade from a RS version lower than 5.2.2 to 5.2.2 and higher, the socket files are not moved to the new location by default.