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."The product is a one-stop solution that you can use to integrate, deploy and host your application."
"The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier."
"AWS CodePipeline has valuable integration features."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"Code deployment is the best feature."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Chef recipes are easy to write and move across different servers and environments."
"The product is useful for automating processes."
"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."
"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 you're talking about multi-cloud, you can't use it."
"The tool does not provide automated features for evidence collection."
"In the next release, I would like to see fewer timeout errors."
"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."
"The setup time is a bit long."
"AWS CodePipeline doesn't offer much room for customization."
"The product’s pricing needs improvement."
"It is an old technology."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"I would like to see more security features for Chef and more automation."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"The agent on the server sometimes acts finicky."
"Since we are heading to IoT, this product should consider anything related to this."
AWS CodePipeline is ranked 3rd in Build Automation with 13 reviews while Chef is ranked 15th 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 SaltStack. 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.
