{"provider_name":"Hatena Blog","categories":["AWS"],"type":"rich","author_url":"https://blog.hatena.ne.jp/tamago-engineer/","width":"100%","blog_url":"https://tamago-engineer.hateblo.jp/","published":"2018-01-20 23:51:12","image_url":null,"height":"190","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Ftamago-engineer.hateblo.jp%2Fentry%2F2018%2F01%2F20%2F235112\" title=\"AWS CodeDeploy logs that you should watch. - TRY AND ERROR\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","title":"AWS CodeDeploy logs that you should watch.","provider_url":"https://hatena.blog","url":"https://tamago-engineer.hateblo.jp/entry/2018/01/20/235112","description":"We have a web service with AWS, located in like below environment. (This time in case of using AmazonLinux) WebServer: - Production\uff1a - ALB * 1 - EC2 * 2 - Dev\uff1a - EC2 * 1 DB: - Production: Aurora * 1 - Dev: Aurora * 1 Our source code is managed by github organization account. And we're going to deplo\u2026","version":"1.0","blog_title":"TRY AND ERROR","author_name":"tamago-engineer"}