- Le plus récent
- Le plus de votes
- La plupart des commentaires
It doesn't have anything to do with free tier but the instance you'd have chosen under free tier eligible instances. As you mentioned, you are using free tier eligible EC2 instance, which can be t2.micro and it comes only with 1VCPU and 1GB of RAM. This can be pretty low for your use case.
I'd suggest you to setup CloudWatch monitoring to observe CPU, memory metrics before launching those two processes.
Once instance freezes, check cloudwatch metric and see where the resources limits are being hit. You might need to consider an instance of higher configuration. You'd typically see this behavior when CPU usage or memory is maxed out.
See Monitoring Instances using Cloudwatch for more details. With this you'd clearly know where is the problem and accordingly you'll need to do the rightsizing of EC2 instance for your use case.
You may not find a free tier eligible instance for your use case.
Hope this helps.
Comment here if you have additional questions, happy to help.
Abhishek
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 4 mois
- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
Thank you Abhishek, you were right. I played and set up a SNS + Cloudwatch. The problem was the CPU load, CPU usage hits 100% when I try to run the playbook from Jenkins. Immediately I switched to a t3-medium instance type everything ran smoothly.
Don't know why I didn't think about this before😅😅....Thank you very much, I really really appreciate your help.