1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
The logs that will tell you the root cause of your problem are likely to be found in the Fargate Task Cloudwatch Logs.
If you want to check out an end-to-end solution, you can look at https://github.com/aws-samples/aws-genai-llm-chatbot which uses AWS Batch + Fargate and not Fargate directly.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
If the Fargate task is correctly started, you should be able to find the reason for the issue in the Fargate task logs.