-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssm agent fails to start on windows t3 ec2 instances #348
Comments
I'm seeing this too but on a T3A.medium AMI running on a C5A.xlarge instance. I can't rule out that just rebuilding the image fixed it, but I started again on a C5A.xlarge and it runs just fine on a C5A.xlarge instance. |
Thanks for reporting this issue, we are working on reproducing this locally. Can you confirm that the metadata service is available on the ec2 instance where the agent is showing these errors?
|
I was able to reproduce the issue with the following steps:
This results in the EC2 metadata service not being available.
I've cut a ticket in our internal ticketing system to the relevant teams. |
I've received feedback that this is expected behavior and that the instance needs to be reconfigured. Please take a look at these docs to get an idea on how to resolve your issue: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2launch.html#ec2launch-config |
Import-Module C:\ProgramData\Amazon\EC2-Windows\Launch\Module\Ec2Launch.psm1; Add-Route |
Hi, I've started seeing errors very similar to #48 when codedeploy creates new instances for deployment.
Specifically when I create new t3 instances. t2 instances seem to work fine.
The ami was created from a t2 snapshot taken in
eu-west-1c
in december, and it has worked fine creating t2 instances ineu-west-1a
- is creating t3 instances from t2 snapshots not supported?amazon-ssm-agent.log
says isThe route table is
The text was updated successfully, but these errors were encountered: