This article is a machine translation of the contents of the following URL, which I wrote in...

What's Changed Add support for waiting on specific CodeDeploy lifecycle events by @moznion in #884 refactor parsing --wait-until=codedeploy: by @fujiwara in #886 all: run modernize happy by @zchee...

LocalStack 4.5 is now available! This release brings AWS Developer Tools support (CodePipeline, CodeBuild, CodeDeploy), enhanced AppSync WebSockets, API Gateway Canary Deployments, PostgreSQL 17 in…

In this blog, we'll walk through setting up a Blue-Green deployment strategy for a Next.js...

An exploration of the operational trade-offs, security responsibilities, and workload suitability when choosing between containerized and serverless deployment models on AWS.

For years, blue/green on ECS meant bolting CodeDeploy onto the side: a second service, an appspec.yaml, extra IAM roles. ECS does all of it natively now. Here's the new config, the lifecycle hooks, and what to know before you delete the CodeDeploy glue.

Deploy the same app with every CodeDeploy strategy — AllAtOnce, OneAtATime, HalfAtATime, and Blue/Green — then wire CloudWatch alarms for automatic rollback.

Deploy the same ECS Fargate application using CodeDeploy blue/green and ECS-native blue/green, compare lifecycle hooks, traffic shifting strategies, and rollback mechanics side by side, then use a decision framework to choose the right approach for your workload.

https://kakakakakku.hatenablog.com/entry/2025/07/19/082038

Learn three ways to deploy AWS Lambda functions safely with gradual traffic shifting and automatic rollback: raw CodeDeploy for the mechanics, SAM DeploymentPreference for real-world automation, and CodePipeline V2's native Lambda deploy action. Covers versions, aliases, routing weights, canary and linear strategies, pre-traffic hooks, and CloudWatch alarm-based rollback.

Amazon ECS デプロイツール、ecspresso v2.6.0 をリリースしました。 github.com 新機能 ECS Blue/Green デプロイ対応 これまで ECS では CodeDeploy と連携する形での Blue/Green デプロイがサポートされていましたが、先日 ECS deployment controller でのネイティブな Blue/Green がサポートされました。その対応が入っています。 aws.amazon.com 使い方としては特にこれまでと変わらず、サービス定義ファイルに B/G 用の属性を追加して ecspresso deploy するだけで…

Groups Conversations All groups and messages Sign in     Choosing between Amazon ECS Blue/Green Native or AWS CodeDeploy in AWS CDK 0 views Eyal Estrin unread, 12:30 PM (9 minutes ago)    to https://aws.amazon.com/blogs/devops/choosing-between-amazon-ecs-blue-green-native-or-aws-codedeploy-in-aws-cdk/ Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com Reply all Reply to author Forward

In this post, we explore the migration path from AWS CodeDeploy to Amazon ECS for blue/green deployments, discussing key architectural differences and implementation considerations. We examine three different migration approaches – in-place update, new service with existing load balancer, and new service with new load balancer – along with their respective trade-offs in terms of complexity, risk, downtime, and cost.

CodeDeployで更新するECS ServiceをCDK管理して失敗した話です。

kun432さんのスクラップ

Leverage my animation project https://frankhefeng.github.io/aws-ecs-deployment-strategy-animation/ to visually compare native AWS ECS Blue/Green, Linear, and Canary deployment strategies and simplify your CI/CD by skipping CodeDeploy.

この記事は、現在 Amazon ECS でのブルー/グリーンデプロイに CodeDeploy を使用しており、新しい Amazon ECS ネイティブなデプロイ戦略への移行を検討している組織を対象としています。 (1) 移行を計画する際に考慮すべき要因 (2) CodeDeploy の概念を ECS ブルー/グリーンデプロイの同等機能にマッピングすること (3) 移行戦略についてのガイダンスを提供します。