We performed a comparison between AWS CodeBuild and Chef based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation."The integration is a good feature."
"The solution provides good integrations."
"The integration is a good feature."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration with other AWS services has streamlined our workflow."
"Chef recipes are easy to write and move across different servers and environments."
"The most valuable feature is the language that it uses: Ruby."
"We have had less production issues since using Chef to automate our provisioning."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"The scalability of the product is quite nice."
"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 deployment fails sometimes."
"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"There is no persistent storage or preservation of workspace between the builds."
"They can further improve the integration of the Bitbucket for CodeBuild."
"Support and pricing for Chef could be improved."
"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."
"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."
"Since we are heading to IoT, this product should consider anything related to this."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
AWS CodeBuild is ranked 9th in Build Automation with 4 reviews while Chef is ranked 13th in Build Automation with 18 reviews. AWS CodeBuild is rated 8.8, while Chef is rated 8.0. The top reviewer of AWS CodeBuild writes "Provides good integrations, is flexible, and has a comparable price". On the other hand, the top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". AWS CodeBuild is most compared with Jenkins, GitLab, CircleCI, GitHub Actions and Tekton, whereas Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix.
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.