AWS Config vs. AWS OpsWorks vs. VMware Cloud Foundation

It's really good if your infrastructure services is all in AWS, that means everything could be audited and monitored using AWS config. You also can create alarms to notify you or your team about any changes on your AWS resources which is very useful to prevent abuse if you have a fairly large team. It's also very useful whenever some third party wants to audit your AWS resources, if you have a fairly comprehensive AWS config configured, the auditing process will be easy since they only need to look at your AWS config setup.

Incentivized

Where you already have some Chef recipes to build your application boxes and are happy to run directly on VMs, OpsWorks really shines. It won't do anything too complex for you, so it only really works well for simple stacks (load balancers, application layers, database layers). If you want to do more complex infrastructure, Cloudformation or Terraform are probably worth looking at.

Incentivized

It is best suited for an on-premise cloud solution where customer can shift their entire production environment. Also, the customer has a preference for a Homogenous Infrastructure Environment where budget is not a challenge. It is not at all suited for a Heterogenous Environment, e.g., a Public cloud where integration becomes a huge issue, also in SMB sections where budget is challenging.

Incentivized

• The ability to track changes in AWS is paramount, AWS config allows you to do this
• Allows the auditing of an AWS account
• Can view history of an account that has AWS config enabled

Incentivized

• connect between serveral AWS services (EC2, RDS, ELB)
• easy configuration management deployment via Chef

Incentivized

• Cloud enabled Solution.
• Support Container based Apps.
• Cost efficient.
• Supports both Public and Private Environments.

Incentivized

• It's only AWS, no third party.
• Not the most intuitive interface, but with a little getting used to it is OK.

Incentivized

• 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.

Incentivized

• The Deployment is complex.
• Recommended Number of Physical Nodes is three or more; with less than 3 Nodes, it becomes difficult to install V-SAN.
• Need for better integration. If we go on the public cloud, it is a huge challenge while integrate with an open source platform.
• Cost can be marginally reduced. SMB segments still prefer a separate license instead of VCF, or they postpone their purchase plans.

Incentivized

Would rate lower for other workloads but for AWS workloads its simple to set up, cost effective and customisable. Primary use case is compliance from a governance perspective.

Incentivized

Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.

Incentivized

I do not know or have used any other product in AWS cloud space that matches what AWS Config provides. We have some custom built monitoring and governance, however that is there because AWS Config does not provide it currently.

Incentivized

OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.

Incentivized

Although the public Cloud Model follows Opex Costing Model, it actually leads to very high costs also, the infra model in my organization is not suited for a Public Cloud Model. Hence We decided on an On-Premise Model, and the best suited was VMware Cloud Foundation, which is a complete Software-Defined Scale-Out Architecture. I also prefer a Homogenous environment; i.e, support and services from a Single OEM, so that I Can get faster resolutions to my tickets raised.

Incentivized

• Enforcing audit requirements
• Easy to set up alerting when there are rule breaches
• Auto remediation reduces the manual policing of such breaches

Incentivized

• very quick way of creating new infrastructure
• low maintenance costs
• easy to create high availability setups thus reducing costs

Incentivized

• My organization has a size of 1300+ employees, using multiple applications and an exchange mail server that is hosted on On-Premise Cloud, hence scalability has not been a challenge.
• Having hosted my Production environment and Mail exchange Server on VCF, there has been optimum resource utilization with very little scope downtime. Hence have been able to save a lot of funds on Hardware resources.
• Due to the size of my organization and due the data load, I have been able to save on Resource Utilization and Organization Funds

Incentivized