1. Home
  2. Release Management Tools
  3. AWS CodePipeline Reviews
  4. User Review of AWS CodePipeline
AWS CodePipeline Review
June 03, 2021

AWS CodePipeline Review

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with AWS CodePipeline

CodePipeline is used by many development teams across the company. We are a heavy GitHub Enterprise user, but those who are seeking a CI/CD type product that has a slick integration with GitHub AND native AWS support - those users always go to CodePipeline. It can also integrate with S3 which is a huge advantage for those who have code files deployed in AWS already and can blend them with files from their teams enterprise GitHub repos. Some of our users also rely on CodeCommit and have integrated CodePipeline with that service as well. The major problem it solves for us is ease of integration and the ability to fully automate + test a release.
  • ease of use
  • multiple service integrations
  • option for container (ECS) support
  • automatic change detection
  • no local integration
  • interface limitations
  • time to setup
  • API access
  • GitHub Enterprise integration
  • AWS native integrations
  • workflow modeling
  • reduced cost
  • reduced 'man hours'
  • lowered risk of pushing bad deployment
CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.

CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.

Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.

Do you think AWS CodePipeline delivers good value for the price?

Yes

Are you happy with AWS CodePipeline's feature set?

Yes

Did AWS CodePipeline live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of AWS CodePipeline go as expected?

Yes

Would you buy AWS CodePipeline again?

Yes

CodePipeline is well suited for an already existing AWS-native deployment. It is very easy to connect to existing repos like GitHub enterprise or cloud repos like CodeCommit. Being able to define the process by code (YAML) is a huge benefit for developers who favor that type of deployment setup. The UI is easy to use yet very powerful and customizable. Being able to leverage CloudTrail or Lambda is quite powerful, especially in larger more complex projects.
It becomes less valuable with smaller projects or locally hosted deployments that don't get the benefits of a managed service in the AWS ecosystem. However, there are agents that can be run on private servers to allow integration. But naturally, smaller one-off projects benefit less from the automation value derived by CodePipeline.