@magdalena.bouza It makes sense that we should be seeing the same behavior.
What I mean by new files/configurations is that the file, “../.aws/aws_console_url” is empty, so using the cat command does not display the url to paste in the browser. I’m not getting a session. I have used the ? Reboot several times today, yesterday, and the day before but I’m having the same experience. I’ll try again now. Same result in Chrome and Safari. I cleared the browser cache as well.
after multiple attempts, following instructions, still showed Failed test case: Expected to generate stress test to increase Networking Activity.
Expected:
NetworkOut > 999999,
but got:
NetworkOut = 299368.0.
Failed test case: Expected to add the inbound rule for the ALB Security Group on port 80.
Expected:
Inbound rule for port 80 exists,
but got:
No inbound rule for port 80 found.
Failed test case: Expected to create and execute the Launch Template.
Expected:
At least two instances of type ‘t3.nano’ exist,
but got:
0 ‘t3.nano’ instance(s) found.
Failed test case: Dynamic scaling policy ‘de-c1w3-scaling-policy’ was not found for ASG ‘c62825a3581670l13786613t1w716650149999-AutoScalingGroup-3CddCumV0Uv5’..
Expected:
None,
but got:
None.
i alerady did as per instructions login aws through link created but still failed WHY???
1 Like
Did you by any chance change any of the configuration files? In the meantime I’m looking into restarting your lab on our end. I’ll let you know as soon as I have more information.
Hi @romeopeay I believe I’ve found the issue with the lab. For each lab, each learner is given a budget for time and cost, in your case, you had exceeded the time budget. That’s why the link was coming blank. We completely understand this can happen, so we have reset it for you.
Hope this helps you finish the lab without any further issues!
I forgot to mention, if this happens again in any of the labs, please report it in this Google Form. Please refer to this reading item with the guidelines on how/where to report issues for a faster resolution.
1 Like
No. I was tempted but did not.
That makes sense… thank you for looking into this.
No problem! Thank you for the patience. Please do let me know if the issue is resolved.
@magdalena.bouza Good news. I was able to access the lab again. While not all services were available on the AWS Console (same issues), I was able to complete all the activities. However, my grade was zero.
Monitor Networking Activity0/20 points earned
Failed test case: Error occurred during monitoring: An error occurred (AccessDenied) when calling the DescribeAutoScalingGroups operation: User: arn:aws:sts::240302954031:assumed-role/voclabs/user4778468=wzghhjbvhcnu is not authorized to perform: autoscaling:DescribeAutoScalingGroups with an explicit deny in an identity-based policy: arn:aws:iam::240302954031:policy/voc-cancel-cred.
Expected:
None,
but got:
None.
Change of ALB Security Group Inbound Rules0/20 points earned
Failed test case: Error occurred while checking ALB Security Group inbound rules: An error occurred (UnauthorizedOperation) when calling the DescribeSecurityGroups operation: You are not authorized to perform this operation. User: arn:aws:sts::240302954031:assumed-role/voclabs/user4778468=wzghhjbvhcnu is not authorized to perform: ec2:DescribeSecurityGroups with an explicit deny in an identity-based policy: arn:aws:iam::240302954031:policy/voc-cancel-cred.
Expected:
None,
but got:
None.
Execution of Launch Template0/30 points earned
Failed test case: Error occurred while verifying EC2 instances: An error occurred (UnauthorizedOperation) when calling the DescribeInstances operation: You are not authorized to perform this operation. User: arn:aws:sts::240302954031:assumed-role/voclabs/user4778468=wzghhjbvhcnu is not authorized to perform: ec2:DescribeInstances with an explicit deny in an identity-based policy: arn:aws:iam::240302954031:policy/voc-cancel-cred.
Expected:
None,
but got:
None.
Creation of Dynamic Scaling Policy0/30 points earned
Failed test case: Error occurred while verifying the scaling policy: An error occurred (AccessDenied) when calling the DescribeAutoScalingGroups operation: User: arn:aws:sts::240302954031:assumed-role/voclabs/user4778468=wzghhjbvhcnu is not authorized to perform: autoscaling:DescribeAutoScalingGroups with an explicit deny in an identity-based policy: arn:aws:iam::240302954031:policy/voc-cancel-cred.
Expected:
None,
but got:
None.
Hello @romeopeay I’m really sorry about this. Looking at your logs, I think that maybe your session finished between the time you finished your lab and when you submitted. Please try to complete everything within a 2 hour period. Please keep in mind that if you start the lab, then leave, and return back all within the 2 hour span, you will be assigned to the first session, so you could be a bit rushed to finish
UPDATE: I was able to replicate your error messages by letting my learner session to expire (waited +2 hours) and then submitted, so that was the issue with your submission.
2 Likes
Perhaps the lab could include some way to notify a learner when their session has expired, to make this easier to diagnose.
1 Like
@magdalena.bouza @TMosh Thanks for looking into this. The real deal is that completing the labs on the console is faster than from the AWS CLI. The console is good for prototyping and experimentation. But the AWS CLI shines in automation. I’m familiar enough with the lab now, so I will be able to complete the lab more quickly this weekend. Thanks again.