Redis Enterprise 6.2.4 introduced internode encryption with the use of a Private Certificate Authority (CA) to manage certificates for internode connections, aiming to maintain high availability and operational simplicity while meeting compliance requirements. The system uses a shared-nothing architecture, increasing reliability and availability, and allows for automatic certificate rotation before expiration or upon request through the REST API. A self-signed certificate is not required in this context, as each node already trusts every other node within the same cluster, making a third-party trusted CA unnecessary to establish trust. This approach addresses compliance concerns related to using self-signed certificates while providing an alternative solution that maintains security without adding unnecessary dependencies.