2 Answers
- Newest
- Most votes
- Most comments
1
So, I got in and so I am answering my own question. However, this may not work for everyone. I managed to connect with the person who setup the LightSail instance in question and it seems like they had changed the default SSH port on the server side and so I had to specify the correct port manually when logging in via SSH in a terminal locally.
0
I having the same issue. I was about my question then saw yours. I will share some pictures to give more context
My steps
0- Mu LightSail instance ( Ubuntu 22 )
1- Installing and Running amazon-ssm-agent
using snap
.
sudo snap install amazon-ssm-agent --classic sudo snap list amazon-ssm-agent
2- Connected to AWS system Manager.
3- Fleet Manager is empty
answered 2 years ago
Relevant content
- asked 3 months ago
- asked 2 years ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Yeah, my issue is the same, except I'm unable to access my Lightsail instance via SSH so I ran the code to add amazon ssm agent via launch script when loading a snapshot of my instance. I've been unable to find an answer in the forums that solved this.
Following the instructions in this post should work: https://repost.aws/knowledge-center/add-lightsail-to-systems-manager.
Another thing to note is that it might take a few minutes for the instance to show up in the fleet management page after it has been registered.