Automating AWS Services with Scripting and the AWS CLI

Go to Lab

836 Reviews

Daniel L. · Reviewed about 7 hours ago

Dimitar M. · Reviewed 1 day ago

Luis M. · Reviewed 4 days ago

Sebastian S. · Reviewed 5 days ago

lab environments runs so slow

Robert L. · Reviewed 5 days ago

Noor S. · Reviewed 6 days ago

くりす F. · Reviewed 6 days ago

Sam Z. · Reviewed 6 days ago

Trinh T. · Reviewed 7 days ago

Jyotiranjan S. · Reviewed 10 days ago

Astrum T. · Reviewed 10 days ago


Lois G. · Reviewed 10 days ago

This lab does not work. Setting up the bastion is incorrect since for some reason my EC2 says it's in the default VPC when I run the script even though it shows in the Lab-VPC on management console

Ruben L. · Reviewed 10 days ago

Tim F. · Reviewed 11 days ago

Gabe P. · Reviewed 11 days ago

Wen-Hsiang C. · Reviewed 13 days ago

bipul k. · Reviewed 14 days ago

Unable to create ingress rules via provided cli command as sg are not created in default vpc, have to stop instances using script but unable to restart instances from the console ... Not pleased at all with this lab.

Gui L. · Reviewed 14 days ago

An error occurred (InvalidGroup.NotFound) when calling the AuthorizeSecurityGrou pIngress operation: The security group 'Bastion' does not exist in default VPC ' vpc-a84e3dcd' The whole bastion automation section did not work.

Draconis N. · Reviewed 17 days ago

Stephen P. · Reviewed 18 days ago

Girish P. · Reviewed 20 days ago

Troy L. · Reviewed 22 days ago

Daniel C. · Reviewed 23 days ago

Paulo C. · Reviewed 23 days ago

I can learn more about AWS CLI.

顏 文. · Reviewed 25 days ago