Configuring an HTTP Load Balancer with Google Cloud Armor Reviews
20148 reviews
Maurizio C. · Reviewed over 5 years ago
this is most unfair lab and dissapointed with error
Cheong T. · Reviewed over 5 years ago
Ransford O. · Reviewed over 5 years ago
Josephat p. · Reviewed over 5 years ago
Alex T. · Reviewed over 5 years ago
Great
Nicola B. · Reviewed over 5 years ago
Priya G. · Reviewed over 5 years ago
Chun W. · Reviewed over 5 years ago
Othman K. · Reviewed over 5 years ago
LTI S. · Reviewed over 5 years ago
Chua T. · Reviewed over 5 years ago
LTI S. · Reviewed over 5 years ago
a few tricky bits. Needed to ssh via cloudshell, also took more than a few minutes for LB to healthcheck, and cloud armour rules to kick in.
Sam Y. · Reviewed over 5 years ago
no se carga los pasos ya realizados
PAEZ S. · Reviewed over 5 years ago
ANTONY NIRMAL RAJ A. · Reviewed over 5 years ago
Damian C. · Reviewed over 5 years ago
Jennifer P. · Reviewed over 5 years ago
Francis Alberto V. · Reviewed over 5 years ago
Nilesh P. · Reviewed over 5 years ago
Step 3, for europe-west1, shall have instructions to create metadat with startup scripts and network tag
Marimuthu P. · Reviewed over 5 years ago
Rodrigo M. · Reviewed over 5 years ago
great concept but the set up has the siege-vm address change with every request as it hits the load balancer. so the cloud armor rule to block the request is meaningless. Also the load probably with the ip shifting did not push the instance above 10%. there as a huge throttle in place on siege as well. i stopped going into to configure that, considered ab but that's just overkill - i think the set up of the lab needs to be narrowed to trigger the load and blocks -- conceptually i know what i was meant to see - but this lab really doesn't get there currently - revisit with current state of GCP - maybe some defaults have changed -- i could have missed something -- double checked all the names ..
Joshua L. · Reviewed over 5 years ago
Nicholas H. · Reviewed over 5 years ago
Trony C. · Reviewed over 5 years ago
Graham R. · Reviewed over 5 years ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.