Open Great-Stone opened 1 year ago
This is definitely need!
If this is implemented, Vault can be used more with AWS Account management case.
In my case This feature is very necessary and important.
Because aws accesskey is not immediately available upon creation. This is because there is a slight delay when Accesskey is activated and used. I don't know the exact time, but in my case it took about 10 seconds after rendered template destination by file.
This is a consideration in all cases where you want to automatically rotate accesskeys. Accesskey should be generated ahead of the pre-activation time to give users minimal delay.
Is your feature request related to a problem? Please describe. There is a problem when templating AWS iam_user method dynamic secret with Vault Agent. For example, if you configure ttl and max_ttl to be 60 seconds, the revoke will happen first and there will be no iam_user created by Vault. Is it possible to add something like create_and_revoke options?
Describe the solution you'd like
Describe alternatives you've considered N/A
Explain any additional use-cases Dynamically issuing the iam_user method seems to be a great advantage of vault, but unfortunately, there seems to be no consideration related to delay in issuing iam_user. For the Azure Client, the delay is more than 10 seconds.
Additional context ..