-
Notifications
You must be signed in to change notification settings - Fork 23
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
Monitor awsarm through SSH #37
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
One item we possibly might want to simplify in a a follow-up PR:
I think we do not necessarily need the sshified
but similar ssh tunnelling setup could be established using just ssh
with option -L
(or possibly -D
). Or did you trial this already?
@henrirosten |
Signed-off-by: Joonas Rautiola <[email protected]>
b3ee8f6
to
284ddf2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure that the sshfied user on awsarm only has the permissions absolutely necessary for this to work.
@tervis-unikie sshified user has whatever is default permissions when using |
Then the user can do whatever a normal user can do, which for the purpose of sshfied is excessive. |
sshified can be used to proxy prometheus metrics through ssh connection, meaning we do not have to open any ports to the world.
This PR adds a derivation to build
sshified
, a systemd service to run it, and the necessary ssh configuration to scrape metrics from awsarm.Also added documentation that tells how to add new monitored targets, with either ssh or http authentication, though there are no more targets that are using http basic auth.