Rule: Lambda Functions Concurrent Execution Limit Configured
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 |
Lambda Functions Concurrent Execution Limit
The Lambda Functions Concurrent Execution Limit is a policy implemented to adhere to the requirements of NIST 800-53 Revision 5. This policy helps organizations regulate and control the maximum number of concurrent executions allowed for AWS Lambda functions. By setting a limit on concurrent executions, organizations can ensure the efficient utilization of resources, prevent overload, and maintain system stability.
Policy Description
The policy specifies the maximum number of concurrent executions allowed for Lambda functions. When the specified limit is reached, no new Lambda function invocations will be executed until there is an available execution slot.
Policy Details
To implement the policy, you need to set the concurrent execution limit for Lambda functions in accordance with NIST 800-53 Revision 5. The specific details for implementing this policy may vary depending on your organization's requirements. However, the following steps provide a general guideline:
- 1.Identify the maximum number of concurrent executions that align with your workload and resources.
- 2.Determine the desired concurrency limit (e.g., 100 concurrent executions).
- 3.Configure the concurrent execution limit for your Lambda functions using the AWS Management Console, AWS CLI, or AWS SDKs.
- 4.Monitor the concurrency usage of your Lambda functions to ensure the limit is sufficient and adjust if necessary.
Troubleshooting
If you encounter any issues related to the concurrent execution of Lambda functions, the following troubleshooting steps may help:
- 1.Verify the concurrency limit set for the Lambda functions by checking the AWS Management Console, AWS CLI, or AWS SDKs.
- 2.Review the error messages received during Lambda function invocations. If the error indicates a concurrency limit exceeded, consider increasing the concurrent execution limit.
- 3.Monitor the usage of resources and throughput of your Lambda functions to identify any bottlenecks or performance-related issues.
- 4.If you have reached the concurrency limit and want to prioritize certain functions, consider using reserved concurrency for specific functions that require higher priority or guaranteed execution slots.
Necessary Code Examples
When using the AWS CLI to configure the concurrent execution limit for Lambda functions, you can use the following command:
aws lambda put-function-concurrency --function-name <FunctionName> --reserved-concurrent-executions <ConcurrencyLimit>
Replace
<FunctionName><ConcurrencyLimit>Remediation Steps
To remediate any issues or adjust the concurrent execution limit for Lambda functions, follow these steps:
- 1.Identify the specific Lambda function(s) for which you want to adjust the concurrency limit or resolve any concurrency-related issues.
- 2.Determine the desired concurrent execution limit for the specific function(s).
- 3.Use the appropriate method (AWS Management Console, AWS CLI, or AWS SDKs) to modify the concurrency limit for the Lambda function(s).
- 4.Test the changes by invoking the Lambda functions and monitoring the concurrent execution usage to ensure it aligns with the desired limit.
- 5.If necessary, repeat this process for other Lambda functions or adjust the concurrency limits as needed.
Remember to regularly monitor the concurrency usage and adjust the limits accordingly based on your organization's evolving requirements.
By implementing and managing the Lambda Functions Concurrent Execution Limit policy according to the guidelines outlined above, organizations can effectively control and optimize the concurrent execution of their Lambda functions, aligning with the requirements of NIST 800-53 Revision 5.