https://dikapediav2.com/wiki/index.php?action=history&feed=atom&title=SSM 2026-05-16T18:27:39Z Revision history for this page on the wiki MediaWiki 1.41.0 https://dikapediav2.com/wiki/index.php?title=SSM&diff=171&oldid=prev 2024-09-11T14:26:49Z

<p>Created page with &quot; ====Run Command Troubleshooting Checklist==== ---- * Verify if the instance is online (SSM agent pre-requisites). Is the Agent up to date? * Verify if SSM document supports the type of instance you want to target (Windows and Linux) * Ask for command ID and verify the status in SSM K2 page from SSM dashboard or from Admiral page. * Check the logs and the stdout location: ** The agent also stores the script (_script.ps1) and outputs (stderr and stdout) in the worker (&lt;...&quot;</p> <p><b>New page</b></p><div><br /> <br /> ====Run Command Troubleshooting Checklist====<br /> ----<br /> <br /> * Verify if the instance is online (SSM agent pre-requisites). Is the Agent up to date?<br /> * Verify if SSM document supports the type of instance you want to target (Windows and Linux)<br /> * Ask for command ID and verify the status in SSM K2 page from SSM dashboard or from Admiral page.<br /> * Check the logs and the stdout location:<br /> ** The agent also stores the script (_script.ps1) and outputs (stderr and stdout) in the worker (&lt;b&gt;Orchestration&lt;/b&gt;) folders located at:<br /> *** /var/lib/amazon/ssm/&lt;instanceID&gt;/document/orchestration/&lt;RunCommandId&gt;/plug-in/step_number.plugin&gt;/std*<br /> <br /> /var/lib/amazon/ssm/&lt; i-xxxxxxxxxxxx&gt;/document/orchestration/&lt;command ID&gt;/awsrunShellScript/[PatchLinux or runInSpecLinux for example]/stdout<br /> <br /> /var/lib/amazon/ssm/&lt;i-instanceid&gt;/document/orchestration/&lt;command ID&gt;/awsrunShellScript/[PatchLinux or runInSpecLinux for example]/stderr<br /> <br /> # example: &quot;runInSpecLinux&quot;<br /> /var/lib/amazon/ssm/i-0bb46bc5e41a7a36b/document/orchestration/6b141723-0c4b-4726-8770-bc8eed816007/awsrunShellScript/runInSpecLinux/stdout<br /> <br /> # If the command action is aws:runCommand :<br /> /var/lib/amazon/ssm/&lt;i-instanceid&gt;/document/orchestration/&lt;command ID&gt;/awsrunDocument/&lt;stepName&gt;/std*<br /> <br /> * Manual execution from instance? <br /> * Check the Run command advanced playbooks.<br /> * Reproduce issue<br /> * Cut a TT/SIM<br /> <br /> <br /> ====Logs====<br /> ----<br /> <br /> * /var/log/amazon/ssm<br /> <br /> You can view SSM Agent logs on instances in the following locations:<br /> /var/log/amazon/ssm/amazon-ssm-agent.log <br /> <br /> /var/log/amazon/ssm/errors.log<br /> <br /> /var/log/amazon/ssm/audits/amazon-ssm-agent-audit-YYYY-MM-DD<br /> <br /> ----<br /> <br /> Checking command logs:<br /> <br /> here is path (replace instance id and command id)<br /> <br /> /var/lib/amazon/ssm/&lt;i-instanceid&gt;/document/orchestration/&lt;command ID&gt;/awsrunShellScript/PatchLinux/stdout<br /> <br /> /var/lib/amazon/ssm/&lt;i-instanceid&gt;/document/orchestration/&lt;command ID&gt;/awsrunShellScript/PatchLinux/stderr<br /> <br /> # If the command action is aws:runCommand :<br /> /var/lib/amazon/ssm/&lt;i-instanceid&gt;/document/orchestration/&lt;command ID&gt;/awsrunDocument/&lt;stepName&gt;/std*<br /> <br /> ====How to install SSM Agent====<br /> ----<br /> <br /> Manually install SSM Agent on EC2 instances for Linux <br /> https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-manual-agent-install.html<br /> <br /> <br /> <br /> ====How to reboot managed instance once by using custom Run Command document====<br /> ----<br /> <br /> Yaml template:<br /> --- <br /> description: &quot;Command Document Example JSON Template&quot;<br /> mainSteps: <br /> - <br /> action: &quot;aws:runShellScript&quot;<br /> inputs: <br /> runCommand: <br /> - |-<br /> #!/bin/bash<br /> REBOOT_INDICATOR=/var/lib/amazon/ssm/ssm-reboot-indicator<br /> echo &#039;Rebooting the host via SSM&#039;<br /> if [ ! -f ${REBOOT_INDICATOR} ]; then<br /> uptime<br /> echo &#039;rebooting... as the reboot file does not exist&#039;<br /> touch ${REBOOT_INDICATOR}<br /> exit 194<br /> else<br /> echo &#039;reboot file exist&#039;<br /> ls -l ${REBOOT_INDICATOR} <br /> uptime <br /> rm -f ${REBOOT_INDICATOR}<br /> exit 0<br /> fi<br /> name: example<br /> schemaVersion: &quot;2.2&quot;<br /> * It first checks if the reboot tracker file (/var/lib/amazon/ssm/ssm-reboot-indicator) exists in the &#039;if&#039; condition. If it does not, then it will create it, run mkfs, and then reboot it by sending out exit 194. <br /> <br /> * Once the system reboots, then it will go through the entire script again. Now since the reboot tracker does exist, it will remove the file and return exit 0. <br /> <br /> * The use of this if-else statement and the reboot tracker file helps prevent the instance from going into a reboot-loop. <br /> <br /> <br /> <br /> --- <br /> description: &quot;Command Document Example JSON Template&quot;<br /> mainSteps: <br /> - <br /> action: &quot;aws:runShellScript&quot;<br /> inputs: <br /> runCommand: <br /> - |-<br /> #!/bin/bash<br /> REBOOT_INDICATOR=/var/lib/amazon/ssm/ssm-reboot-indicator<br /> echo &#039;Mounting volume and Rebooting the host via SSM&#039;<br /> mount -a<br /> if [ ! -f ${REBOOT_INDICATOR} ]; then<br /> uptime<br /> echo &#039;Creating filesystem on /dev/nvme1n1&#039;<br /> mkfs -t ext4 /dev/nvme1n1<br /> echo &#039;rebooting... as the reboot file does not exist&#039;<br /> touch ${REBOOT_INDICATOR}<br /> exit 194<br /> else <br /> echo &#039;reboot file exist, the server has been rebooted after mounting&#039;<br /> ls -l ${REBOOT_INDICATOR}<br /> uptime<br /> rm -f ${REBOOT_INDICATOR}<br /> exit 0<br /> fi<br /> name: example<br /> schemaVersion: &quot;2.2&quot;</div>

Ardika Sulistija