I might have preferred to use SAM, which uses CF under the hood but is much more focused on getting lambdas to work. I'd pass in DB settings as parameters to t

I might have preferred to use SAM, which uses CF under the hood but is much more focused on getting lambdas to work. I'd pass in DB settings as parameters to the SAM file, rendering them as env. variables for the lambdas. with DB access managed by IAM roles (so you don't need sensitive info in the lambda env). And depending on size/scope of project/team, might have one CF for the DB infra, and another for the app lambdas. Using IaC services means I can have both dev and prod infra, so I can test DB migrations. And I can do this as a solo dev on a side project where I'm also responsible for front-end and the other back-end stuff plus keeping clients happy on evenings/weekends.