Optionally, launch an EC2 instance for the jump host to remotely access the elastic
runtime environment. If you can access the private subnet through your enterprise network,
you don't need to create a jump host.
The jump host is an EC2 instance in the public subnet that you can use to SSH into nodes
in the elastic runtime environment in the private subnet. Because the elastic runtime
environment is designed to run in a private subnet, a jump host can remotely access the
environment.
Using a jump host is a best practice for secure and scalable infrastructure so that the
elastic runtime environment isn't exposed to the internet. The jump host greatly reduces
the attack surface and prevents unauthorized access to the elastic runtime environment,
and access is controlled using SSH authentication and security group rules. If the jump
host is compromised, nodes in the elastic runtime environment are protected by a
firewall and security groups.
Create a jump host using the launch instance wizard in AWS. Use the following
guidelines:
Use Amazon Linux as the OS
image.
Use instance type
t3.small
.
Create a new key pair.
Use the VPC that you created.
For the subnet, select the public
subnet that you created.
Enable
Auto-assign public
IP
.
Use the security group that you
created for the jump host. For more information, see Step 1. Create AWS resources.
ASK INFAPreview
