Lambda Function Concurrent Execution Limit Configured Rule
This rule checks if the concurrent execution limit is configured for Lambda functions.
| Rule | Lambda functions concurrent execution limit configured |
| Framework | NIST 800-53 Revision 5 |
| Severity | ✔ Low |
Rule Description:
The AWS Lambda service allows users to run code without provisioning or managing servers. In order to maintain performance and prevent resource exhaustion, AWS sets a concurrent execution limit for Lambda functions. The NIST 800-53 Revision 5 is a security and compliance framework that outlines specific guidelines for managing Lambda function concurrency.
Rule Details:
The NIST 800-53 Revision 5 specifies that the number of concurrent executions of Lambda functions must be limited to an acceptable level in order to prevent any potential performance degradation or resource exhaustion. By properly configuring the concurrent execution limit, it ensures the stability and availability of Lambda functions.
Remediation:
To remediate this rule and ensure compliance with the NIST 800-53 Revision 5, follow the steps provided below:
Step 1: Identify the Concurrency Limit:
Determine the maximum concurrency limit that aligns with your application's requirements and the resources available. This limit should be defined based on factors such as expected traffic, function complexity, and available memory.
Step 2: Update Function Configuration:
- 1.Open the AWS Management Console and navigate to the Lambda functions dashboard.
- 2.Select the Lambda function for which you want to configure the concurrency limit.
- 3.Click on the "Configuration" tab to access the function's settings.
- 4.Scroll down to the "Concurrency" section and click on the "Edit" button.
- 5.In the "Reserved concurrency" field, enter the desired number of concurrent executions or leave it blank for unreserved concurrency (up to the account level limit).
- 6.Click "Save" to apply the changes.
Step 3: Test and Monitor:
- 1.Monitor the function's concurrency usage and observe its behavior under different loads.
- 2.Perform load testing to ensure that the defined limit is appropriate and that the function performs as expected.
- 3.Continuously monitor and adjust the concurrency limit as needed to maintain optimal performance.
Troubleshooting:
If you encounter any issues while configuring or managing the concurrency limit for Lambda functions, consider the following troubleshooting steps:
- 1.
Validation Errors: If you receive an error while saving the concurrency limit, check that you have appropriate permissions to modify function configurations. Ensure that the entered value is within the acceptable range and does not exceed your account or resource limits.
- 2.
Performance Issues: If you experience performance degradation even after setting an appropriate concurrency limit, consider reviewing the code within the Lambda function itself. Optimize the function's code and resource allocation to achieve better performance.
- 3.
Monitoring and Alerts: If you are unable to track concurrency usage or receive alerts for high utilization, ensure that you have enabled CloudWatch metrics and alarms for Lambda functions. Configure appropriate monitoring thresholds and notifications for early detection of concurrency-related issues.
Conclusion:
Configuring the concurrent execution limit is crucial for maintaining the stability and performance of Lambda functions while adhering to the NIST 800-53 Revision 5 guidelines. By following the remediation steps and troubleshooting recommendations, you can successfully implement and manage the concurrent execution limit for your Lambda functions.