You should receive another notification on Slack, this time with the real remote host IP address.īuilding a bot and running it in Google Container Engine Keep this SSH window open in case something went wrong and verify that you can login from another SSH terminal. It configures /etc/pam.d/sshd to run the script whenever someone SSHes into the machine by adding the line 'session optional pam_exec.so seteuid /etc/slack/login-notify.sh'. The install.sh script creates a /etc/slack directory and copies the login-notify.sh script and slack-hook configuration there. We'll be using the notify sample for this integration. Next, SSH into the machine and clone the repository.

Give the hook a nice name, like 'SSH Bot' and a recognizable icon, like a lock emoji. You can follow this guide to create one and follow along.Ĭreate a Slack incoming webhook and save the webhook URL. To get started, we assume you have a Linux Compute Engine instance. This could be an audit log, but it's also useful to know when someone is using a shared machine so you don't step on changes each other are making. If you're using Google Compute Engine as a virtual private server, it can be useful to get an alert to know who's using a machine. Using Slack for notifications from a Compute Engine instance Since all the platforms we use in this tutorial support incoming HTTPS connections, all these samples could be extended into Slack Apps and distributed to other teams.

Or make your own fork to use as the base for your own integrations.

Slack login google