AWS Documentation » AWS Systems Manager » User Guide » AWS Systems Manager Actions & Change » AWS Systems Manager Automation » Working with Automation Documents » Systems Manager Automation Documents Reference » Systems Manager Automation Document Details Reference » AWSSupport-TroubleshootSSH

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

AWSSupport-TroubleshootSSH

Description

The AWSSupport-TroubleshootSSH automation document installs the Amazon EC2Rescue tool for Linux, and then uses the EC2Rescue tool to check or attempt to fix common issues that prevent a remote connection to the Linux machine via SSH. Optionally, changes can be applied offline by stopping and starting the instance, if the user explicitly allows for offline remediation. By default, the document operates in read-only mode.

Document Type

Automation

Owner

Amazon

Platforms

Linux

Parameters

• InstanceId

  Type: String

  Description: (Required) ID of your EC2 Linux instance.

• Action

  Type: String

  Allowed values: CheckAll,FixAll

  Default: CheckAll

  Description: (Required) Specify whether to check for issues without fixing them or to check and automatically fix any discovered issues.

• AllowOffline

  Type: String

  Allowed values: True,False

  Default: False

  Description: (Optional) Fix only - Set it to true if you allow an offline SSH remediation in case the online troubleshooting fails, or the provided instance is not a managed instance. Note: For the offline remediation, SSM Automation stops the instance, and creates an AMI before attempting any operations.

• SubnetId

  Type: String

  Default: SelectedInstanceSubnet

  Description: (Optional) Offline only - The subnet ID for the EC2Rescue instance used to perform the offline troubleshooting. If no subnet ID is specified, AWS Systems Manager Automation will create a new VPC.

  Important

  The subnet must be in the same Availability Zone as InstanceId, and it must allow access to the SSM endpoints.

• S3BucketName

  Type: String

  Description: (Optional) Offline only - S3 bucket name in your account where you want to upload the troubleshooting logs. Make sure the bucket policy does not grant unnecessary read/write permissions to parties that do not need access to the collected logs.

• AutomationAssumeRole

  Type: String

  Description: (Optional) The IAM role for this execution. If no role is specified, Systems Manager Automation will use the permissions of the user that runs this document.

Examples

Check the current SSH status

aws ssm start-automation-execution --document-name AWSSupport-TroubleshootSSH --parameters "InstanceId=INSTANCEID"

Perform an online fix of all detected SSH issues

aws ssm start-automation-execution --document-name AWSSupport-TroubleshootSSH --parameters "InstanceId=INSTANCEID,Action=FixAll"

Perform an offline fix of all detected SSH issues

aws ssm start-automation-execution --document-name AWSSupport-TroubleshootSSH --parameters "InstanceId=INSTANCEID,Action=FixAll,AllowOffline=True"

Retrieve the execution output

aws ssm get-automation-execution --automation-execution-id EXECUTIONID --output text --query 'AutomationExecution.Output'

Required IAM Permissions

It is recommended that the EC2 instance receiving the command has an IAM role with the AmazonSSMManagedInstanceCore Amazon managed policy attached. For the online remediation, the user must have at least ssm:DescribeInstanceInformation, ssm:ExecuteAutomation and ssm:SendCommand to run the automation and send the command to the instance, plus ssm:GetAutomationExecution to be able to read the automation output. For the offline remediation, the user must have at least ssm:DescribeInstanceInformation, ssm:ExecuteAutomation, ec2:DescribeInstances, plus ssm:GetAutomationExecution to be able to read the automation output. AWSSupport-TroubleshootSSH calls AWSSupport-ExecuteEC2Rescue to perform the offline remediation - please review the permissions for AWSSupport-ExecuteEC2Rescue to ensure you can run the automation successfully.

Document Steps

1. aws:assertAwsResourceProperty - Check if the instance is a managed instance

   1. (Online remediation) If the instance is a managed instance, then:

      1. aws:configurePackage - Install EC2Rescue for Linux via AWS-ConfigureAWSPackage.

      2. aws:runCommand - Run the bash script to run EC2Rescue for Linux.

   2. (Offline remediation) If the instance is not a managed instance then:

      1. aws:assertAwsResourceProperty - Assert AllowOffline = True

      2. aws:assertAwsResourceProperty - Assert Action = FixAll

      3. aws:assertAwsResourceProperty - Assert the value of SubnetId

      4. (Use the provided instance's subnet) If SubnetId is SelectedInstanceSubnet us aws:executeAutomation to run AWSSupport-ExecuteEC2Rescue with provided instance's subnet.

      5. (Use the provided custom subnet) If SubnetId is not SelectedInstanceSubnet use aws:executeAutomation to run AWSSupport-ExecuteEC2Rescue with provided SubnetId value.

Outputs

troubleshootSSH.Output

troubleshootSSHOffline.Output

troubleshootSSHOfflineWithSubnetId.Output