Method 2: Use AWS Systems Manager Session Manager
#Termius timeout serial
Disconnect the EC2 Serial Console session if it's no longer required. Next, connect to the instance using SSH.ĥ. If you have iptables rules configured, then run following command to add a rule in iptables accepting all SSH connections on default port 22:Ĥ. The commands also verify that the sshd service is running and listening on port 22.ġ. These commands verify that the SSH connections aren't being blocked by the OS firewall or TCP wrapper. For more information on running ssm-user commands, see the section Managing ssm-user sudo account permissions on Linux and macOS.Īfter configuration, connect to the EC2 instance through the EC2 serial console using a password-configured Linux user.
If there isn’t a Linux account with a login password configured, you must run ssm-user to reset the password for an account with sudo access. Note: Each instance using the serial console must include at least one password-based Linux user with sudo access.įor more information on configuring the EC2 Serial Console for Linux, see Configure access to the EC2 Serial Console. Then, create AWS Identity and Access Management (IAM) policies granting access to your IAM users. The serial console is accessible using the Amazon EC2 console or the AWS Command Line Interface (AWS CLI).īefore using the serial console, grant access to it at the account level. The serial console allows troubleshooting of boot issues, network configuration, and SSH configuration issues. If configured, you can use the EC2 Serial Console for Linux to troubleshoot OS-level issues on supported Nitro-based instance types. Method 1: Use the EC2 Serial Console for Linux Method 3: Run the AWSSupport-TroubleshootSSH automation runbook.
0 kommentar(er)
