[Enhancement]: Add Language Identification support for Transcribe Processor in ChimeSDK Call Analytics

[damews]

Description

Amazon Chime SDKCall Analytics Transcribe Processor configuration currently does not support a language identification configuration, only a specific language. The Transcribe Processor supports this through the IdentifyLanguage, LanguageOptions and PreferredLanguage parameters.

This is a valid configuration in the AWS Console

Affected Resource(s) and/or Data Source(s)

resource "aws_chimesdkmediapipelines_media_insights_pipeline_configuration" "my_configuration" {
  name                     = "MyTranscribeConfiguration"
  resource_access_role_arn = aws_iam_role.example.arn
  elements {
    type = "AmazonTranscribeProcessor"
    amazon_transcribe_processor_configuration {
      [...]
    }
  } 
}

Potential Terraform Configuration

resource "aws_chimesdkmediapipelines_media_insights_pipeline_configuration" "my_configuration" {
  name                     = "MyTranscribeConfiguration"
  resource_access_role_arn = aws_iam_role.example.arn
  elements {
    type = "AmazonTranscribeProcessor"
    amazon_transcribe_processor_configuration {
      language_identification              = true
      language_options                     = "en-US,en-GB,pt-BR"
      language_preferred                   = "en-US"
    }
  } 
}

References

TranscribeProcessorConfiguration Object for the API Terraform amazon_transcribe_processor_configuration atributte

Would you like to implement a fix?

No

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.