Dynamic version of Amazon Transcribe Post Call Analytics


Source: https://github.com/aws-samples/amazon-transcribe-post-call-analytics

Found the AWS solution in the source link.

By default, its behavior is configured through the inputs in the stack before you deploy it. It takes audio files uploaded to an input bucket as input to a lambda function that starts a step-function workflow.

The confusing part is that it currently has a lot of variables in the config file which stores them in ssm.

Wondering how I should go about making the input and behavior of the application more dynamic? Instead of uploading a file to trigger the workflow, have a normal lambda that points to a location for a file. Or specify what transcribe options are used etc. Do any of the configs need to be dynamically accepted as inputs?

No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions