How do I troubleshoot SSH connection issues using AWSSupport-TroubleshootSSH automation workflow?
How do I troubleshoot SSH connection issues using AWSSupport-TroubleshootSSH automation workflow?
Skip directly to the demo: 0:27
For more details see the Knowledge Center article with this video: https://repost.aws/knowledge-center/e…
Jason shows you how to troubleshoot SSH connection issues using the AWSSupport-TroubleshootSSH automation workflow.
Subscribe:
More AWS videos - http://bit.ly/2O3zS75
More AWS events videos - http://bit.ly/316g9t4
#AWS
Content
0.38 -> [Music]
12.32 -> hello i'm jason
13.44 -> a cloud support engineer here at the aws
15.679 -> office in dublin
16.8 -> today i'm going to show you how you can
18.24 -> troubleshoot ssh connection issues
20.56 -> with your amazon alas to compute cloud
22.64 -> instances using aws systems manager
25.599 -> let's get started we can use the awf
28.56 -> support troubleshoot ssh systems manager
30.88 -> document to troubleshoot errors when
32.64 -> connecting with ssh
34.239 -> such as permission denied or connection
36.32 -> refused
39.6 -> after logging into the aws management
41.52 -> console navigate to the systems manager
44 -> automation console
51.76 -> select execute automation
55.6 -> search for ssh in the list of documents
59.84 -> and then select the aws support
62.239 -> troubleshoot ssh document
65.36 -> select next
72.56 -> if your ec2 instance is currently online
74.88 -> and managed by systems manager
76.64 -> then you can select your instance from
78.32 -> the list
80.24 -> or if not you can enter the instance id
82.64 -> manually
84.24 -> in this example we'll troubleshoot an
85.759 -> offline ec2 instance
90 -> for action choose fix all
94.24 -> if your instance is online and managed
96.32 -> by systems manager
97.439 -> you can leave the default values for the
99.6 -> allow offline
100.64 -> subnet id and s3 bucket name parameters
105.68 -> however if your instance is offline are
107.759 -> not managed by systems manager
109.759 -> set allow offloading to true or subnet
113.119 -> id choose a subnet id which allows
116 -> access to the required ssm endpoints by
118.88 -> means of the internet or
120.399 -> vpc endpoints the default value
123.6 -> selected instant subnet will use is the
125.759 -> same subnet that the instance is
127.36 -> currently in
129.36 -> for offline instances you can also
131.36 -> specify an amazon simple storage service
134.08 -> bucket
134.72 -> in the s3 bucket name parameter to send
137.599 -> troubleshooting logs to
144.16 -> for automation assume role you can
146.319 -> optionally specify an aws identity and
148.8 -> access management role
150.08 -> with permissions for the execution to
151.84 -> run otherwise your current user
154.08 -> permissions will be used
156.08 -> choose execute
161.12 -> while the automation runs review each of
163.2 -> the steps output to monitor the
165.04 -> troubleshooting progress
179.92 -> after the automation completes
181.44 -> successfully try to connect your
183.28 -> instance again
184.239 -> using ssh
197.519 -> now you know how to use aws systems
199.599 -> manager automation to troubleshoot ssh
202 -> connection issues on your ec2 instances
205.599 -> thanks for watching and happy cloud
207.12 -> computing from all of us here at aws
215.44 -> you
Source: https://www.youtube.com/watch?v=QuyFwrXheMw