search

awslabs / genai-bedrock-chatbot

A demo application that uses Amazon SageMaker manuals and pricing data tables as an example to explore the capabilities of a generative AI chatbot.
https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/develop-advanced-generative-ai-chatbots-by-using-rag-and-react-prompting.html
MIT No Attribution
32 stars 9 forks source link

CDK Deployment Fails #3

Closed quadrupole closed 9 months ago

quadrupole commented 9 months ago

I get the following error in my cloudformation stack events when deploying: 

Resource handler returned message: "Resource of type 'AWS::ApplicationAutoScaling::ScalableTarget' with identifier 'service/chatbot-stack-dev-ecs-cluster/chatbot-stack-dev-chatbot-service|ecs:service:DesiredCount|ecs' was not found." (RequestToken: 6e97d684-000d-618a-8779-07f0a3b6be46, HandlerErrorCode: NotFound)

Is this a known issue? As far as i can tell I am following the tutorial correctly

cdk --version                                                                                                                                                                                                                           
2.115.0 (build 58027ee)

Any ideas? Furthermore I observe that the deployment takes quite a considerable amount of time ~25min before I reach the error. Is this expected?

praveenflash commented 9 months ago

Yes, it takes approximately 30 min since the creation of Kendra index takes long time.

It seems the container is crashing. Can you provide the container logs here?

quadrupole commented 9 months ago

Thanks for your response. I destroyed the stack and redeployed, and the deployment ran to completion. Could it have had something to do with Load balancer resources not being available on the first time round due to lag?

praveenflash commented 9 months ago

Could be, not sure. Logs are the only source to check this out.

quadrupole commented 9 months ago

Where can I access the logs you are thinking of? I did not see anything suspicious in the terminal output, but happy to take a look and try to reproduce the error!