We performed a comparison between AWS CodePipeline and Chef based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."AWS CodePipeline has valuable integration features."
"Code deployment is the best feature."
"The product is a one-stop solution that you can use to integrate, deploy and host your application."
"The product is cost-effective and integrates well with the AWS environment."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"The integrations are good."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most valuable feature is the language that it uses: Ruby."
"Deployment has become quick and orchestration is now easy."
"AWS CodePipeline doesn't offer much room for customization."
"AWS CodePipeline functions well, but there's room for improvement in providing technical support to regular customers who haven't purchased developer support. I mean, having it available for everyone, even if it's not a 24-hour service. It would be more useful if specific support hours were available for assistance."
"In the next release, I would like to see fewer timeout errors."
"If there are many dependancies involved in the setup, it may take a long time."
"The migration process from one source code to another needs improvement."
"The support team’s response time must be improved."
"If you're talking about multi-cloud, you can't use it."
"The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"The agent on the server sometimes acts finicky."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"The solution could improve in managing role-based access. This would be helpful."
"I would like to see more security features for Chef and more automation."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
AWS CodePipeline is ranked 4th in Build Automation with 13 reviews while Chef is ranked 13th in Build Automation with 18 reviews. AWS CodePipeline is rated 8.4, while Chef is rated 8.0. The top reviewer of AWS CodePipeline writes "A fully managed service with excellent integrations and a flexible architecture". On the other hand, the top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". AWS CodePipeline is most compared with GitLab, AWS CodeStar, Jenkins, GitHub Actions and Tekton, whereas Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix. See our AWS CodePipeline vs. Chef report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
