Ian Downard

related to #99

See also https://github.com/aburkleaux-amazon/aws-media-insights-engine/issues/6

I've not seen that error before but it looks like the error info is incomplete. Look for a line number in the log to indicate where the exception is being...

Step functions offers another possible solution for locking assets: https://aws.amazon.com/blogs/compute/controlling-concurrency-in-distributed-systems-using-aws-step-functions/

Thanks for submitting an issue for this. For what it's worth, I have not seen any cases where the default Lambda concurrency limits caused a problem in MIE.

@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.

I think this PR is okay to merge as long as the e2e test passes, but I recommend waiting until after the MIE 5.0.0 release to merge.

As a general purpose framework, MIE needs to be decoupled from any particular workflow definition. Workflow definitions therefore need to be in a separate repo. A better place for this...

Also, document how to overwrite data store for a given asset, according to this method: @app.route('/metadata/{asset_id}', cors=True, methods=['POST'], authorizer=authorizer) def put_asset_metadata(asset_id) READ: curl -L -w "%{http_code} %{url_effective}\\n" -k -X GET...

Also document how to get the workflow id for an asset: curl -L -w "%{http_code} %{url_effective}\\n" -k -X GET -H 'Content-Type: application/json' -H 'Authorization: '$MIE_ACCESS_TOKEN $WORKFLOW_API_ENDPOINT/workflow/execution/asset/ebb8d873-ae75-4b92-b632-1bc4b8f37c28 | jq