Skip to main content

​
More Info:

Checks if the Lambda function is configured with a function-level concurrent execution limit. The rule is NON_COMPLIANT if the Lambda function is not configured with a function-level concurrent execution limit.

​
Risk Level

Medium

​
Address

Configuration

​
Compliance Standards

  • APRA CPS 234 (Australia)
  • BSI C5 (Germany)
  • Brazil LGPD
  • CCPA / CPRA (California)
  • CIS Critical Security Controls v8
  • CMMC 2.0
  • CSA Cloud Controls Matrix v4
  • Cloudanix Best Practice
  • DPDPA
  • Digital Operational Resilience Act (EU)
  • ISO/IEC 27017
  • ISO/IEC 27018
  • ISO/IEC 27701
  • KSA PDPL
  • MAS Technology Risk Management (Singapore)
  • MITRE ATT&CK (Cloud)
  • NIS2 Directive
  • NIST SP 800-171
  • NYDFS 23 NYCRR 500
  • Reserve Bank of India (RBI) Master Direction – Information Technology Framework
  • SWIFT Customer Security Controls Framework
  • Sarbanes-Oxley IT General Controls
  • UK NCSC Cyber Assessment Framework

​
Triage and Remediation

​
Remediation

Using Console

To remediate the misconfiguration of AWS Lambda not having Concurrency configured, follow these steps using the AWS Management Console:
  1. Sign in to the AWS Management Console: Go to https://aws.amazon.com/ and sign in to your AWS account.
  2. Navigate to AWS Lambda: Click on the “Services” dropdown at the top left corner of the console, then select “Lambda” under the “Compute” section.
  3. Select the Lambda Function: From the list of Lambda functions, select the function that you want to configure Concurrency for by clicking on its name.
  4. Configure Concurrency: In the function’s configuration page, scroll down to the “Concurrency” section and click on the “Edit” button.
  5. Set Concurrency Limit: In the Concurrency settings, you can set the maximum number of concurrent executions allowed for the Lambda function. Enter the desired value in the “Reserved concurrency” field. You can also set the “Unreserved concurrency” if needed.
  6. Save Changes: After entering the concurrency limit, click on the “Save” button to apply the changes.
  7. Verify Configuration: Once saved, verify that the Concurrency configuration is correctly set by checking the Concurrency section on the Lambda function’s configuration page.
By following these steps, you have successfully remediated the misconfiguration of AWS Lambda not having Concurrency configured. This will help in controlling the maximum number of concurrent executions for the Lambda function.

​

To remediate the misconfiguration of AWS Lambda not having concurrency configured, follow these steps using AWS CLI:
  1. List all the Lambda functions to identify which functions do not have concurrency configured:
  1. For each Lambda function identified in the previous step, set the concurrency limit using the following command:
Replace <function-name> with the actual name of the Lambda function and <concurrency-limit> with the desired maximum number of concurrent executions allowed for the function.
  1. Verify that the concurrency configuration has been successfully applied by describing the function and checking the concurrency settings:
By following these steps, you can remediate the misconfiguration of AWS Lambda functions not having concurrency configured using AWS CLI.
To remediate the misconfiguration of AWS Lambda not having concurrency configured, you can follow these steps:
  1. Open the AWS Management Console and navigate to the AWS Lambda service.
  2. Select the Lambda function for which you want to configure concurrency.
  3. In the function configuration page, scroll down to the “Concurrency” section.
  4. Click on the “Edit” button next to the “Concurrency” section.
  5. In the “Edit Concurrency” dialog box, you can set the maximum number of concurrent executions for the Lambda function. You can set a value between 1 and 1000.
  6. Once you have set the desired concurrency limit, click on the “Save” button to apply the changes.
  7. You can also configure the reserved concurrency for the Lambda function if you want to ensure that a specific number of concurrent executions are always available for the function.
  8. After configuring the concurrency settings, monitor the Lambda function to ensure that it is operating within the specified concurrency limits.
By following these steps, you can remediate the misconfiguration of AWS Lambda not having concurrency configured.
This change does not force replacement of the Lambda function; Terraform will update the function’s reserved concurrency in place.To verify, terraform plan should show an update to the aws_lambda_function.THIS_FUNCTION resource with reserved_concurrent_executions changing from null (or its previous value) to your chosen integer (e.g., 10).