Occasionally, we must quickly disable an AWS Lambda without removing it. It may happen when we accidentally deploy incorrect code, when a lack of input validation causes it to propagate erroneous data downstream, or when we must disable an application function for safety reasons.

When this happens, we don’t need to remove the lambda function or its triggers. That would be a terrible solution because we would have to restore it later, and that may create more bugs. Instead of that, we can use the concurrency configuration to prevent the function from running.

If the concurrency is set to 0, the function will not run.

aws lambda put-function-concurrency --function-name function_name --reserved-concurrent-executions 0
Older post

How to add an EMR step from AWS Lambda

How to configure a new EMR step using AWS Lambda in Python

Newer post

How to configure both core and spot instances in EMR using Terraform

Use EMR instance group to add spot instances to an EMR cluster