Guys has this happened with anyone ..my older aws ec2 instance just vanished from my console but I can still ssh into it, how do I manage it for security groups and other things..?

.

Have you performed an instance stop/instance start process on the instance in a while? It’ll migrate the VM to a different host system and should become viewable on the console again. (Was this instance initially launched prior to Dec 2016?)

Also, if you happen to perform the stop/start you might want to just detach and reattach the volumes while it’s off (provided they are EBS volumes not instance store volumes). If this is one of those pre-Dec2016 instances this step allows the ebs volumes to permit live volume resizing if needed in the future.

But of course, the best way to be safe is to reach out to AWS and see if their systems aren’t displaying older instances.

Another thing to ask is, is this instance in a VPC or in EC2 classic?

@TerraNimbus-io it was an ec2 classic instance..launched around may of 2017..

Hopefully this can help some, not sure if you’re using Linux or Windows as your main OS and whether or not you have the aws cli setup with PowerShell on your system, but this little one liner with report back if the instance is in a VPC or not. If the `VpcId` field is blank then this is an EC2 Classic instance.

(Get-EC2Instance -region “us-west-etc...” -ProfileName “this is your aws credentials profilename”).Instances | Where PublicIpAddress -eq x.x.x.x

You can substitute the `PublicIpAddress` with `PrivateIpAddress` if it doesn’t have a Pub IP.

@tayadehritik just saw your response, and I’ll be completely honest, I haven’t got a lot of experience with troubleshooting them over VPC instances. But I would imagine that they should be very similar in troubleshooting.

If the system hasn’t had a stop/start performed in a while then that could help it by causing the VM to migrate to a different host system. My thinking is that possibly the underlying host may not be reporting information correctly to the console. But Since AWS is hush hush about the infrastructure I can’t guarantee this would help as the host systems may not be responsible for that.

The next to check might be that the ec2 services local to the instance are running and if they are up-to-date. I think a quick way to check that, would be to go into SSM and see if you can run a simple command against the instance. It could potentially save you an ssh trip into the box looking for a service status and version.

I hate to be that guy that asks this question, but is it possible that the instance is in a different region? Sorry in advance for the question.

@TerraNimbus-io no I had checked all the regions it was no where...

@TerraNimbus-io yeah and I had not done a start/stop for a long time..

@TerraNimbus-io anyways thanks for the help man..