Analyzing Network Traffic with VPC Flow Logs Reviews

Noreen Jade L. · Reviewed 4 days ago

Reetayan M. · Reviewed 4 days ago

Cameron M. · Reviewed 4 days ago

Rishav J. · Reviewed 4 days ago

Rishav J. · Reviewed 4 days ago

Martyna G. · Reviewed 4 days ago

柏緯 江. · Reviewed 5 days ago

Sambit P. · Reviewed 5 days ago

Chandrashekhara N. · Reviewed 5 days ago

the section to create bq_vpcflows is not clear.the data didnt loaded to table.

Malinda P. · Reviewed 5 days ago

Aasheesh K. · Reviewed 5 days ago

Durga Prasad A. · Reviewed 5 days ago

Durga Prasad A. · Reviewed 5 days ago

good

Mahesh A. · Reviewed 6 days ago

Wenbo Y. · Reviewed 6 days ago

Jason L. · Reviewed 6 days ago

Good job!

Hải N. · Reviewed 6 days ago

good

Mahesh A. · Reviewed 6 days ago

Olmo R. · Reviewed 7 days ago

Step 2 (Create an Apache web server), completly bug

Lukas O. · Reviewed 7 days ago

I still get pass the check mark for the apache being installed on the VM. from gemini (inside console.cloud.google.com): I have thoroughly investigated your web-server VM instance, network configuration, and system logs to see why your progress check might be failing. Investigation Findings All of your Google Cloud resource configurations are 100% correct and perfectly match the instructions: VM Name: web-server (Running) Zone: us-east4-a Machine Type: e2-micro Network / Subnetwork: vpc-net / vpc-subnet (IP 10.1.3.3) Network Tag: http-server is correctly assigned to the VM. Firewall Rules: There are active ingress firewall rules on vpc-net (vpc-net-allow-http and allow-http-ssh) allowing TCP port 80 traffic to instances tagged with http-server. Apache Service Status: VM system boot and application logs confirm that the Apache service (apache2.service) successfully installed and started running. also, how could I have completed all other steps if the first one failed. This is just sad checking progress :)

Mikael F. · Reviewed 7 days ago

The Labs Web server step check fails.

David C. · Reviewed 7 days ago

Step 2 (Create an Apache web server), completly bug

Lukas O. · Reviewed 7 days ago

i had a vm named web-server with e2 micro us-region1-a on the specific subnet with apache2 installed and the custom landing page loaded. i could load it in the browser still it didn't like it. restarting the lab to see what I did wrong perhaps. sigh. second time same problem, maybe i'm utterly blind today.

Olmo R. · Reviewed 7 days ago

akash y. · Reviewed 7 days ago