Configuring Network Connectivity Center as a Transit Hub avis

Mohinder R. · Examiné il y a 5 mois

Way too long.... Why not just configure all this using cloud shell? This is kind of ridiculous.

Christopher H. · Examiné il y a 5 mois

Bad indications

Domiciano A. · Examiné il y a 5 mois

Prashant S. · Examiné il y a 5 mois

Ahmed H. · Examiné il y a 5 mois

Levin Madhu Sudhan M. · Examiné il y a 5 mois

Shahbaz Ikram B. · Examiné il y a 5 mois

Andrey R. · Examiné il y a 5 mois

The info was wrong for vpc-b-vm-1 in the spreadsheet. It caused some confusion when it didn't work the first time.

Dirk P. · Examiné il y a 5 mois

Dirk P. · Examiné il y a 5 mois

Justin R. · Examiné il y a 5 mois

Ramkumar D. · Examiné il y a 5 mois

Prabhu V. · Examiné il y a 5 mois

Juan Ramon V. · Examiné il y a 5 mois

Daman K. · Examiné il y a 5 mois

Need to use better naming convention. Also tunnels should be numbers 1,2,3,4 ....also ther aer some typos making it even more confusing.

Vimal P. · Examiné il y a 5 mois

Anindya S. · Examiné il y a 5 mois

Sergei L. · Examiné il y a 5 mois

Hymavathi l. · Examiné il y a 5 mois

Vimal P. · Examiné il y a 5 mois

This Lab can not be completed. The VPC and region mapping is messed. vm1 expected in us east region , to be created in vpc a, where as in vpc a there is only one subnet in us east region.

Pravin B. · Examiné il y a 5 mois

Xavier R. · Examiné il y a 5 mois

Task with vpc-b-vm-1 is not clear. It tells user to create vm in the same zone as vpc-a-vm-1. In this case it is impossible to connect vpc-b-vm-1 to vpc-b. Instruction has to be updated to use the same region as vpc-b is using.

Bruno S. · Examiné il y a 5 mois

Piotr K. · Examiné il y a 5 mois

Kartik G. · Examiné il y a 5 mois