2 Answers
- Newest
- Most votes
- Most comments
0
Hi,
I solved doing these steps
#mkdir /tmp/ssm
#systemctl stop snap.amazon-ssm-agent.amazon-ssm-agent.service
#systemctl start snap.amazon-ssm-agent.amazon-ssm-agent.service
And check you have activity in the log file tail -f /var/log/amazon/ssm/amazon-ssm-agent.log
If you are not sure, using console go to AWS System Manager --> Managed Instances and check it.
Regards.
answered 5 years ago
0
This should probably just trigger a warning rather than an error, since the config file doesn't exist, I'm assuming amazon-ssm-agent is operating based on default values and that's not really an error in itself.
answered 8 months ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago