Configurar um balanceador de carga de aplicativo com escalonamento automático (AWS) avaliações

Andrew P. · Revisado há about 2 years

Mahmoud B. · Revisado há about 2 years

Alejandro H. · Revisado há about 2 years

Jaime S. · Revisado há about 2 years

Shreyas R. · Revisado há about 2 years

Cassio B. · Revisado há about 2 years

Kyaw (Steve) T. · Revisado há about 2 years

Anrie S. · Revisado há about 2 years

Eric P. · Revisado há about 2 years

Multiple attempts to run f1 instances as directed, then tried n1 instances but none available in us-west-1 Instead I chose an E instance and I think this is why I got the popup "We are ending this lab because we have detected you are not following the lab instructions..." I mean what else am I supposed to do with the lab half completed and the clock ticking down for when the lab will be closed? I think a little more lenience would be good. Also multiple Chrome browser tab crashes... I closed down other tabs and other apps but it continued to happen. This may be an issue on my side but nonetheless it only added to the frustration.

Toby R. · Revisado há about 2 years

Though configured correctly, the progress check is failing

Venkata K. · Revisado há about 2 years

Dr. Kondala Kameswara Rao N. · Revisado há about 2 years

Console is so piggish, my browser and entire machine locked up multiple times. I ran out of time on the first attempt - you need at least 4 hours for this. Also, instructions are so outdated, there is no f1-micro in N1 anymore, and IPV4 wasn't an option for multiple steps, and labels are all wrong (http-backend on monitoring LB). If you decide to actually QA your labs, reach out to me, I am available for work.

Phillip B. · Revisado há about 2 years

Deyana N. · Revisado há about 2 years

Aryan P. · Revisado há about 2 years

Steven Q. · Revisado há about 2 years

Lismar O. · Revisado há about 2 years

Isaac M. · Revisado há about 2 years

Steven S. · Revisado há about 2 years

James C. · Revisado há about 2 years

Was fine until the end when I couldn't launch the stress-test VM because GCP is too busy

Chris B. · Revisado há about 2 years

Alexey P. · Revisado há about 2 years

Duc N. · Revisado há about 2 years

mohammaderfan k. · Revisado há about 2 years

Ankit G. · Revisado há about 2 years