MemberMay 16, 2020 at 6:32 pm
Question: You are using a cluster of Amazon Linux EC2 instances to host an online forum. AWS CodeDeploy is used for deploying the new version of the application. The AppSpec file has been modified to use custom, non-default settings to fit your application deployment needs. You configured a deployment script during the lifecycle event to download the application code and install a few packages needed for operation. This deployment script completes in about 1 to 2 minutes. During deployment, CodeDeploy reports that the deployment has failed but upon checking the generated logs, the deployment script has successfully finished.
Which of the following could be the possible cause of the failed deployment?
The correct answer is: CodeDeploy has reached timeout while waiting for the long-running script to finish.
The option that says: CodeDeploy has reached timeout because of misconfigured health check on ALB is incorrect because even if the ALB health checks are configured properly, the deployment will still fail if CodeDeploy reaches the default 60-second timeout.
Checking the AWS documentation, for CodeDeploy the default timeout in the hooks section is 1 hour (3600 seconds). However, in the explanation, it mentions the default timeout is 60 seconds. I’m a bit confused where the default 60-second timeout came from. Is this for something different?
AdministratorMay 18, 2020 at 3:25 pm
Thank you for bringing this up to our attention. Yes, the default timeout is 1 hour (3600 seconds). In the scenario, it says that the AppSpec file has been modified to use custom, non-default settings to fit the application deployment needs. This means that the default timeout value is not used, but a custom value (less than 1 hour, or perhaps, just 1 minute).
I acknowledge that the explanation incorrectly said that the default timeout is only 60 seconds. I have rectified this issue and the change will be reflected in our practice tests soon.
Jon Bonso @ Tutorials Dojo
Log in to reply.