{"id":13163,"date":"2023-04-05T02:09:52","date_gmt":"2023-04-05T08:09:52","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=13163"},"modified":"2023-07-26T06:24:49","modified_gmt":"2023-07-26T12:24:49","slug":"how-to-regain-access-to-aws-ec2-linux-instance-when-key-pair-lost","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/how-to-regain-access-to-aws-ec2-linux-instance-when-key-pair-lost\/","title":{"rendered":"How to Regain access to AWS EC2 Linux instance when key pair lost?"},"content":{"rendered":"\n

An associated key pair ( private key and a public key) is necessary to access EC2 instance securely. In case you have lost or corrupted the key pair, here’s how you can regain access to AWS EC2 Linux instance.<\/p>\n\n\n\n

Let\u2019s assume that the EC2 instance running contains a website but you have lost the key pair that is associated with the EC2 instance. And here we will show the two easiest ways to regain access to AWS Linux EC2 instances.<\/p>\n\n\n\n

  1. By using an Amazon Machine Image (AMI)<\/li>
  2. By swapping the volume of the EC2 instance <\/li><\/ol>\n\n\n\n

    By using an AMI <\/strong><\/h2>\n\n\n\n

    An Amazon Machine Image (AMI) is the exact copy of the settings and configuration of an EC2 instance. We can create an AMI from an existing running instance. <\/p>\n\n\n\n

    In this method, we don\u2019t have to stop the running EC2 instance. <\/p>\n\n\n\n

    1. The first step is to create an Amazon Machine Image of our primary web server EC2 instance. <\/strong><\/h3>\n\n\n\n

    Select the instance > Actions > Image and templates > Create image<\/p>\n\n\n\n

    \"\"\/<\/figure>\n\n\n\n

    Now provide the necessary details like image name, and description and create the image. <\/p>\n\n\n\n

    2. Now we can deploy a new instance by using the customized image that we have created. <\/strong><\/h3>\n\n\n\n

    Follow the steps below to deploy a new instance by using the customized AMI.<\/p>\n\n\n\n

    1. Login to the AWS<\/a> console and navigate to the instances page.<\/li>
    2. Click on Launch an instance and provide the new instance name.\u00a0<\/li>
    3. Now click on the option My AMIs and select the AMI we have created.\u00a0<\/li><\/ol>\n\n\n\n
      \"\"\/<\/figure>\n\n\n\n
      1. Also create a new key pair for the new instance. <\/li><\/ol>\n\n\n\n
        \"\"\/<\/figure>\n\n\n\n
        1. Now click on the button \u201cLaunch instance\u201d to create the new web server instance. <\/li>
        2. We can now access the new web server instance using the new key pair and terminate the old instance. <\/li><\/ol>\n\n\n\n

          This approach does not involve the retrieval of the key pair for the initial instance. Rather, it entails the customization of an image of the web server and the subsequent launch of a new web server that replicates the previous instance, albeit with a new key pair.<\/p>\n\n\n\n

          By swapping the volume of the EC2 instance <\/strong><\/h2>\n\n\n\n

          This approach entails the regeneration of a new SSH key pair and its attachment to the EC2 instance in order to restore its functionality. However, a major drawback of this method is that it requires the instance to be halted, thereby causing a service interruption.<\/p>\n\n\n\n

          For this demonstration, I\u2019ve deployed two EC2 instances with different key pairs. <\/p>\n\n\n\n