deployment configuration
The CodeDeploy rule for how fast a release moves, such as all at once, half at a time, one at a time, or a canary or linear traffic shift.
In more detail
For EC2 it sets how many instances must stay healthy while others update. For ECS and Lambda it sets how traffic moves to the new version: all at once, a canary share and then the rest, or equal steps every few minutes. A slower configuration gives alarms time to catch a bad release before every customer sees it.
Related terms
- AWS CodeDeploy — The AWS service that rolls a new application revision out to EC2 instances, ECS services or Lambda functions, and can roll it back automatically.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- linear deployment — A release that moves traffic to the new version in equal steps at fixed intervals, such as 10 percent every minute, until all traffic has moved.
Taught in
- Two Hundred Accounts And One Bad Deploy — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- CodeDeploy: Hooks That Never Ran — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Strategies Across Compute: The Canary That Saw Nothing — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Troubleshooting Failed Deployments: Read The First Failure — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Long-Stem Clinic: When Two Answers Both Work — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep