Here's an SST design question, why does SST need to create a new IAM role for each Lambda function even though the roles each appear different? Clearly you need one for each stage and region as the resources will be different in those cases, but for each Lambda function of which I have many SST is creating an identical Role. Obviously if you have customized resources for each Lambda they need different roles, but in my case they all have the same IAM requirements.

It's a bit hard for us to analyze all your functions and figure out which ones have the same requirements and generate a shared role

It was more a curiosity than an issue, as I have 212 roles in my account at the moment, and it just seemed like a lot. Since I am not manually managing them, it doesn't hurt me, and the only time it would impact a deployment length would be if one changed if I understand how things work correctly.

Hey @Michael Robellard here’s an example of re-using the same role for all routes in an Api https://docs.serverless-stack.com/constructs/Api#using-1-role-for-all-routes