Splunk container on EC2 always getting deleted

0

Hi guys, I am running Splunk on a container on EC2 (t2.macro), and I am always getting the same error where my EC2 is crushing (I cannot connect to it via SSH or Instance Connect) and after rebooting, the container is getting deleted from the machine. Does anyone know what can be the problem?

Mor
已提问 2 个月前218 查看次数
1 回答
0

Hello.

I don't know for sure since I haven't looked at your actual EC2 metrics or load situation, but in general, t2.micro is an instance type with very small specs.
https://aws.amazon.com/ec2/instance-types/t2/?nc1=h_ls

Also, since it is a T-based instance type, CPU credits will be consumed when the load is high.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances.html

Therefore, the cause may be that running the container exceeds the EC2 baseline throughput and continues to consume CPU credits, causing the performance to drop to the baseline throughput.
I recommend checking the CPU credit metrics in CloudWatch metrics.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html#cpu-credit-metrics

profile picture
专家
已回答 2 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则