Grades issues with Assignment 2: Good Data Architecture

Course Q&A Data Engineering Introduction to Data Engineering
, ,
1

Monitor Networking Activity

Why?

Failed test case: Expected to generate stress test to increase Networking Activity.
Expected:
NetworkOut > 999999,
but got:
NetworkOut = 46208.0.

  • EC2 Service does not display instances (Policy issue)
  • Cloudshell is not enabled for the policy assigned (Policy issue)
  • Load Balancers do not display (Policy issue)

I was able to view the load balancer DNS, de-c1w3-alb-1425470307.us-east-1.elb.amazonaws.com, in the browser.

Since Cloudshell was not available, I could not install

  • sudo yum install httpd-tools -y
  • I cannot add this to User Data because permissions donā€™t allow stop and start

I used a workaround from the AWS CLI.

for i in {1..7000}; do curl -s http://curl http://de-c1w3-alb-1425470307.us-east-1.elb.amazonaws.com/ > /dev/null & done

This put the instance under stress.

Once again, the CloudWatch service was not available because of the configured policy.

Change of ALB Security Group Inbound Rules0/20 points earned

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.

  • I created a new rule and deleted the old ruleā€¦I verified connectivity.

Execution of Launch Template30/30 points earned

All tests passed! Congratulations!

Creation of Dynamic Scaling Policy0/30 points earned

Failed test case: Dynamic scaling policy ā€˜de-c1w3-scaling-policyā€™ was not found for ASG ā€˜c62825a3581670l13652295t1w240302954031-AutoScalingGroup-Dnn0w9uLUNbgā€™..
Expected:
None,
but got:
None.

I created a new de-c1w3-scaling-policy for 2 t3.nano. Both started. The t3.micro instances were terminated. I created a scaling group. Since Cloudshell was not working, I used the AWS CLI to run:

for i in {1..1000000}; do curl -s http://de-c1w3-alb-1425470307.us-east-1.elb.amazonaws.com/ > /dev/null & done

Lab ID

wzghhjbvhcnu

Iā€™m working the problems but Iā€™m not getting credit.

2

Iā€™m not seeing any resolutions to reported problems like this in over a year. We are taking the time to post problems. The least we deserve is acknowledgement from technical that they are or are not working on the issue. Not a bot. Not a student rep. Not for points when a comment is written. A real response.

3

@romeopeay Iā€™m forwarding your post to our tech team and also trying to recreate your issue.
Give it some time, please.

4

Thanks for responding.

5

@romeopeay you mentioned that because of Policy issues EC2 Service and Cloudshell are not enabled. Could you check, please, if you are logged in with the lab account or your personal account?

6

I mentioned the policy issue because in the console, I do not have access because the service does not display or the message displays that I donā€™t have access. I verify my access by executing AWS CLI commands that tell me the user we are assigned as does not have access because the policy is not configured to allow access.

I have attempted to start the lab a few times today. It appears, I am stuck in the loop of my last active session. I have rebooted and updated but the last session will not end. When I execute the first command, ā€œcat ../.aws/aws_console_urlā€ the AWS Console URL does not load. It doesnā€™t load because the file is nearly empty. Linux comman ls -la ../.aws/aws_console_url returns a nearly empty file: -rw-rā€“r-- 1 root root 1 Feb 10 18:28 ../.aws/aws_console_url. I cannot get to the console without the URL.

7

You need to walk away for at least 2 hours, so your session will time-out and be erased.

8

That did not resolve my issue. Thanks

9

@juliak I am still unable to access the console ā€¦ because cat ../.aws/aws_console_url is empty. From the AWS CLI, I cannot get a response to describe the target group

aws elbv2 describe-target-groups --region us-east-1

Normally, I would get a response about the load balancerā€¦

The response is: An error occurred (InvalidClientTokenId) when calling the DescribeTargetGroups operation: The security token included in the request is invalid.

10

I just want to level set the issueā€¦. originally, I opened this conversation because the grade I was getting was not reflective of the tasks I completed. The grading system is telling me it does not see certain values, therefore the task is not complete. Other enrolleeā€™s complain of the same issue.

Cloudshell, EC2, Load Balancer, CloudWatch do not display when the console is available. The IAM role assigned to us for this activity does not have the correct policy/permissions assigned to it.

Autoscaling groups and Security Group do display. I use the AWS CLI to complete most of the tasks.

Weā€™ve moved on from the grading issue to not being about to access the console because the link is not populating in the virtual environment like normal.

11

Grading issue is related to your not being able to access the console.
The task was to add a new inbound rule for the ALB Security Group, not delete an old one.
Iā€™ve just tried to recreate your issue and hit the same IAM policy issue when trying to modify the existing inbound rule. With adding a new rule this section was graded 20/20.

AWS CLI is ok, but I think it would be easier via AWS console. Via CLI you might accidentally attach a rule to a wrong group, so the grader didnā€™t give a credit for that.
@romeopeay

12

I am still unable to reach the console. I am also not able to use the AWS CLI (Invalid token).

The task is to add an inbound rule to the ALB security group. I added rule to the load balancer security group. I deleted the old load balancer security group afterward. This is the one activity Iā€™m not having an issue with. So, I agree 20/20.

For this activity, the Console is definitely easier but so many of the services that activity calls for are not available with the role assigned (EC2, CloudWatch, Load Balancer, Cloudshell). Is someone going to fix this or is my only hope the AWS CLI?

13

@romeopeay It may take some time to fix this. Meanwhile are you able to complete it with AWS CLI?
As far as I understand, only ā€œCreation of Dynamic Scaling Policy 0/30 points earnedā€ is left.

14

I can complete all of the activities using the AWS CLI. However, when the activity is graded, the scorer is searching for a values that are different than mine. Also, this assignment was due Feb 11, so Iā€™ve run out of time.

15

As far as I remember learners are not penalized for completing labs after due date.

1 Like
16

Hi @romeopeay . Iā€™m looking into this right now. If you could clarify a couple of things that would help a lot.

  1. If you go to the AWS dashboard, you donā€™t have access to CloudShell? Iā€™m testing the lab as a learner, and Iā€™m being able to access and install the required packages. I also have access to CloudWatch.

I think there might have been an error when setting up your environment, or maybe you are connected on another AWS session? You session appears as terminated, so if you reopen the lab you should get a new session with new resources.
Please let me know if you see any change in behavior

1 Like
17

@magdalena.bouza When I was able to log into the console, EC2 instances did not display. There was an unauthorized message. The same for CloudWatch widgets (CPU, Memory, etc), CloudShell, Load Balancers, etc. I was able to reach these services by way of the AWS CLI.

Iā€™ll try opening the activity again now. When I open the lab, it loaded. However, when I executed ā€œcat ../.aws/aws_console_urlā€ in the terminal session, nothing appeared. The file is empty. It is supposed to have the AWS Console HTTP link. So, I cannot access the lab this way.

18

@romeopeay, it seems the resources were not created if you are not seeing the AWS Console link. Could you please try rebooting your lab and try again? I donā€™t see your session active on Vocareum, in fact you last initiated session for this lab was on Feb. 9th. To reboot, click on the question mark symbol on the top right of the lab and click on Reboot. Please let me know if this fixes the issue

19

@magdalena.bouza Iā€™ve rebooted several times but seem to be accessing the same session without acquiring new files/configurations. I have rebooted several times with the same result. What AWS IAM role are you using? Is it the same as the lab IAM role? If not, that might explain why you are seeing a different result.

Please inform management that the main reason Iā€™m taking this course is because of the hands on labs. So, if the labs are down, Iā€™m not getting the value I expect. However, I do understand that the infrastructure is ephemeral and there are many users trying to access it and the resources. I just need to know that I wonā€™t be penalized or held back from completing the courses.

20

@romeopeay thanks for your patience through all this.
I am using the resources of the lab (I started the lab as a learner), so we should be seeing the same behavior.
Just to clarify, what do you mean you are not getting new files/configurations? Rebooting does not affect the files in your directory. If you think there might be something wrong with the files, you need to delete the files from your directory (only the ones originally shown to you) and click on the ā€œget latest versionā€ option. If you want to keep track of your progress you can download your files before doing that. Also, after rebooting, do you get the link to AWS console, or is that still coming blank?
As far as I can tell the lab is not down, but Iā€™m not sure why you are not getting the correct resources.