Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Cloud Quest VPC lab not working

0

Hello Team, I started the Cloud Quest Cloud practitioner, it went well till the last stage ie VPC peering. Im stuck at 92% due to the lab not working, first problem is I couldnt connect to the instance saying "failed to describe instance information" (e.g:arn:aws:ec2:us-east-1:262756598347:instance/i-09c608e4e7d96b085), second problem is I could not edit the route table association, add rule is not there in the page while clicking Edit route association(arn:aws:ec2:us-east-1:262756598347:subnet/subnet-097b2f1bd9ec8d031 -Route id :rtb-048292cde86024d26 | connecting-vpc/Marketing VPC/MarketingPublicSubnet1). Please respond. Please help me resolve the issue and get certification.

  • Gunasekaran, Makendran EXPERT
    17 days ago

    May I know the module name or the lab name you are facing issue so that I can replicate and see if there is a issue in the lab or not ?

  • Sri
    17 days ago

    Hi, I just ran the assignment and was able to complete it. Based on the description of the error you mentioned, looks like the lab time probably expired. Please retry again. Thanks!

  • Ramya
    17 days ago

    Thanks for the response, it worked for me in a diff browser.

  • Ramya
    17 days ago

    Thanks for the response, it worked for me in a diff browser.

Topics
Training and CertificationComputeNetworking & Content Delivery
Tags
Amazon VPCAmazon EC2Training and Certification
Language
English
asked 17 days ago44 views
1 Answer
-1

When experiencing issues with the Cloud Quest VPC lab, there are several common troubleshooting steps you can try:

For the "failed to describe instance information" error:

  1. Check that you're in the correct AWS region (commonly us-east-1)
  2. Try signing out completely and signing back in
  3. Clear your browser cache and cookies
  4. Try using a different web browser (some users report success switching from Edge to Chrome)

For the missing "Edit route association" or "Add rule" options:

  1. Refresh the page as suggested in the lab instructions
  2. Ensure you're looking at the correct tab - sometimes UI elements appear in different locations than expected
  3. Check that you have the correct permissions in the lab environment
  4. Try restarting the entire lab from the beginning rather than just continuing where you left off

These types of UI issues are relatively common in Cloud Quest labs and often stem from permission configurations, regional settings, or technical glitches in the lab environment itself. If these steps don't resolve your issue, you may need to contact AWS Cloud Quest support directly, as this could be a bug in the lab environment that requires their attention.

Cloud Quest lab environments have restricted permissions and pre-configured resources, which sometimes leads to these types of issues when the lab instructions don't perfectly align with the current AWS console experience.
Sources
Lab 2 is giving me issues | AWS re:Post
Cloud Quest Generative AI Practitioner - Stuck on "Create an Enterprise knowledge Assistant" | AWS re:Post

answered 17 days 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.

Relevant content