Differences

This shows you the differences between two versions of the page.

--- bloglike:2021-06 [2021/06/04 09:18] – AWS CodeBuild and CloudWatch Logs integration stybla
+++ bloglike:2021-06 [2021/06/17 04:50] – When AWS CodeBuild and CloudWatch logs integration doesn't work stybla
@@ Line 9: / Line 9: @@
 It looks alright and usable, especially logs available in build status. Better than fishing logs from S3.
+ --- //[[stybla@turnovfree.net|Zdenek Styblik]] 2021/06/04 15:06//
+===== When AWS CodeBuild and CloudWatch Logs integration doesn't work =====
+Previously, I was praising AWS CodeBuild and CloudWatch Logs integration. Today, it's something else :) I was in need of quick-and-dirty CodeBuild project in order to try something. I've made couple mistakes along the way, but I still think and it's possible there are cases when logs won't appear in CloudWatch and when you still need to offload logs to S3 bucket.
+<code>
+[Container] 2021/06/14 15:05:28 Waiting for agent ping
+[Container] 2021/06/14 15:05:31 Waiting for DOWNLOAD_SOURCE
+[Container] 2021/06/14 15:05:32 Phase is DOWNLOAD_SOURCE
+[Container] 2021/06/14 15:05:32 CODEBUILD_SRC_DIR=/codebuild/output/src123899037/src
+[Container] 2021/06/14 15:05:32 YAML location is /codebuild/readonly/buildspec.yml
+[Container] 2021/06/14 15:05:32 Phase complete: DOWNLOAD_SOURCE State: FAILED
+[Container] 2021/06/14 15:05:32 Phase context status code: YAML_FILE_ERROR Message: wrong number of container tags, expected 1
+</code>
+btw there was no ''version: 0.2'' in buildspec file.
+<code>
+[Container] 2021/06/14 15:46:59 Waiting for agent ping
+[Container] 2021/06/14 15:47:02 Waiting for DOWNLOAD_SOURCE
+mounting '127.0.0.1:/' failed. connection reset by peer
+</code>
+I had to setup S3 bucket(so much for quick) in order to get to the bottom of what exactly is wrong.
+ --- //[[stybla@turnovfree.net|Zdenek Styblik]] 2021/06/17 09:47//