Allow the connection scheme (redis or rediss) to be defined using an environment variable to support ElastiCache with Valkey and SSL. #8832
Description
New feature motivation
Currently, when attempting to use AWS ElastiCache with Valkey, it is necessary to connect using SSL (rediss://). However, Prowler only considers the redis:// string by default, which prevents direct integration with clusters that require secure connections.
This creates limitations when deploying Prowler in production environments where security policies require the use of SSL/TLS for communication with Redis/Valkey in ElastiCache.
Solution Proposed
Add a new environment variable that allows you to specify the connection scheme, for example:
VALKEY_SCHEME=redis # connection without SSL
VALKEY_SCHEME=rediss # connection with SSL
This would maintain compatibility with current environments (redis) and enable support for secure connections (rediss), allowing full integration with AWS ElastiCache.
Describe alternatives you've considered
Alternatively, we tried to directly configure the connection URL by including rediss://, but the current code forces the use of redis://.
Additional context
The use of rediss is a common requirement in production environments that comply with corporate security policies and cloud regulations. Including this environment variable (VALKEY_SCHEME) would provide flexibility and avoid insecure workarounds.
This change would also facilitate the adoption of Prowler in architectures where ElastiCache with Valkey and SSL is standard.