reference deployment
Linux Bastion Hosts on AWS
Secure remote access with Linux bastion hosts on the AWS Cloud
This Quick Start adds Linux bastion hosts to your new or existing AWS infrastructure for your Linux-based deployments. The bastion hosts provide secure access to Linux instances located in the private and public subnets of your virtual private cloud (VPC).
The Quick Start sets up a Multi-AZ environment and deploys Linux bastion host instances into the public subnets to provide readily available administrative access to the environment. You can specify the instance type for the bastion hosts and the number of instances you'd like to deploy (1-4).
An Auto Scaling group ensures that the number of bastion host instances always matches the capacity you specify. The Quick Start also sets up Amazon CloudWatch Logs for remote storage of shell history logs, for added security. After you deploy this Quick Start, you can layer your cloud environment with additional AWS services, infrastructure components, and applications to complete your Linux environment in the AWS Cloud.
This Quick Start was developed by
AWS solutions architects.
-
What you'll build
-
How to deploy
-
Cost and licenses
-
What you'll build
-
Use this Quick Start to set up the following networking environment on AWS:
- A highly available architecture that spans two Availability Zones.*
- A VPC configured with public and private subnets according to AWS best practices, to provide you with your own virtual network on AWS.*
- An internet gateway to allow access to the internet. This gateway is used by the bastion hosts to send and receive traffic.*
- Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
- A Linux bastion host in each public subnet with an Elastic IP address to allow inbound Secure Shell (SSH) access to EC2 instances in public and private subnets.
- A security group for fine-grained inbound access control.
- An Amazon EC2 Auto Scaling group with a configurable number of instances.
- A set of Elastic IP addresses that match the number of bastion host instances. If the Auto Scaling group relaunches any instances, these addresses are reassociated with the new instances.
- An Amazon CloudWatch Logs log group to hold the Linux bastion host shell history logs.
* The template that deploys the Quick Start into an existing VPC skips the tasks marked by asterisks and prompts you for your existing VPC configuration.
The architecture built by this Quick Start supports AWS best practices for high availability and security. We recommend that you follow the best practices detailed in the deployment guide when you’re using the architecture built by the Quick Start.
-
How to deploy
-
To add a bastion host to your Linux environment on AWS, follow the instructions in the deployment guide. The deployment process includes these steps:
- If you don't already have an AWS account, sign up at https://aws.amazon.com.
- Launch the Quick Start. Each deployment takes about five minutes. You can choose from two options:
- Add other AWS services or your Linux applications.
To customize your deployment, you can change your VPC configuration, choose the number and type of bastion host instances, enable TCP or X11 forwarding, and enable a default or custom banner for your bastion hosts.
- If you don't already have an AWS account, sign up at https://aws.amazon.com.
-
Cost and licenses
-
You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.
The AWS CloudFormation template for this Quick Start includes configuration parameters that you can customize. Some of these settings, such as instance type, will affect the cost of deployment. For cost estimates, see the Amazon EC2 pricing page.
