This is a secure/locked-down bastion implemented as a Docker Container. It uses Alpine Linux as the base image and ships with support for Google Authenticator & DUO MFA support.
It was designed to be used on Kubernetes together with GitHub Authorized Keys to provide secure remote access to production clusters.
Here's a demo of what a user experiences when setting up Google Authenticator for the first time.
When using Duo as the MFA provider, this becomes even more magical because Duo supports automatic Push notifications to your mobile device. Just approve the request on your mobile phone (e.g. with a thumb press on iOS) when prompted.
Here's what it looks like when someone connects to the bastion if Slack notifications are enabled.
We recommend using Slack notifications for self-reporting.
This project is part of our comprehensive "SweetOps" approach towards DevOps.
It's 100% Open Source and licensed under the APACHE2.
Refer to the Environment Variables section below to tune how the
$ docker run -p 1234:22 cloudposse/bastion:latest
$ git clone https://github.com/cloudposse/bastion.git $ cd bastion $ make docker:build
sudo) access to this container as doing so would allow remote users to manipulate audit-logs in
/var/log/sudo-ioto a remote, offsite location. If using S3, we recommend enabling bucket-versioning.
/etc/groupinto the container as read-only
/homeinto container; the bastion does not manage authorized keys
The following tables lists the most relevant environment variables of the
bastion image and their default values.
Duo is a enterprise MFA provider that is very affordable. Details here: https://duo.com/pricing
||Enable the Duo MFA provider||duo|
||Duo Integration Key|
||Duo Secret Key|
||Duo Host Endpoint|
||How to fail if Duo cannot be reached||secure|
||Automatically send a push notification||yes|
||How many times to prompt for MFA||1|
Google Authenticator is a free & open source MFA solution. It's less secure than Duo because tokens are stored on the server under each user account.
||Enable the Google Authenticator provider||google-authenticator|
The enforcer ensures certain conditions are satisfied. Currently, these options are supported.
||Enable general enforcement||
||Erase dot files in home directory before starting session||
The enforcer is able to send notifications to a slack channel anytime there is an SSH login.
||Enabled Slack integration||
||Slack integration method (e.g.
||Slack handle of bot (defaults to short-dns name)|
||Deny logins if slack notification fails||
The SSH auditor uses
sudosh to record entire SSH sessions (
||Enable the SSH Audit facility||
This will require that users login with the
Update user's default shell by running the command:
usermod -s /usr/bin/sudosh $username. By default,
root will automatically be updated to use
sudoreplay command to audit/replay sessions.
bastion was written to be easily extensible.
You can extend the enforcement policies by adding shell scripts to
etc/enforce.d. Any scripts that are
chmod 755) will be executed at runtime.
Here's how you can quickly demo the
bastion. We assume you have
~/.ssh/authorized_keys properly configured and your SSH key (e.g.
~/.ssh/id_rsa) added to your SSH agent.
$ docker run -it -p 1234:22 \ -e MFA_PROVIDER=google-authenticator \ -v ~/.ssh/authorized_keys:/root/.ssh/authorized_keys cloudposse/bastion
Now, in another terminal you should be able to run:
$ ssh [email protected] -p 1234
The first time you connect, you'll be asked to setup your MFA device. Subsequently, each time you connect, you'll be prompted to enter your MFA token.
Got a question?
Work directly with our team of DevOps experts via email, slack, and video conferencing.
We provide commercial support for all of our Open Source projects. As a Dedicated Support customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.
Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.
Signup for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Please use the issue tracker to report any bugs or file feature requests.
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!
Copyright © 2017-2018 Cloud Posse, LLC
See LICENSE for full details.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
All other trademarks referenced herein are the property of their respective owners.
We offer paid support on all of our projects.