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
These are definitely good suggestions. For your reference, keymaker is intended for use in environments where you procedurally and idempotently generate and save AMIs, instead of managing them on an ad hoc basis (which is the only scenario in which you'd need such a command). I would encourage you to look into ways to build your AMIs and manage your instances automatically.
With that said, the listing of files is a low priority and easy item to do. The actual uninstall command is low priority and high complexity (figuring out a safe way to back out keymaker-induced changes from the sshd config is an open question for me).
Agree that with automation of keymaker setup this is a non-issue. An alternative to baking keymaker into an AMI is to automate keymaker installation from a vanilla AMI, for example using cloudformation. Then when you don't want keymaker just remove the automation or just use a vanilla AMI
Currently, there is no way to uninstall keymaker.
Please add this option and explain how to do it in the documentation.
It would also be helpful to list where the keymaker files are installed to (file paths).
The text was updated successfully, but these errors were encountered: