This is an optional step. If you experience problems during deployment, you will need to investigate the status of the CodeDeploy agent on the virtual machines. Or even if you don’t have any issues to track down, you can find out what the Heartbeat service is up to. To connect to Windows virtual machines you must use the PEM file containing the KeyPair generated during the installation process, to decrypt the Windows password, and then use the Microsoft Remote Desktop client to connect to the virtual machine.
Use password and RDP file to access to Windows virtual machine.
In Windows virtual machine, open c:\temp\host-agent-install-log file.
Check and make sure that there are no lines with errors, such as: Failed to connect to server because this is an error that occurred during the installation.
If something goes wrong during the installation, you can try re-running it yourself with the following commands:
c:\temp\codedeploy-agent.msi /l*v c:\temp\host-agent-install-log.txt
aws deploy create-deployment --application-name idevelopDemo --deployment-group-name HeartbeatInstances --deployment-config-name CodeDeployDefault.AllAtOnce --description "Retrying Initial Deployment" --s3-location bucket=idevelop-codedeployartefacts-<yourinitials>,key=CodeDeployHearbeatDemo.zip,bundleType=zip
Replace with your name the same as the name of the S3 bucket created in the previous step. The ZIP file will be copied to the S3 bucket.
Assuming the CodeDeploy agent is successfully installed and running, and you want to confirm the deployment of the Heartbeat service successfully, you can perform the following steps:
[INFO]09/14 08:33:18 - Initialising Heartbeat Service...
[INFO]09/14 08:33:18 - Heartbeat Service is now running...
[INFO]09/14 08:33:18 - Heartbeat - Deploy has Worked on Tuesday! Iteration 1
[INFO]09/14 08:33:19 - Heartbeat - Deploy has Worked on Tuesday! Iteration 2
...
...