- Newest
- Most votes
- Most comments
Hi JonasL,
Thank you for posting here. Could you please provide the following information to help us investigate this issue?
- Instance type
- AMI id
- Region
- Logs about amazon-ssm-agent
Sure:
AMI id - amzn-ami-2017.09.f-amazon-ecs-optimized (ami-acb020d5)
Instance type - m5.xlarge
Region - eu-west-1
Logs attached
Turns out there was a bug in the executable that the ssm-agent tried to restart. This caused the ssm-agent to re-try to execute the script even though it was failing - causing the 100% cpu.
Hi JonasL,
Base on the log, there are over 180 command executions within 2 mintues. All the commands have the same content, all excutions completed with failed status (no retry).
The high CPU usage was related to the nubmer of the commands have been executed.
Do you have configuration (StateManager, CloudWatch) that sends commands to the instance after restart?
Regards,
Shihua
Relevant content
- asked 2 years ago
- asked a year ago
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago