Day 37: Issue with Managing EC2 Access with S3 Role-based Permissions

KodeKloud Engineer
#1

Hi team,

I am facing an issue with this task when I am trying to connect ec2 instance. Its not connected even after allowing ssh port 22 on inbound rule. This happen with me on other tasks as well. Can you please check why we are not able to connect EC2 instance?

#2

Hi @sandeepchoudhary04

There are several reasons for this:

  • A public IP is assigned to the EC2 instance
  • The Security Group allows SSH (port 22) from your IP

Please share the exact error message you get when connecting, or a screenshot—it would be very helpful.

#3

Error1
Error11093×627 16 KB

error2
error2925×630 43.4 KB

error3
error31651×553 41.9 KB

#4

Hi @sandeepchoudhary04

I’ve just started the task and able to ssh to the datacenter-ec2 without doing anything, could you please try it again and let me know if it persists?

image
image1909×819 48 KB

image
image1897×969 104 KB

#5

Still I am facing the same issue. Why its happening can you please troubleshoot if I share you my screen. Please let me know once you free.

#6

Can anyone help me on this?

#7

Raymond’s doing something a bit different than what you’re doing – he’s setting up a security group to allow ssh from arbitrary addresses, which works. You’re using “EC2 Instance Connect” – which should work for the existing instance, since I tried using that and it worked. You need to use the “Connect using public IP address” setting, which is the default for that connect type. If you changed any of the settings for the existing EC2 instance, that might explain the problem.

#8

Not working through EC2 Instance Connect or if I tried to connect through SSH client. Instance xfusion-ec2 which is already created for this task has no key pair associated with it. Please let me know how to complete this task.
as i tried to create with creating instance from my side also with same name and associate with key pair. The task steps completed by still it shows error like unable to get details of an instance while submitting the task. please help me regarding the same.

#9

No key pair is required for EC2 Instance Connect, and when I did it, the default settings allowed it to work. How are you invoking it? Again, the default settings simply worked for me when I did it. Certain SG and routing settings do have to be set, but again, they are already set for you.

#10

I did nothing change. whenever I tried to connect through EC2 Instance Connect. It shows error to me everytime,

Failed to connect to your instance

Error establishing SSH connection to your instance. Try again later.

Please help me regarding the same as I stuck in this lab from last 5 days and unable to proceed with next lab.

#11

TBH, I just don’t know why you’re failing here. I just did the following:

  • Created a public key pair (ssh-keygen with no arguments) in the terminal.
  • Logged into the AWS console.
  • Opened the EC2 “instances” list, and chose “Connect” for the existing instance.
  • Chose “EC2 Connect” with straight out defaults; EC2 connect worked.
  • Using the open “ec2-connect” terminal, edited ~/.ssh/authorized_keys to contain the id_rsa.pub file from the lab terminal.
  • Chose the security tab from the instance display for the EC2 instance, and chose the security group of the instance.
  • Edited incoming, and added ssh for 0.0.0.0.
  • Went back to the Connect screen, choose “ssh client”
  • Copied the ssh connect string.
  • Edited the string so the -i argument points to ~/.ssh/id_rsa.
  • Executed the command, got the ubuntu account for the instance.

Please read this AWS doc page, to make sure you’re doing what I suggest above.

#12

I already followed the same steps which you have mentioned multiple times but I don’t know why it’s not working for me. Not able to connect through EC2 Connect. Is there any other way to complete this task?

#13

Hi @sandeepchoudhary04

It is really weird. Could you please record a screenshot and share it? I couldn’t reproduce your case on my end.