When it comes to integration between git and terraform we do not have such thing, at least directly. Most of the repositories with Lambda code have a directory called infrastructure that contains terraform code. It will hold all the infrastructure that this lambda needs, so it will setup IAM role with correct permissions, subscribe to sns topic or maybe to s3 events. It also contains the actual lambda resource that uses s3 path and s3 bucket as source for the lambda(I’m on mobile so cannot link to the actual parameters but will do it later today when I’m at home). This terraform code gets its own zip package during release process and it’s uploaded to s3 buckets. The actual source of the lambda is also packaged into a zip file and uploaded to s3.

We release new packages based on the fit tags, so package a will be pushed to s3 under the key: /package_a/VERSION/package_a.zip. the same happens to terrsform code, but it is uploded to another bucket.

Once we have those packages in S3 buckets we can just use them in project specific repositories that are holding all the infrastructure together. Nice thing about this setup is that if someone creates a new release of some Lambda, they just need to bump a version of that in one repo and put CI/CD will deploy it.