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

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

5-star reviews ( Show all reviews )

We have had less production issues since using it to automate our provisioning

  • By Timothy R.
  • on 12/26/2018

We use it for provisioning Adobe Experience Manager web application environments.
How has it helped my organization?
It has given us more resiliency in all the stuff we now manage with Chef, which was previously sort of manually maintained. Now, we are able to drive all of that through version control and automation, which is a lot faster.
What is most valuable?
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.
What needs improvement?
There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based. However, it is just a different product and requires you to acclimate yourself, just like any other product would.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
We have had no stability issues.
What do I think about the scalability of the solution?
The scalability works. We haven't scaled it too high. We have a few different servers in different places.
We have been looking into the high availability offering, but we haven't actually stood it up yet. We are hopeful about it though.
How is customer service and technical support?
We have had to open a few Amazon support tickets. However, they have typically not been Chef-related, they have been Amazon service-related.
The technical support has been great. Our tickets have all been closed out quickly.
Which solutions did we use previously?
Our environments used to be on-premise, then we were moving them into the cloud. Since they were big and complicated, we decided we needed a manageable provisioning system instead of doing it by hand every time.
What was our ROI?
We have seen ROI. It has decreased a lot of man-hours that we were previously spending doing stuff which we now manage with Chef. It has decreased when we have a production issue, since we are able to fix it faster. We also have had less production issues since using Chef to automate our provisioning.
What's my experience with pricing, setup cost, and licensing?
I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up.
Which other solutions did I evaluate?
We considered Chef, Puppet, Ansible, and homegrown solutions. We had a couple people who used to use Ansible and some people who had previously used Chef. I think we just settled on Chef after trying it because we liked that it was Ruby-based, and there were a lot of community cookbooks already. This lined up parallel with what we wanted to be doing.
What other advice do I have?
I would recommend Chef. It is very user-friendly. There are a lot of community resources which make it easy to onboard. It also plays nicely with existing automation tools and other things which you are probably already using.
Chef works with Adobe Experience Manager, Terraform, and AWS CLI tools. We have been pleased with the integration.


It integrates with many products in ILT and data management areas with each of them providing cloud computing

  • By Joel B.
  • on 12/10/2018

I have used in my current company for three years, and with other clients for more than ten years.
How has it helped my organization?
My clients are happy, which is the most important thing.
What is most valuable?
The most valuable feature is automation.
What needs improvement?
The AWS monitoring, AWS X-Ray, and some other features could be improved.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
We have some issues in Brazilian region with stability. However, in US region, we have no issues with stability.
What do I think about the scalability of the solution?
Scalability is pretty good. We have nothing to complain about, except the price.
How is customer service and technical support?
I would rate the technical support as a ten out of ten.
Amazon is a great partner.
How was the initial setup?
The integration and configuration are pretty good in the AWS environment. The problems are usually on our side, not on AWS' side.
What's my experience with pricing, setup cost, and licensing?
The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it.
Which other solutions did I evaluate?
I don't like some of the products offered by VMware. I like the automation offered by Chef and Puppet.
We chose Chef because some clients have some legacy systems and decided to work with them. We don't really like work with VMs, but when we have to, we use Puppet.
What other advice do I have?
I have used the on-premise and AWS versions. I prefer the AWS for troubleshooting.


Watch "sudo automate-ctl tail" until it calms down, THEN initialize.

  • By Mike
  • on 08/15/2018

I initially also had the same issue with the 500 error when attempting to download the starter kit. After playing with this a bit, I discovered the cause. The system was not fully initialized.

No upgrade is necessary for this AMI to succeed. Just wait until "sudo automate-ctl tail" calms down i.e. not scrolling so often, then perform the initialization step.

STEP 1: CREATE / LAUNCH AWS AUTOMATE INSTANCE:
STEP 2: LOGIN TO AWS CHEF AUTOMATE:
$ ssh -i ec2-user@
STEP 3: WATCH CHEF AUTOMATE LOGS UNTIL THEY CHILL OUT
$ sudo automate-ctl tail
STEP 4: CONFIGURE CHEF AUTOMATE (after automate-ctl tail calms down):
https:///biscotti/setup
STEP 5: LOGIN TO CHEF AUTOMATE
https://
STEP 6: PROCEED WITH LEARN CHEF RALLY CONTENT


Great for learning Chef Automate

  • By Chris
  • on 05/28/2018

Others have left poor ratings and reviews, but its really due to their lack of drive to learn Chef, much less debug. The first thing I did after launching this AMI, was upgrade chef-server and chef-automate on the instance. Simple Google searches will reveal an easy process to do this.

SSH into your instance (it's an Amazon Linux AMI, btw) to perform the upgrades as I mentioned. From there, activate your Automate instance as described in the "Usage Instructions" listed for your instance in the EC2 console.

Return to your Learn Chef Rally exercise to bootstrap any nodes that you'd like. In all, this was a very painless process to running on Chef Automate!


showing 1 - 4