You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding the Lambda Insights extension, we started to see the following warning during stack synthesis:
[Warning at /challenge-staging-stateless/challenge-staging-lambdas/Role] Policy too large: 91 exceeds the maximum of 20 managed policies attached to a Role
However, the generated CloudFormation template does not contain that many policies, and there is only one policy CloudWatchLambdaInsightsExecutionRolePolicy attached to the Lambda Execution Role, also there is no error during the deployment process.
It is important to note that all Lambda functions in the stack share the same Role. I think if we used separate, auto-generated roles for each lambda function, we wouldn't even see this warning, but that's what we have at the moment, and we can't understand why there is a discrepancy between this warning and the actual CloudFormation template.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After adding the Lambda Insights extension, we started to see the following warning during stack synthesis:
[Warning at /challenge-staging-stateless/challenge-staging-lambdas/Role] Policy too large: 91 exceeds the maximum of 20 managed policies attached to a Role
However, the generated CloudFormation template does not contain that many policies, and there is only one policy
CloudWatchLambdaInsightsExecutionRolePolicy
attached to the Lambda Execution Role, also there is no error during the deployment process.It is important to note that all Lambda functions in the stack share the same Role. I think if we used separate, auto-generated roles for each lambda function, we wouldn't even see this warning, but that's what we have at the moment, and we can't understand why there is a discrepancy between this warning and the actual CloudFormation template.
Is anyone familiar with this problem?
Thank you!
Language:
Python
CDK version:
[email protected]
Node:
v16.13.0
OS
macOS, Ubuntu
Beta Was this translation helpful? Give feedback.
All reactions