You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aws-cli does not support generating a Redis AUTH token like what RDS does with command aws 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 for aws-cli.
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
CLI version used
2.13.36
Environment details (OS name and version, etc.)
MacOS M2 Macbook
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: