Closed romelBen closed 1 month ago
Thanks for the feature request. This would likely need to be implemented as a customization similar to the generate-db-auth-token RDS command that you referenced. And that would involve coordinating with the AWS Elasticache team. I'm going to transfer this to our cross-SDK repository since customization requests like this should be considered across SDKs for consistency. Please 👍 this issue if interested in the feature request.
Duplicate of this https://github.com/aws/aws-sdk/issues/580 ? I subscribed to both since we also need this functionality, but it would be good to only track one issue.
Thanks for catching that, you're right - this does appear to be a duplicate. Closing in favor of https://github.com/aws/aws-sdk/issues/580 to continue tracking there.
This issue is now closed.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the feature
aws-cli
does not support generating a Redis AUTH token like what RDS does with commandaws generate-db-auth-token
.Use Case
Currently we have to create a token through code which is used for applications. This is understandable and is notated here in this AWS blog post; however, there is no documentation for developers to access the Redis clusters using
aws-cli
only RDS.Proposed Solution
Add another command with name
generate-redis-auth-token
foraws-cli
.Other Information
No response
Acknowledgements
CLI version used
2.13.36
Environment details (OS name and version, etc.)
MacOS M2 Macbook