AWS CodePipeline vs. CircleCI

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
AWS CodePipeline
Score 9.2 out of 10
N/A
AWS CodePipeline is a fully managed continuous delivery service that helps users automate release pipelines for fast, reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the release model a user defines. This is to enable rapid, reliable delivery of features and updates. Users can integrate AWS CodePipeline with third-party services such as GitHub or with a custom plugin. AWS…
$1
per active pipeline/per month
CircleCI
Score 8.4 out of 10
N/A
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$0
per month
Pricing
AWS CodePipelineCircleCI
Editions & Modules
AWS CodePipeline
$1
per active pipeline/per month
Free Tier
Free
Free
$0
per month
Performance
$30
per month
Server
$35
per month
Scale
Custom Pricing
Offerings
Pricing Offerings
AWS CodePipelineCircleCI
Free Trial
NoNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
AWS CodePipelineCircleCI
Considered Both Products
AWS CodePipeline
Chose AWS CodePipeline
I felt that, out of the alternatives, AWS CodePipeline was the simplest to setup and most reliable. Since my client's infrastructure was already hosted in AWS, I felt it was a no-brainer. If a client needed a similar solution with on-prem or non-AWS infrastructure, I would …
Chose AWS CodePipeline
AWS Codepipeline is proprietary to Amazon Web Services and works well when you're working with other AWS products. If you're using a different technology stack, then Codepipeline may not be the best tool and some open source/closed source tools available on the web may suffice.
Chose AWS CodePipeline
They all pretty much have the same feature set. AWS CodePipeline has been improving in recent years, and it just makes sense to keep everything within Amazon's ecosystem.
CircleCI
Chose CircleCI
CircleCI is still being developed and worked on continually while TravisCI is not.
Top Pros
Top Cons
Best Alternatives
AWS CodePipelineCircleCI
Small Businesses
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
Ansible
Ansible
Score 9.0 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
Ansible
Ansible
Score 9.0 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AWS CodePipelineCircleCI
Likelihood to Recommend
9.0
(8 ratings)
8.0
(26 ratings)
Usability
9.0
(1 ratings)
10.0
(1 ratings)
Performance
6.8
(2 ratings)
7.8
(3 ratings)
Support Rating
9.1
(2 ratings)
6.9
(6 ratings)
Ease of integration
7.4
(2 ratings)
-
(0 ratings)
User Testimonials
AWS CodePipelineCircleCI
Likelihood to Recommend
Amazon AWS
I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.
Read full review
CircleCI
CircleCI is perfect for a CI/CD pipeline for an app using a standard build process. It'll take more work for a complex build process, but should still be up to the task unless you need a lot of integrations with other tools. If you have a big team and can spare someone to focus full time on just the CI/CD tools, maybe something like Jenkins is better, but if you're just looking to get your app built, tested, and delivered without a huge amount of effort, CircleCI is probably your preferred tool.
Read full review
Pros
Amazon AWS
  • It is reliable and works without errors
  • It integrates well with our repository and all other AWS functions as well as our end database
Read full review
CircleCI
  • Multiple builds can be run at the same time in parallel.
  • The CircleCI web interface (UI/UX) is very easy to understand and use.
  • Easy Configuration to learn and use. Just a single configuration YAML file.
  • Many integrations. We use the GItHub, Slack, and DataDog integrations.
Read full review
Cons
Amazon AWS
  • Ease of use - things like CircleCI or other tools are a bit easier to learn.
  • Ability to build from more sources.
Read full review
CircleCI
  • The "phases" their config file uses to separate out options seem very arbitrary and are not very helpful for organizing your config file
  • No way that I know of to configure which version of MongoDB you use. You have to write your own shell script to download and start MongoDB if you want a specific version.
  • Hard to access build artifacts in the UI
Read full review
Usability
Amazon AWS
Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.
Read full review
CircleCI
CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in
Read full review
Performance
Amazon AWS
Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.
Read full review
CircleCI
It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Read full review
Support Rating
Amazon AWS
We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.
Read full review
CircleCI
Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Read full review
Alternatives Considered
Amazon AWS
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.
Read full review
CircleCI
Circle was the first CI with simple setup, great documentation, and tight integration with GitHub. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when we switched.
Read full review
Return on Investment
Amazon AWS
  • CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
  • CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
  • CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.
Read full review
CircleCI
  • It has eased the burden of standardizing our testing and deployment, making onboarding new developers much faster, and having to fix deployment mistakes much less often.
  • It allows us to focus our process around the GitHub workflow, ignoring the details of whatever environment the thing we're working on is actually hosted in. This saves us time.
Read full review
ScreenShots