-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
AWS cli plugin session-manager-plugin cannot be used on macOS without workaround #5758
Comments
Hi @programmer04, thanks for the report. I don't have Big Sur in order to test this, but I will check in with the SSM team. |
This happens when its installed via Homebrew instead of manually installing it from the AWS website. It would be wonderful if AWS could work with the Homebrew folks, so that AWS can publish the source that Homebrew uses for these packages. It would resolve a great many issues in the ecosystem around AWS. |
Unfortunately, this issue still exists for the current newest version |
Is this still an issue for you, @programmer04? Can you confirm what @skyzyx noted is that it occurs when installed via Homebrew? If you install via one of the supported installation mechanisms, does it still occur? @skyzyx, I appreciate the feedback. We have proposed a new source distribution (#6352) that addresses package maintainers ability to build from source. The Homebrew team is aware of this proposal. |
It occurs when is not installed from pkg (which is notarized) available since version
thanks for introducing this notarized pkg. Hence I'm prosing changes in the formula Homebrew/homebrew-cask#113686 to install AWS Moreover, @kdaily could the AWS team bump the version in this formula always when the new |
My PR Homebrew/homebrew-cask#113686 has been already merged. Thus this issue can be considered as resolved. |
|
Describe the bug
AWS cli plugin session-manager-plugin is not notarized by Apple, so after fresh installation, it cannot be open:
The workaround described here solves the issue and the program works, but basically, the user has to bypass macOS default security checks to get it run, which is not nice.
SDK version number
I tried with two last versions of session-manager-plugin:
1.2.30.0
1.2.7.0
Platform/OS/Hardware/Device
To Reproduce (observed behavior)
Just try to run
session-manager-plugin
after fresh installation (without workaround) e.g.Expected behavior
This binary should work out of the box.
Additional context
Many other projects resolved it in the past e.g.:
The text was updated successfully, but these errors were encountered: