3 Answers
- Newest
- Most votes
- Most comments
0
This happened to me as well. I was running a t2 instance. Apparently that is not one of the supported instances:
T2 is not in that last (T3 is - among many others).
answered 3 years ago
0
<dupe removed>
Edited by: wallazoo on Aug 10, 2021 5:21 PM - remove dupe post (or empty it at least - I don't see a way to delete it).
answered 3 years ago
0
Hi There,
For supported instance types, please refer below:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-to-serial-console.html#sc-prerequisites
For session manager, the instance needs to be ssm managed and should have ssmmessages permission and connectivity to ssmmessages endpoint. [ https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started.html ]
Hope this helps
Relevant content
- asked 4 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago