StackExchange / StackExchange/StackExchange.Redis
[Question] Does the StackExchange Redis Client support Aws IAM Authentication
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
I am trying to use AWS IAM authentication to authenticate a connection to Elasticache redis as described here
https://docs.aws.amazon.com/AmazonElastiCache/late st/dg/auth-iam.html. To flow being that we provide an IAM authentication token using an Sig V4 Signing process. After providing the lAM role appropriate access, we use the [AWS4Signer ] (https://github.com/aws/aws-sdk-
net/blob/main/sdk/src/Core/Amazon.Runtime/Internal/A uth/AWS4Signer.cs) to sign a request and use the various authorization headers to create an auth token that we provide as the password to Redis. In this case, providing the password directly to the Password param in the ConfigurationOptions. Unfortunately the connection fails with
"StackExchange.Redis.RedisConnectionException:
The message timed out in the backlog attempting to send because no connection became available". I have tried many different methods of building the token following the Java or Python examples, but no luck.
Before I continue I wanted to confirm that this even possible with this library? There is no mention of it in documentation or code, but I imagine that this library doesn't do anything in terms of authentication and simply passes this string to elasticache, which should handle it and allow the connection. Any guidance or confirmation would be greatly appreciated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ConfigurationOptions password path and compare it with the AWS4Signer and ElastiCache IAM authentication documentation linked in the issue. The issue names no project file or test; completion would require confirming whether the client supports this flow and defining an implementation or documentation target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp, redis
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100