aws-samples/amazon-transcribe-live-meeting-assistant

Longer CloudFormation stack names cause errors in length of Lambda function names

moose-in-australia opened this issue · 2 comments

moose-in-australia commented

Important: Bug reports submitted here should relate specifically to the open source sample amazon-transcribe-live-meeting-assistant project. Do not submit bugs related directly to any AWS service.
If your issue relates to Amazon Transcribe, Amazon Bedrock or Amazon Bedrock Knowledge Base - setup, user provisioning, document ingestion, accuracy, or other aspects of the service, then first check the service documentation, and then reproduce the problem using the relevant AWS service console before engaging AWS support directly. Thank you.

Describe the bug
When you use a longer, more descriptive CloudFormation stack name like "LiveMeetingAssistant" instead of "LMA", the stacks fail to deploy because the name of the stack is used to generate the names of the Lambda functions. The names of these Lambda functions quickly exceed the 64 character limit. See screenshot at the end.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the README and Launch Stack button to launch the CloudFormation stack
  2. Enter LiveMeetingAssistant as the stack name instead of the default LMA
  3. Leave all other values default and create the stack
  4. Within 5-10 minutes, the stack will fail with an error message similar to the screenshot above

Expected behavior
It would be nice if the CloudFormation stack names can be a little longer and more descriptive, especially when multiple stacks are deployed in a single AWS account.

Screenshots

redacted_error

Additional context
N/A

rstrahan commented

Fix in develop branch, queued for next release. Stack Names can now be 25 characters, enforced by a custom resource check.

rstrahan commented

Fixed in v0.1.2
StackName length max is 25 characters, enforced by a custom resource in the main template. You can now use stack name of "LiveMeetingAssistant" no problem :)