SSM Agent Won't Start

Hi,

I have now had this resolved. My issue here was that the SSM agent needed to hit the magic IP address which allows metadata to be queried, as per one of the above responses the Invoke-RestMethod -uri http://169.254.169.254/latest/metadata is intended to test this. Another way to test this would be Test-NetConnection -ComputerName 169.254.169.254 -Port 80.

In my context, the AMI was not syspreped and so the EC2 instance was trying to use the GW from the AMIs subnet in it's route table. To fix this, the EC2 instances route table needed to be fixed. The following two commands did the trick:

1. Import-Module "C:\ProgramData\Amazon\EC2-Windows\Launch\Module\Ec2Launch.psd1"
2. Add-Routes

The first command enables the second, and the second corrects the routing table.

Regards

Edited by: ntendo64 on Nov 24, 2021 8:30 AM

Thanks for reaching out to us! We are looking into your request.

Hi BanksAT, Could you verify that the EC2 metadata service is accessible inside the bastion host? You can verify that by running the following command:

Invoke-RestMethod -uri http://169.254.169.254/latest/meta-data/

If it is unavailable and you are using a custom AMI, these links should help you get the metadata service working again:

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2launch.html#ec2launch-config
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.html#update-metadata-KMS

Thank you for the assistance, thor-aws! I will check on this and get back to you.

Regards

Did you figure out the issue and fixed?
I am running into the same issue

Hi BanksAT. Just following up on this -- were you able to try the steps suggested by thor-aws?

Edited by: DanR@AWS on Aug 13, 2021 2:59 PM

Hi,

I'm experiencing the exact same problem and wondered if this can be relooked at.... Let me know what information to provide

Thanks in advanced for the assistance