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).
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).
For supported instance types, please refer below:
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
RDS console bug - instance type missing and drop down empty for existing instanceasked 3 months ago
Ubuntu Serial Console Connection Vanishedasked 8 months ago
EC2 Serial Console - 500 Server Errorasked 8 months ago
This instance type is not supported for the EC2 serial consoleasked a year ago
ec2 serial console utf8asked a month ago
access the ec2 instance using ssh, ssm with iam credentialsAccepted Answerasked 2 months ago
Unresponsive ec2 instanceAccepted Answerasked 4 months ago
"This instance type does not support retrieving the latest console logs"asked 6 months ago
A connection to the ECC2 t2 micro instance could not be establishedAccepted Answerasked 4 months ago
EC2 instance stopping non-repsonsiveasked 9 months ago