Ian Downard

Option 3: Operators can be created via a POST to WORKFLOW_API_ENDPOINT/workflow/operation. Those calls include parameters for StartLambdaArn and MonitorLambdaArn, and the StepFunctionRole is provided in os.environ, so we have everything...

The only problem with *Option 3* is an IAM quota that limits us from adding more than 10 policies to a role. We have no limit on the number of...

Option 3 is not going to work because quotas. Option 2 is ineffective because it contains a wildcard, and therefore no better than what StepFunctionRole already uses. Option 1 is...

We should use inline policy, not managed policy for option #3. Thanks Brandon for bringing that to my attention. The inline policy approach will work!

Turns out, inline policies won't work either because we will too easily exceed the maximum length for inline policies. [The aggregate inline policy size must not exceed 10,240 bytes](https://aws.amazon.com/premiumsupport/knowledge-center/iam-increase-policy-size/). If...

The limitation is 10,000, not 1000. Related to aws-solutions/aws-media-insights-engine#93

> @ianwow could you add s screenshot of StepFunctions, so that I could get a better view which will help me to quickly get to the code pieces. > I...

Depends on https://github.com/awslabs/aws-media-insights-engine/pull/176. Lets revisit this PR when that PR has been merged into MIE.

We also need to add front-end validation for images to the github pr-workflow. That should be done alongside this PR. Here's the issue to track that: https://github.com/awslabs/aws-media-insights/issues/73