AWS CodeDeploy vs Spinnaker

AWS CodeDeploy automates application releases across development, test, and production environments. It deploys to Amazon EC2, AWS Fargate, AWS Lambda, and on-premises instances using in-place, canary, or blue/green methods. Rolling updates and deployment health tracking help limit disruption; when too many updates fail, CodeDeploy can stop a deployment and restore a previous revision. Teams can launch and monitor releases through the AWS Management Console, CLI, SDKs, or APIs. AWS CodePipeline and some AWS partners offer prebuilt CI/CD connections. For EC2, CodeDeploy works with Auto Scaling and can update an instance before it joins an Elastic Load Balancing load balancer. Amazon SNS can send deployment-event notifications by SMS or email. The service uses a file- and command-based installation model with an AppSpec configuration file and is platform and language agnostic. EC2 deployments have no additional CodeDeploy charge; on-premises updates cost $0.02 per instance update, with no minimum fees or upfront commitments. On-premises instances must connect to public AWS service endpoints. The free plan is listed at free.

Spinnaker is a free, open-source, self-hosted multi-cloud continuous delivery platform for releasing software changes. Its pipelines can run integration and system tests, manage server groups, monitor rollouts, and start from Git, Jenkins, Travis CI, Docker, or CRON events. Built-in blue/green and canary strategies are available, and teams can define custom strategies. Documented providers include AWS, Azure, Cloud Foundry, Google Compute Engine, Kubernetes, Oracle Cloud, and App Engine. At least one provider must be enabled and configured before applications can be deployed. CI integrations include Jenkins, Travis, AWS CodeBuild, Concourse, Google CodeBuild, and Artifactory; source integrations include GitHub, Bitbucket Server/Stash, and GitLab. Authentication supports OAuth 2.0, SAML, or LDAP, while authorization can use groups or team-based role providers. SSL secures UI and API communication. Kubernetes is the recommended installation route, with local Debian packages documented for smaller deployments. The local guide recommends at least four cores and 16GB RAM and warns that single-machine installations may have downtime.