Closed eddelac closed 3 years ago
We filter out interfaces that are either not up or are a loopback/pointtopoint interfaces (check code here).
The three interfaces you have are either loopbacks or point to point, so they will all get filtered out. Thus, when calling UpdateInstanceInformation, there will be no IP and a validation error will be thrown.
Is there a way to bypass this validation? This worked in the past. (Installed around 2018, working ok, server was wipped out.) AFIK the setup of the VPS server hasn't changed.
The only change has been in the latest available version of the client. Downgrading to a previous version might work?
Thanks for any advise you might have, I assume that this is an atypical network setup, but I have little control of the interfaces.
Do you know which version of SSM Agent you were using before?
Hi there,
I've installed the version (2.2.546.0) - Released 11 May 2018, and now the instance registers correctly.
As I said, the network setup hasn't changed, although the instance registers with the 127.0.0.1 as IP Address the run command works.
I want to use the remote session manager, so I would like to know how to bypass the validation on the first run of the new version if possible.
Hello,
Since we cannot update the code to no longer filter out P2P interfaces as this could have backward compatibility issues, our suggestion would be for you to build SSM Agent for your use case by modifying this line.
The instructions on how to build the SSM Agent yourself can be found in the README.md file.
Thanks, Faho Shubladze
Hello,
Since we cannot update the code to no longer filter out P2P interfaces as this could have backward compatibility issues, our suggestion would be for you to build SSM Agent for your use case by modifying this line.
The instructions on how to build the SSM Agent yourself can be found in the README.md file.
Thanks, Faho Shubladze
Thanks for the feedback Faho,
I would try to make a custom build to my scenario. Is great to know that the agent has such thorough support.
Regards, Edgar
Hi
I did a fresh installation of SSM on a VPS server, the hybrid activation works fine, but after it appears this on the error log: /var/log/amazon/ssm/amazon-ssm-agent.log
It was working in the same VPS with a previous version,
details for /var/log/amazon/ssm/errors.log
I don't know if the interface is being marked as loopback, the Public IP is set on venet0:0 (2 last octets replaced for X)
It appears to be thrown by this function
amazon-ssm-agent/agent/platform/platform.go
The information of the Managed Instance appear like this on SSM
Is there any workaround for this scenario?