Issue With (LAB – Public and Private subnets and the gateways)

Hi Everyone,

I’ve reached to at stage of " AWS Solutions Architect Associate Certification" course where I’ve to complete my first LAB. While starting my LAB I’ve accidentally clicked on next button without actually opening LAB with provided credentials. This took me to next page of step 1 of the LAB test. Though I’ve logged into the LAB using other option of the platform and completed my first and second step.

But on clicking Check button it is showing as Incomplete for both the steps.

There seems some issue with my login as I’m not able to see below pre created security group and keypair mentioned in third question of LAB.

Keypair: ec2-user (already present in the lab terminal)
Security Group: existing security group > kloudswift-sg

Is there anything additional that I need to do?

Regards,
Manoj

Reset the lab and try again.

After lot of retry and restart it worked. I’m able to complete first 10 steps. But now I’m facing issues with 11th. Step I’m not able to connect to ec2 instance. Please refer attached screen shot.

Hi Manoj thank you for using kodekloud. In 1st question of every lab there is information how to use terminal. Click on expand panel button to access terminal. There you will have all required resources as per lab requirements.
Thank you.

Thanks a lot Jarugu. This helped. I’m able to find terminal option inside LAB browser page. Earlier I was trying to connect to this EC2 Instance which I’ve created as part of first LAB from my local Mcbook terminal.

Ideally I should be able to connect to this EC2 Instance from my McBook terminal also because it is connect to Internet Gateway and has Public IP assigned to it.

I’m not able to understand why I’m not able to do that?

@JARUGU-PHANIVARDHAN

Can I connect to EC2 instance from which I created as part of LAB from outside as it has internet gateway attached and public accessible entry created in route table?

Hello @manoj.gupta.91,

Certainly! you can access the EC2 instance, provided the security groups and network policies are aligned for your specific lab. Simply copy the SSH key from the lab terminal to yours, ensuring the name and content match. Don’t forget to adjust permissions. Now, with the SSH command, you’re all set to access. Remember Key differs for every lab session.

For a broader exploration of AWS services, feel free to utilize our playgrounds.

Thank you for your attention.

Best regards,
J. Phani Vardhan