How To Create & Use Bastion or Jump Host in AWS | Access Private Subnet Instance | Proxy Command
This AWS Solution adds Linux bastion hosts to your new or existing Amazon Web Services (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 solution sets up a Multi-AZ environment and deploys Linux bastion host instances into the public subnets. You can specify the instance type for the bastion hosts and the number of instances you want to deploy (1–4).
An Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling group ensures that the number of bastion host instances always matches the capacity you specify. For added security, the solution also sets up Amazon CloudWatch Logs for remote storage of shell history logs. After you deploy this solution, you can add more AWS services, infrastructure components, and applications to complete your Linux environment in the AWS Cloud.
This solution sets up the following:
A highly available architecture that spans two Availability Zones.*
A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
In the public subnets:
Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*
1–4 Linux bastion hosts in an Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling group for connecting to Amazon EC2 instances and other resources deployed in public and private subnets.**
An Amazon CloudWatch log group to hold the Linux bastion host shell history logs.
AWS Systems Manager for access to the bastion host.
#aws
#AWSbastionhost
#awscloud
#awssecurity
#subnet
#vpc
#devops
#awsdevops
#bestpractice
#awstraining
#devopstrainingvideos
#awscertification
#devopscertification
#devopscommunity