Sign in
Categories
Migration Mapping Assistant Your Saved List Partners Sell in AWS Marketplace Amazon Web Services Home Help

Chef Automate (First 10 nodes free)

Chef Automate gives you everything you need to build, deploy and manage your applications and infrastructure at speed. Use the Chef Automate platform to package and test your applications, provision and update your infrastructure, and manage it all with compliance and security checks and dashboards... See more

Customer Reviews

3
  • 5 star
    0
  • 4 star
    0
  • 3
  • 2 star
    0
  • 1 star
    0
Create Your Own Review

3-star reviews ( Show all reviews )

Great for configuration management and integration, especially in AWS

  • By AwsConte413b
  • on 01/06/2019

We use it for training.
How has it helped my organization?
All the Chef enthusiasts who come to us to learn and train, improve their skillsets to get jobs. It's a really easy product in AWS. It's easy to teach and easy to understand.
What is most valuable?
The most valuable feature is the language that it uses: Ruby.
Regarding integration and configuration of the product, they're pretty manageable. The layers are really easy to configure.
What needs improvement?
I would like to see more security features for Chef and more automation.
What do I think about the stability of the solution?
It's working great. It's stable. We try to produce real-world scenarios with the students as much as possible.
How was the initial setup?
It's a really easy product in AWS. It's easy to teach and easy to understand.
Which other solutions did I evaluate?
We considered Puppet and Ansible. We went with Chef because Chef uses Ruby and Ruby is pretty popular right now.
What other advice do I have?
Compare it to the other services that you use.


Its recipes are easy to write and move across different servers and environments. However, they need to provide better functionalities when creating recipes.

  • By Sharath A.
  • on 12/05/2018

Our primary use case is having the properties set up across the servers. We have Chef recipes deployed and configured across our servers, so we get the same type of replication across our servers and environments.
We are using the on-premise version. We have our applications already set up for on-premise. We are using Chef and preparing it for CI/CD and other properties. Now, we are planning ahead and will use the AWS service too.
How has it helped my organization?
Earlier, we used to do everything manually, such as configuring the servers across different environments. Using Chef and Puppet, we can automate our CI/CD process with reduced effort from our DevOps team.
What is most valuable?
Chef recipes are easy to write and move across different servers and environments.
What needs improvement?
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.
We would also like more recipes. This is key for us.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
We do put a lot of stress on it from the QA, staging, and servers. We have a CI/CD pipeline continuously running as the developer commits the code to Chef and Puppet, which are always up and running.
What do I think about the scalability of the solution?
The scalability is working well for our organization.
How is customer service and technical support?
As a developer, I don't use the technical support.
What's my experience with pricing, setup cost, and licensing?
We are still in the process of evaluating Chef Compute. Currently, we use Chef and Puppet. Soon, we will probably be purchasing it from AWS Marketplace.
Which other solutions did I evaluate?
We were already using Chef and Puppet for most of our DevOps. These were our only choices.
What other advice do I have?
I would definitely recommend using Chef.
Chef integrates and configures well with AWS and other products. We use Chef and Puppet together. We are also using Splunk for log traces. We just started using Chef with AWS for easy to use containers. AWS is great for storage, CloudFormation, and CloudFrond CDN.


Bad Gateway - and how to fix

  • By Deano
  • on 03/04/2018

I had the same Bad Gateway errors as the other reviewers. I did a little digging and found a fix.

ssh on and then

sudo chef-server-ctl upgrade


showing 1 - 3