xpk/code-dumps
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

DOC: updated comment for elasticache-iam-auth.py

Browse Source
This commit is contained in:
xpk
2025-08-11 23:07:56 +08:00
parent d5e24c4825
commit 33a976be9a
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
py/elasticache-iam-auth.py
+6 -1
View File
@@ -2,10 +2,15 @@
""" """
When elasticache valkey is deployed without encryption in transit, IAM auth cannot be used. When elasticache valkey is deployed without encryption in transit, IAM auth cannot be used.
To enable TLS after deployment, it takes 20min to set it to prefer TLS, and another 5 min to set it to require To enable TLS after deployment, it takes 20min to set it to prefer TLS, and another 5 min to set it to require TLS.
When TLS is enabled, configuration endpoint address is changed When TLS is enabled, configuration endpoint address is changed
IAM auth is available only after TLS is required. One needs to manually associate the cluster with the elasticache usergroup IAM auth is available only after TLS is required. One needs to manually associate the cluster with the elasticache usergroup
It took me a day to figure out how to connect to elasticache/valkey using iam auth, even with help from perplexity. It should
not be this difficult.
The following code is based on valkey's example, which for some reason did not enable TLS.
Other considerations Other considerations
* Elasticache userid must be the same as username * Elasticache userid must be the same as username
* The signed request must have validity of 15min * The signed request must have validity of 15min