While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• Would be great to figure out some magic to add template validation testing in CircleCI
• Maybe a Rakefile task?

The documentation indicates

If you discover bugs while in Production, you can revert to previous application version by clicking and approving the change again.

Does this imply you need to revert code and re-commit to have the pipeline build again, or is there a way to simply flip the blue/green deployments back to the previous version. The later would be preferable. In this case would a

The module outputs the param codebuild_badge_url (as documented in the Outputs section of README) but seems like there is no input variable called badge_enabled. Seems like a simple fix and would be greatly appreciated if this could be added. Thanks

Add WAF to CloudFront (web-ui) and web service load balancers. Note that once #5 is complete, WAF should be added to APIGW instead.

The IAM policy for the role allows * too too many aws services without resource restrictions. Allowing a var supplied policy here could be a good first step. (https://github.com/cloudposse/terraform-aws-ecs-codepipeline/blame/master/main.tf#L66-L87).

IMHO you can use Makefile to organize the vars changes and big commands (if you add terraform inside docker commands)

If you name your stack - sagemaker-pipeline, the stack creation will fail because of S3 bucket name clash with the original author's buckets.