Deployment failed to Lambda concurrent executions limit

Describe the bug Initial deployment of the MIE failed with the following error:

Resource handler returned message: “Specified ReservedConcurrentExecutions for function decreases account’s UnreservedConcurrentExecution below its minimum value of [50]. (Service: Lambda, Status Code: 400, Request ID: ca621951-bdba-4e26-9f5e-d7438ca65d9a)” (RequestToken: fb976251-30fa-4556-d1a7-a28941a31f7e, HandlerErrorCode: InvalidRequest)

To Reproduce Select eu-central-1 as region, deploy the MIE with the following parameters

Expected behavior The MIE deployment should have worked.

Please complete the following information about the solution:

• Version: 4.0.1

Mappings:
  SourceCode:
    General:
      GlobalS3Bucket: "solutions-reference"
      RegionalS3Bucket: "solutions"
      CodeKeyPrefix: "aws-media-insights-engine/v4.0.1"
      TemplateKeyPrefix: "aws-media-insights-engine/v4.0.1"
      FrameworkVersion: "v4.0.1"

• Region: eu-central-1
• Was the solution modified from the version published on this repository? no
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the sevices this solution uses? yes
• Were there any errors in the CloudWatch Logs? no

Additional context The resource that results in this error is the WorkflowSchedulerLambda

[aburkleaux-amazon]

Another user encountered this issue recently. I think it has to do with variation in the default limits of the AWS account. Their account had a default for lambda concurrent executions set to 100. In my account, the default limit is 1000. Changing the limit to 1000 resolved the rollback.

[ianwow]

@cremich Someone on the MIE gitter channel also encountered this issue. I think the following line could be causing this error:

https://github.com/aws-solutions/media-insights-on-aws/blob/42f24bd615c8e3f299edd9db1b55acddcdc6889e/deployment/media-insights-stack.yaml#L1346

I recommend removing that line and redeploying.