‫So now let's talk
‫about troubleshooting on CodeDeploy.
‫In case you have a deployment,
‫and then you get a deployment error
‫of invalid signature exception,
‫because the signature has expired,
‫and there is a time reference in this,
‫well, it's because CodeDeploy is trying to deploy
‫and then we get a signature exception.
‫This is an issue, because we have a time issue,
‫and this comes from missing accurate time references.
‫So what does it mean?
‫Well, we need to make sure that the time on CodeDeploy,
‫which is a time of AWS,
‫and the time on your EC2 instances,
‫which is whatever time you set it to be,
‫and it can be matching an external server for example.
‫So if your EC2 instance
‫or your servers do not have the correct time,
‫then CodeDeploy is going to reject
‫the deployment altogether.
‫This is because time is very important.
‫So the simple answer to fixing this is to make sure
‫that your EC2 instance is connected
‫to correct time server that is in sync with AWS.
‫If you also have deployment issues on EC2 instances,
‫they failed for whatever reason,
‫you have log files available on your EC2 instance.
‫So under the slash O-P-T CodeDeploy agent folder,
‫you will find the logs of the agent.
‫Okay, that's it for this lecture.
‫I hope you liked it.
‫And I will see you in the next lecture.