You are designing a system that has a Bastion host. This component needs to be highly available without human
intervention. Which of the following approaches would you select?
A.
Run the bastion on two instances one in each AZ
B.
Run the bastion on an active Instance in one AZ and have an AMI ready to boot up in the event of failure
C.
Configure the bastion instance in an Auto Scaling group Specify the Auto Scaling group to include multiple AZs but have a min-size of
1 and max-size of 1
D.
Configure an ELB in front of the bastion instance
http://docs.aws.amazon.com/quickstart/latest/linux-bastion/architecture.html
0
0
C
0
0
C
0
0
Answer is : C
Tricky part is to make sure same Elastic IP get configured for the newly instance in case of instance fail.
————————————————————————–
Elastic IP addresses are associated with the bastion instances to make it easier to remember and allow these IP addresses from on-premises firewalls. If an instance is terminated and the Auto Scaling group launches a new instance in its place, the existing Elastic IP addresses are re-associated with the new instances. This ensures that the same trusted Elastic IP addresses are used at all times.
Link : http://docs.aws.amazon.com/quickstart/latest/linux-bastion/architecture.html
0
0
C
0
0
A – “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.”
https://docs.aws.amazon.com/quickstart/latest/linux-bastion/architecture.html
0
0