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

EC2 instance does not use OnPrem identity even after the instance is registered successfully as Onprem instance #484

Closed
gianniLesl opened this issue Nov 10, 2022 · 1 comment
Labels

Comments

@gianniLesl
Copy link
Contributor

Steps to reproduce:

  1. Register agent 3.2.183.0 on EC2 instance as onprem while the instance is running
  2. Restart agent service
  3. Observe registration info is not saved in agent vault manifest

Logs:

INFO Successfully registered the instance with AWS SSM using Managed instance-id: mi-07eb9fb58c50c4bc5

WARN [OnPremIdentity] error while loading server info%!(EXTRA *errors.errorString=Failed to load instance info from vault. RegistrationKey does not exist.)

Workaround:
Replace the file contents of the vault manifest with the following json

Linux:

{"InstanceFingerprint":"/var/lib/amazon/ssm/Vault/Store/InstanceFingerprint","RegistrationKey":"/var/lib/amazon/ssm/Vault/Store/RegistrationKey"}

Windows:

{"InstanceFingerprint":"C:\\ProgramData\\Amazon\\SSM\\InstanceData\\Vault\\Store\\InstanceFingerprint","RegistrationKey":"C:\\ProgramData\\Amazon\\SSM\\InstanceData\\Vault\\Store\\RegistrationKey"}

The vault manifest is located at

Platform Location
Linux /var/lib/amazon/ssm/Vault/Manifest
Windows C:\ProgramData\Amazon\SSM\InstanceData\Vault\Manifest

This issue affects agent version 3.2.183.0

@gianniLesl gianniLesl added the bug label Nov 10, 2022
@gianniLesl
Copy link
Contributor Author

Fixed in agent version 3.2.286.0

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

No branches or pull requests

1 participant