I completed the task and ran the check, but it starts shutting down the lab saying the task was not completed successfully. I ran the lab twice, same error.
I believe you; I tried this using the console, and it failed. I tried the lab again, though, using the CLI, and it worked:
aws-client ~ ➜ echo i-04102d6cfed76d51e
i-04102d6cfed76d51e
aws-client ~ ➜ aws ec2 describe-instance-attribute --instance-id i-04102d6cfed76d51e --attribute disableApiStop --query "DisableApiStop.Value"
false
aws-client ~ ➜ aws ec2 modify-instance-attribute --instance-id i-04102d6cfed76d51e --disable-api-stop
aws-client ~ ➜ aws ec2 describe-instance-attribute --instance-id i-04102d6cfed76d51e --attribute disableApiStop --query "DisableApiStop.Value"
true
aws-client ~ ➜
This may be a console bug, rather than our bug. But I’ll run the lab one more time to confirm this. If you want to just get past this task though, use the CLI and see if that works for you.
Just tried the lab again. Yeah, this appears to be an AWS Console bug – enabling stop protection in the console does not actually update stop protection, at least not immediately: I checked the UI, and it did not actually update. Curiously, checking with the CLI with describe-instance-attribute did indicate it was; when I refreshed the console after I did this, the console’s display did now indicate this.
May be an AWS issue, or it does the update with a lag, which is still an AWS issue. So for now, use the CLI for this task, and avoid the mystery ![]()
hi follow this video tutorial and star my repo if it helps.