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

Bug: Can't start an encrypted session #11

Closed
jonasneves opened this issue Dec 13, 2020 · 3 comments
Closed

Bug: Can't start an encrypted session #11

jonasneves opened this issue Dec 13, 2020 · 3 comments

Comments

@jonasneves
Copy link
Contributor

I get the following error when I try to start a session on version >=v1.1.0

----------ERROR-------
Encountered error while initiating handshake. KMSEncryption failed on client with status 2 error: Failed to process action KMSEncryption: Error calling KMS GenerateDataKey API: UnrecognizedClientException: The security token included in the request is invalid.
	status code: 400, request id: b3ebe283-c1bf-4722-b553-8f08693a9694

gossm v1.0.5 works without any problem.

@gjbae1212
Copy link
Owner

@jonasneves
It's working well for me.
I also have made sessions using KMS in AWS.
I would say, maybe AWS session-manager-plugin differents.
gossm have used session-manager-plugin internally, so this plugin is placed in $home/.gossm directory.

Check it session-manager-plugin. you can check to try it, such as ./session-manager-plugin --version

At least, I do works session-manager-plugin 1.1.61.0.

@zswanson
Copy link

It appears that doing an upgrade of gossm doesn't update the session-manager plugin that's 'installed' in the home directory, if it has a minimum version required for gossm

@jonasneves
Copy link
Contributor Author

Closing this as I'm not seeing the error anymore in the new version. Unfortunately, it's a different one though

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

3 participants