ecs-files-composer VS aws-secrets-manager-rotation-lambdas

I have an app where I used Files-Composer as the container that gets the secrets. In there I have a Jinja2 template for the final fine, and the files-composer just renders the config file into a docker volume that is then shared with the main app (once it is finished). That way for apps that do not support to use env vars to set properties, you have a way around it :)

Enough talking about it from me, please post back some feedback and open Feature Requests on GH.

Create a new Lambda function that will handle the rotation - here is a template https://github.com/aws-samples/aws-secrets-manager-rotation-lambdas/blob/master/SecretsManagerRDSMySQLRotationMultiUser/lambda_function.py - I created it in a separate folder within the same repository. If you are like me, new to using Python, you could use this helpful guide:https://docs.aws.amazon.com/lambda/latest/dg/python-package.html.

One extra benefit of using Secrets Manager is that you can enable secret rotation. You can find reference implementations for the rotation lambda here https://github.com/aws-samples/aws-secrets-manager-rotation-lambdas

I would like to deploy SecretsManagerRDSPostgreSQLRotationMultiUser lambda with terraform; meaning I would store source code of lambda linked above in my repository and use terraform to package it into zip file, including dependencies and then upload it to AWS.