AWS CodeDeploy
CodeDeploy
You need to automate deployment updates to a supported compute platform with a defined rollout strategy.
Reach for it when
- Managing supported application deployments to EC2, on-premises instances, Lambda or ECS.
- Using a compatible rollout and health-check strategy to reduce release risk.
Do not reach for it when
- Provisioning an entire cloud architecture: use infrastructure as code.
- Assuming all deployment strategies are supported on every target platform.
Alternatives, and how to choose
| Service | Pick it instead when |
|---|---|
| CloudFormation | Create and update infrastructure resources. |
| A platform-native deploy workflow | Choose a deployment system matched to the hosting environment. |
How you pay
- The model
- Pricing depends on deployment target and related compute services.
- The line item that surprises people
- The target infrastructure continues to incur its own usage charges during deployment.
What trips people up
- Rollback restores an application revision under configured conditions; it does not automatically reverse incompatible data changes.
- Deployment hooks, permissions and health checks are part of the rollout design.
Verify the live service
This page is a concept reference. Cost models are qualitative; confirm the current offering, Region and pricing before deploying.