[Feature Request]: AWS IAM Authentication credentials provider

Problem description

RedisInsight has no way to automatically generate and rotate AWS IAM authentication tokens when connecting to Amazon ElastiCache.

IAM auth tokens are SigV4 pre-signed URLs with a 15-minute TTL, passed as the AUTH password with the ElastiCache user ID as the username.

Because RedisInsight only accepts a static password, the connection fails with an auth error after 15 minutes.

AWS recommends clients implement a credentials provider interface to handle token rotation transparently for long-lived connections. (Ref - https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/auth-iam.html)

How often do you encounter this problem

Every time RedisInsight is used to connect to an ElastiCache cluster configured with IAM authentication (RBAC).

Alternatives considered

Periodically restarting the RedisInsight Docker container with a freshly generated token passed via RI_REDIS_PASSWORD.

This requires scripting a loop that regenerates the SigV4 token and restarts the container every 14 minutes, which is fragile, requires AWS CLI/SDK tooling outside of RedisInsight, and loses any active workbench state on each restart.

Additional information

No files or tests are named. Start with the AWS ElastiCache IAM authentication documentation and trace RedisInsight’s existing connection credential handling; done means supporting SigV4 token generation and transparent rotation for long-lived connections without requiring container restarts.