AWS Config vs. VMware Cloud Director

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

If you have a lot of customers that all need to have a separate place to work in, without the possibility of getting in each other way, and you want to safe yourself a lot of work. Than I strongly recommend you Cloud director. Ofcourse, only if you have a VMware environment as your working environment. If you just have a small group of customers and you can easily handle the work that's coming from it, then it is overkill to add cloud director to your environment. In a later station, you can always introduce cloud director (so tis never to late if you still want to use it)

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

• Building virtual racks
• Managing the customers' network and security
• Simplicity but the completeness of IaaS solution
• Integration with major software providers

Incentivized

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

Incentivized

• The add-on/extension required on the internet browser sometimes are difficult to get working at first. We've experience instances where the add-on/extension latest versions will not work and have to downgrade to an older version.
• The server console lacks features and tools. For example it would be useful to have a copy and paste tool or a file upload tool.
• The vCloud Director management site uses Adobe Flash, which makes it impossible to use on a mobile device.

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

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

vCloud Director is definitely my favorite as far as cloud managers. The only thing that compares is Cisco UCS Director, but it has slightly different functionality and purpose. I understand why a lot of clients still go with vCloud Director even though VMware intends to sunset it

Incentivized

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

Incentivized

• Saves a lot of time, and time is money
• Stable, so little to non downtime
• With P1 , good support

Incentivized