aws-samples / amazon-transcribe-post-call-analytics

Apache License 2.0
74 stars 60 forks source link

Cloud Formation Failure on SSM module #257

Closed knightfoxapps closed 1 month ago

knightfoxapps commented 5 months ago

I keep getting this error when running the CloudFormation:

Embedded stack arn:aws:cloudformation:us-east-1:679819004921:stack/PostCallAnalytics-version2-SSM-14XZ7KY58ACHE/7e0cfda0-07cf-11ef-b9bd-0affc2bcb0d7 was not successfully created: The following resource(s) failed to create: [TranscribeApiModeParameter, TelephonyCTRFileSuffixParameter, FilenameGUIDRegexParameter, SupportFilesBucketNameParameter, EntityRecognizerEndpointParameter, FilenameDatetimeFieldMapParameter, TranscribeLanguagesParameter, BulkUploadBucketParameter, MaxSpeakersParameter, ConversationLocationParameter, DatabaseNameParameter, MinSentimentNegativeParameter, VocabFilterNameParameter, InputBucketRawAudioParameter, ContentRedactionLanguagesParameter, SpeakerSeparationTypeParameter, CustomLangModelNameParameter, OutputBucketParsedResultsParameter, ComprehendLanguagesParameter, BulkUploadStepFunctionNameParameter, OutputBucketNameParameter, InputBucketFailedTranscriptionsParameter, InputBucketNameParameter, EntityTypesParameter, VocabFilterModeParameter, StepFunctionNameParameter, InputBucketOrigTranscriptsParameter, CallRedactionTranscriptParameter, FilenameDatetimeRegexParameter, TelephonyCTRTypeParameter, VocabularyNameParameter, FilenameAgentRegexParameter, MinSentimentPositiveParameter, EntityThresholdParameter, BulkUploadMaxTranscribeJobsParameter, BulkUploadMaxDripRateParameter, InputBucketAudioPlaybackParameter, OutputBucketTranscribeResultsParameter, CallRedactionAudioParameter, FilenameCustRegexParameter, KendraIndexIdParameter, SpeakerNamesParameter, EntityStringMapParameter].

kishd commented 5 months ago

Hello Egbert, I'd recommend looking through the stack (including nested stacks) to identify a particular resource that FAILED. The rest of them would have failed because the first failed resource triggered a rollback and the resource creation for other resources got canceled. If you can pinpoint that first resource that failed and share the error, we would be able to provide better guidance.

knightfoxapps commented 5 months ago

my main issue now is this one: 2024-05-01 11:06:16 UTC-0500 SupportFilesBucket
CREATE_FAILED

kishd commented 5 months ago

You have more than the allowed number of S3 buckets in your account. I would suggest either removing the unused buckets or request a quota increase. You can find the instructions here: https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html

knightfoxapps commented 5 months ago

i solved my S3 issue but I am back at square 1 with the same issue i reported up top. It fails with the SSM. Screenshot 2024-05-01 at 8 38 16 PM

kishd commented 5 months ago

You will have to navigate to the nested stack PostCallAnalytics-version2-SSM-XXXXXX and identify the resource that failed to create (The first failure event under the Events tab). Note that the events are shows most recent first so you need to navigate down to find the first occurrence of the CREATE_FAILED event. I suspect you already have an existing deployment of PCA or one that didn't completely rollback. If that is the case, I would first clean up the older stack and retry.

knightfoxapps commented 5 months ago

im not getting an issue in any of the nested tasks that are running. they complete but then the main one creates this SSM error and fails. What is the SSM stack which gets created after the LLM Prompt is completed. The other one I see fail is the Bedrock Boto3 Layer.

kishd commented 5 months ago

The stacks may have rolled back and deleted. Choose the "Deleted" dropdown under stacks and look through the nested stacks (SSM and perhaps the Boto3 Layer first, then the rest of the nested stacks).

You have to find the CREATE_FAILED event that triggered the stack to rollback and provide the failure reason to be able to further troubleshoot the issue.

rstrahan commented 1 month ago

Thread has gone quiet.. Closing for now, but please reopen if issue remains.