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달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인