AWSOverview
It is recommended to have one IAM role per each Lambda function in order to follow the Principle of Least Privilege.
This way you can ensure that your Lambda functions will have the minimum privileges needed to perform the required tasks.
Remediation guidance
AWS remediation
Console
- Identify Lambda functions sharing an execution role.
- Create one least-privilege role per function.
- Update each function to use its dedicated role.
AWS CLI
aws lambda update-function-configuration \
--function-name <function-name> \
--role arn:aws:iam::<account-id>:role/<dedicated-lambda-role>
References
- https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html
- https://docs.aws.amazon.com/cli/latest/reference/lambda/update-function-configuration.html
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
AWS Lambda functions do not share the same AWS IAM execution role
Connectors
AWS
Covered asset types
Function
Expected check: eq []
{AWSIAM21{...AssetFragment}}
