These instructions are not working in my case. And I am testing them with a new instance created from scratch, using DEBIAN 11 template from Amazon Lightsail itself (available images). I also read other posts like this one: https://repost.aws/questions/QUC6_b2TEHTcqDR5rC3ZvrSg/adding-lightsail-instance-to-aws-systems-manager-didn-t-show-in-fleet-manager and the final comments on it didn't help me. I am still testing Lightsail platform and interface, so I wanted to understand this mechanism of troubleshoot an Instance via AWS Systems Manager (just in case), before proceeding to deploy production instances in Lightsail.
By the way, this is the constant error I get after running those commands (again, brand new Debian instance, nothing installed on it, not even firewall):
> sudo -E amazon-ssm-agent -register -code 'xxxxxxx' -id 'xxxxxx' -region 'us-east-1a' <br>
> Error occurred fetching the seelog config file path: open /etc/amazon/ssm/seelog.xml: no such file or directory <br>
> Initializing new seelog logger <br>
> New Seelog Logger Creation Complete <br><br>
> ERROR Registration failed due to error registering the instance with AWS SSM. RequestError: send request failed
caused by: Post "https://ssm.us-east-1a.amazonaws.com/": dial tcp: lookup ssm.us-east-1a.amazonaws.com on 172.xx.xx.x:53: no such host <br><br>
Any clue?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
I found what I was doing wrong:
I was using "us-east-1a" (with the "a") as it was shown under my LIGHTSAIL Instances Dashboard. [ Virginia, Zone A (us-east-1a) ]
So, this command:
sudo amazon-ssm-agent -register -y -id xxxxxxxxxxxxxxxx -code Pxxxxxxxxxxxxxxxxxxxx -region us-east-1a
was supposed to be like this:
sudo amazon-ssm-agent -register -y -id xxxxxxxxxxxxxxxx -code Pxxxxxxxxxxxxxxxxxxxx -region us-east-1
Now it is working.
us-east-1a is an availability zone, us-east-1 is a region.
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- published a year ago