You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of AWS SSM, in some cases, I may try and connect to an instance with an old version of the SSM agent. Because I may want or need to update the agent in order to use ssm-session, it would be nice to have the ability to use the update functionality of SSM to resolve this issue.
In some cases, the StartSession API may return a "TargetNotConnected" error. This indicates that "the specified target instance for the session is not fully configured for use with Session Manager", which can indicate several different issues, including an SSM agent version older than 2.3.68.0.
Fortunately, AWS provides an SSM document ("AWS-UpdateSSMAgent") that can be used to resolve the problem of an outdated agent. This could be implemented as an additional subcommand and/or as an extension of ssm-session.
The text was updated successfully, but these errors were encountered:
As a user of AWS SSM, in some cases, I may try and connect to an instance with an old version of the SSM agent. Because I may want or need to update the agent in order to use ssm-session, it would be nice to have the ability to use the update functionality of SSM to resolve this issue.
In some cases, the StartSession API may return a "TargetNotConnected" error. This indicates that "the specified target instance for the session is not fully configured for use with Session Manager", which can indicate several different issues, including an SSM agent version older than 2.3.68.0.
Fortunately, AWS provides an SSM document ("AWS-UpdateSSMAgent") that can be used to resolve the problem of an outdated agent. This could be implemented as an additional subcommand and/or as an extension of ssm-session.
The text was updated successfully, but these errors were encountered: