0

I was following the instructions here:

Re-gaining root access to an EC2 EBS-boot image

  http://serverfault.com/questions/234061/re-gaining-root-access-to-an-ec2-ebs-boot-image

And I successfully completed this stage:

  Re-attach the drive back to your original problematic instance and set to "Start"

But then the new instance spun up, but it has no public DNS nor any public IP. How can I be sure it has the same settings as the previous instance that it was built from?

To be clear, I took the old instance and clicked "Launch more like this", and that is how I created the new instance. But it seems to have different settings.

4
  • 1
    Can you expand on "no public DNS"? You can't do nslookups? Maybe output the IP details - in unix type "ip a".
    – Tim
    Apr 18, 2016 at 22:18
  • I mean, if I look here: console.aws.amazon.com/ec2/v2/…, then I don't see any entry in the columns "Public DNS" and "Public IP". The problem is described here: stackoverflow.com/questions/20941704/…. However, these instances have always had Public DNS set to "Yes".
    – lorm
    Apr 19, 2016 at 0:23
  • Post a screen shot please, we can't see your console. You probably have to attach a network interface and then an elastic IP to that instance.
    – Tim
    Apr 19, 2016 at 0:33
  • I gave up on this. I created a new instance, and I clicked the "Enable Auto Public DNS" option when I was creating the instance.
    – lorm
    Apr 19, 2016 at 16:38

0

You must log in to answer this question.

Browse other questions tagged .