“Enough already with the DHCP complaints!” It’s Friday, so it means soon, we can stop worrying about such stuff and can get onto better things…
Until then, I’m sure other folks will be working with an AWS instance, go to log in after setting it up the initial time and want to know why the ssh connection that worked fine the day before is now hanging. In fact, if anything has been done to renew their DHCP release and change their IP Address, this could occur.
There’s always more than one way to skin a cat and along with setting aliases for your favored IP address, the second option is to follow the next steps.
What’s Your Number?
So you can get to your instances via the EC2 console and use the Delphix admin console without any issue, but if you try to ssh into a source or target, (aka instances) the prompt just hangs. The problem is that all that lovely automation that built out this incredible environment for the Delphix AWS Trial, also built out the security group setting for inbound traffic for you, tying the access to your IP address. This information was entered in the terraform.tfvars file and the IP in this file no longer matches your new IP Address.
- Get the new IP Address. Number of methods- but I’m lazy and just type in “What is my ip address” in Google.
Update Your Security Group Rule
- In the the AWS EC2 Console, click on the instance you’re trying to log into.
- Click on the Description tab in the lower part of the screen.
3. In this tab, you’ll see a listing for Security Groups. Click on the group name to the right of Security Groups.
4. Click on Edit
5. You’ll see what was your previous IP address, (if you haven’t updating your terraform.tfvars since the build, you can verify this.)
6. Update the IP address with your new one and click on SAVE.
Now try to SSH into the box. You’ll need to do this for any and all instances that you want to connect to via a terminal.
Hint hint: This is also the location to add a new workstation that needs access to work on the instances.