Currently, we heavily rely on AWS SSM to store and read secrets from. All of our services and CodePipelines use AWS SSM for fetching the secrets.Secret rotation with AWS SSM requires the use of lambda functions, it would get quite tiresome since we have large number of secrets.
We researched about HashiCorp Vault and the two features that we would like to use our Secret rotation and Dynamic secrets. The secret rotation with HashiCorp seems painless as compared to SSM secret rotation.
Is it possible to use both of them together? Basically, the secret rotation would be done by HashiCorp Vault and the new values can be written back to AWS SSM. All the services (such as ECS, Beanstalk) will need to be restarted to fetch the new secrets.
In short, does Vault provide some sort of integration for the above or do I have to include the writing back part in the same secret rotation cron job script for the Vault?