Skip to content
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

Updating from Ubuntu 20.04.1 to 22.04.19 broke SSM link #567

Open
ophilli opened this issue May 7, 2024 · 4 comments
Open

Updating from Ubuntu 20.04.1 to 22.04.19 broke SSM link #567

ophilli opened this issue May 7, 2024 · 4 comments

Comments

@ophilli
Copy link

ophilli commented May 7, 2024

Problem:

After updating from Ubuntu 20.04.1 to 22.04.19 my host began failing to connect to AWS Systems Manager. Notably with the following error:

_ = log.Error("Cannot connect to AWS Systems Manager. Machine configuration has changed more than the allowed threshold.")

I also had the following warnings:

WARN [OnPremCredsProvider] The 'IP Address' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
WARN [OnPremCredsProvider] The 'processor-hash' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
WARN [OnPremCredsProvider] The 'ipaddress-info' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
WARN [OnPremCredsProvider] The 'disk-info' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
WARN [OnPremCredsProvider] The 'memory-hash' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
WARN [OnPremCredsProvider] The 'bios-hash' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
WARN [OnPremCredsProvider] The 'system-hash' value (REDACTED) has changed from the registered machine configuration value (REDACTED).
INFO [OnPremCredsProvider] Calculated hardware difference, regenerating fingerprint...
ERROR [CredentialRefresher] Retrieve credentials produced error: MachineFingerprintDoesNotMatch: Fingerprint does not match REDACTED
@ophilli
Copy link
Author

ophilli commented May 7, 2024

https://www.reddit.com/r/aws/comments/scobtu/aws_ssm_machine_fingerprint_changed_after_os/ suggests that I may need to aws ssm create-activation again.

@ophilli
Copy link
Author

ophilli commented May 7, 2024

I ended up running create-activation again and now I'm up and running but I have a new managed id unfortunately.

It would be nice if the ssm agent were more resilient to distro upgrades, or had better documentation about how to manage this process.

@drzewiec
Copy link

Having the same issue as well. Patched one of my systems using Patch Manager, and the new fingerprint caused the machine to stop reporting in with SSM. Hopefully Amazon can get a fix for this, because I definitely have reservations about using Patch Manager now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants