𝐉𝐮𝐦𝐩 𝐒𝐞𝐫𝐯𝐞𝐫 𝐂𝐨𝐧𝐜𝐞𝐩𝐭 𝐢𝐧 𝐀𝐖𝐒
EC2 1- Create an EC2 instance inside a VPC and attach an internet gateway to VPC, Create the instance in Public Subnet which means assign an internet gateway in routes.
EC2 2- Create an EC2 instance inside the same VPC, Create the instance in Private Subnet which means assign a NAT Gateway to the Private subnet routes.
Nat Gateway should always be created in a Public Subnet.
We have to allow the connectivity between EC2 1 and EC2 2 ....
To achieve this ENI of the instance in Public Subnet should be allowed in Routes of the Private Subnet's EC2 Machine.
From the EC2 1 if it's a Linux machine we can SSH into EC2 2.
It's advised not to store key pairs of the machines inside the instance.
We must always store the keys in Pagent and in Putty we must enable agent forwarding.
Scenario : Consider EC2 1 as a Public Instance ie accessible through internet
Consider EC2 2 as a Private Instance that cannot be accessed via internet but following the above steps via EC2 1 the EC2 2 Webserver can be connected.
In order to connect to a Windows machine from Linux we must install remote desktop client
My articles - https://lnkd.in/gq7fdDvR

aws #awscloud #awssolutionsarchitect