In order to shrink the root volume of the AWS EBS

0

In order to shrink the root volume of the AWS EBS, the following steps were taken

  1. acquire a snapshot of the root volume from the EC2 to be shrunk (set the EBS to be shrunk as v1)
  2. create a volume from the snapshot created in step 1 (set the created EBS as v2)
  3. Start a new EC2 from the same AMI as the EC2 to be downsized
  4. Detach the root volume from the EC2 created in step 3 (the detached EBS is designated as v3)
  5. Attach the v2 and v3 EBSs to the EC2 to be downsized
  6. Synchronize the contents of v2 to v3
  7. Change the root volume of the EBS to be shrunk to v3

After completing the above steps, when checking the connection to the server, I received a "Permission denied" error on Teraterm. Also, the Tereterm error message drops out as soon as it pops up. Is anyone else experiencing similar problems? I would like to borrow the wisdom of those in the know.

Is anyone else experiencing similar problems? I would like to borrow the wisdom of those in the know.

https://blog.e2info.co.jp/2021/10/29/aws-ebs%E3%83%AB%E3%83%BC%E3%83%88%E3%83%9C%E3%83%AA%E3%83%A5%E3%83%BC%E3%83%A0%E3%81%AE%E3%82%B5%E3%82%A4%E3%82%BA%E3%82%92%E7%B8%AE%E5%B0%8F%E3%81%99%E3%82%8B/

asked 2 years ago465 views
1 Answer
0

Hi there,

I understand that you are trying to access your instance and you are getting a “permission denied” error on your Teraterm. Please correct me if my understanding is wrong.

From your response, I see that you have taken steps to decrease the root volume of the AWS EBS. Your error could be due to several issues such as you are trying to connect using the wrong user name for your AMI(1), The file permissions within the operating system are incorrect on the instance(2) and the incorrect SSH public key (.pub) file is in authorized_keys file(3). In recommendation verify that the file permissions within the operating system are correct and that the correct SSH public key is in the authorized_keys file.

You follow the steps provided on the following links to troubleshoot your issue:

[1]https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesConnectingPuTTY [2]https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-fix-permission-denied-errors/

I hope the above information is helpful.

Winnie
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions