Apparently, I've done a stupid thing and forgot my Ubuntu Server in AWS is Server 14. I've upgraded the ubuntu to 16.04 a few months back, but forgot that it's supposed to be still Ubuntu Server 14.
So I followed the guide https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html and followed the steps in Ubuntu Server 16. This got me locked out of my own server, and no matter what I tried (rebooting, assigned new private IP, tried pinging from other servers in the same subnet), I still can't get in. SSH ends up in Operation timed out. I've locked myself out.
I even tried creating an AMI and launch the image into a new instance but still it won't work, maybe because the network interfaces files are backed up into the image as well?
Apparently, I've done a stupid thing and forgot my Ubuntu Server in AWS is Server 14. I've upgraded the ubuntu to 16.04 a few months back, but forgot that it's supposed to be still Ubuntu Server 14.
So I followed the guide https:/ /docs.aws. amazon. com/vpc/ latest/ userguide/ vpc-migrate- ipv6.html and followed the steps in Ubuntu Server 16. This got me locked out of my own server, and no matter what I tried (rebooting, assigned new private IP, tried pinging from other servers in the same subnet), I still can't get in. SSH ends up in Operation timed out. I've locked myself out.
I even tried creating an AMI and launch the image into a new instance but still it won't work, maybe because the network interfaces files are backed up into the image as well?
What can I do to regain access to my server?