-
Updated
Mar 1, 2020
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
Demo code for running Ruby Sinatra on AWS Lambda
AWS Lambda boilerplate for Node.js 6.10, adding ES2018/7/6 features, Docker-based unit testing and various CI/CD configurations
Terraform module to build Docker image with Jenkins, save it to an ECR repo, and deploy to Elastic Beanstalk running Docker stack
A collection of higher-level aws cdk constructs: slack-approval-workflow, #slack & msteams notifications, chatops, blue-green-container-deployment, codecommit-backup, OWASP dependency-check, contentful-webhook, github-webhook, stripe-webhook, static-website, pull-request-check, pull-request-approval-rule, codepipeline-merge-action, codepipeline-check-parameter-action...
Source code samples for DevOps Essentials on AWS Complete Video Course
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
AWS-powered serverless build, test and deploy pipeline ft. multiple environments
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).
An approach for GitOps of AWS backing resources like databases with CodePipeline together with Kubernetes via Flux
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.
Digging into DevOps with AWS and Terraform
Example of a Ubiquiti Unifi Controller in AWS using Network Load Balancer for TLS termination
Automated Lambda Deployments with Terraform & CodePipeline
Pipeline to build, test and deploy Serverless Framework Projects with CodeBuild and CodePipeline on AWS using Terraform.
dadoune.com static site generator
Terraform module for deploying Atlantis as an ECS Task
Serverless stack with CI/CD & blue-green deployments - API + Static UI + Async Tasks
Tool for monitoring AWS CodePipeline status and pushing events to Datadog, Slack and Cloudwatch.
Test IAM Policies in Multi Account Structures in your CI/CD pipeline
Lambda function for updating the commit status on GitHub based on CodePipeline execution state changes.
A template for deploying Laravel 5 with AWS Codepipeline
Add a description, image, and links to the codepipeline topic page so that developers can more easily learn about it.
To associate your repository with the codepipeline topic, visit your repo's landing page and select "manage topics."
While testing another PR, I found that
mu pipeline logscommand displays information from the pipelines, but also shows this error:This error does not occur with the `-f