AWS Config vs. (EOL) Cisco CloudCenter

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

It is well suited for large corporate entities, whether they are in manufacturing, sales, engineering, healthcare, supply or shipping. It is easy to understand and operate once it has been initially configured. Expansion of the system is likewise easy to do once expertise has been acquired. The only difficulty with this or any cloud scenario is ensuring where the data is located and managing that securely.

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

• We are able to automate deployment which has been a strength to the geographical distribution of the enterprise.
• We have been able to work with a wider variety of developer tools and haven't had to customize to fit CloudCenter.
• It is easier for us to allocate space and allow users to take advantage of the system directly with a minimum of overhead.

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 software and systems don't present a problem to us but the continued interaction with mid-level support teams and vendors can slow down implementation or correction of difficulties we experience.
• The continued overhead associated with peripheral training on systems we have purchased can cause delays.
• Language barriers sometimes show up but this, again, is due to remote middle agents that are themselves contractors of or sales agents of the main agency. It slows down communication and can introduce business difficulties.

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

We found that the cost advantages were greater by going with Cisco because of our present contracts and the materials and equipment we already had on hand. The reliability of the system, for us, outweighed any cost advantages we might have been realized by going with another provider. Certainly the service and support for the entire system is much better when handled by a single vendor with a good track record.

Incentivized

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

Incentivized

• We have had a positive return on investment by adopting Cisco CloudCenter as the system is more mature than competitors. We have saved a lot by working with them rather than continuing to act as a defacto test location for other systems.
• We have been able to reduce the number of staff necessary to operate the system and turn them over to more profitable work.
• One negative impact we have seen is that it is difficult to map where the data is located at any specific instance.

Incentivized