AWS OpsWorks vs TeamCity

• The interface is quite intuitive and allows you to discover and easily find what you want to do and what other features are within OpsWorks.
• Chef integration is pretty seamless and there are a good set of options and operating systems to choose from
• It makes things like auto scaling set up, either via load or time, more straight forward and intuitive than what you'd typically see via the EC2 console

Read full review

• Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
• Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
• Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.

Read full review

• Getting up and running with OpsWorks is a very technical and potentially time-consuming process. You need to know the ins and outs of Chef/Puppet if you really want to get into it and there isn't a convenient way to test out the environment locally so debugging can be time-consuming.
• To take advantage of some of the newer AWS instance types you need to be running on a VPC, which again is a pain if you don't have a DevOps team.
• The error logs and monitoring metrics in OpsWorks are pretty basic and haven't changed much over the years.

Read full review

• Reading build output logs can be a pain at times, as they aren't really parsed; just long lines of output.
• When you have multiple projects and branches, determining what is currently building, what is pending, and what has failed can be difficult.

Read full review

• OpsWorks has allowed some of our more simple application stacks to be implemented quickly and effectively. Whilst it is difficult to put actual numbers on it, it meant we could hit the ground running before tackling the more complex world of Cloudformation/Terraform to manage parts of our infrastructure.

Read full review

• It has drastically improved the turnaround time for building and deploying projects to Production
• The build process can be augmented by adding build servers quickly
• In my opinion the licensing cost is not expensive at least for small to medium enterprises, although I haven't looked in detail into how it changes when you move up.

Read full review