Amazon Web Services offers AWS Config, a service that provides monitoring and assessment of AWS resource configurations to support compliance auditing, change management and troubleshooting, with resource histories and comparison of historical configurations against planned configurations.
N/A
Cognizant Cloud360
Score 5.0 out of 10
N/A
Cognizant offers Cloud360, a comprehensive cloud management platform.
N/A
Pricing
AWS Config
Cognizant Cloud360
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AWS Config
Cognizant Cloud360
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With AWS Config, you are charged based on the number of configuration items recorded, the number of active AWS Config rule evaluations and the number of conformance pack evaluations in your account. A configuration item is a record of the configuration state of a resource in your AWS account. An AWS Config rule evaluation is a compliance state evaluation of a resource by an AWS Config rule in your AWS account, and a conformance pack evaluation is the evaluation of a resource by an AWS Config rule within the conformance pack.
—
More Pricing Information
Community Pulse
AWS Config
Cognizant Cloud360
Features
AWS Config
Cognizant Cloud360
Cloud Management
Comparison of Cloud Management features of Product A and Product B
To keep track of changes and to answer many compliance issues this is a life-saver. AWS does a good job providing tools like this. Any AWS workload should be monitored with AWS Config. It even is great for troubleshooting and seeing who changed what at what time.
Cognizant Cloud 360 is very well suited for cloud integration of modern, common software among users of a wide spectrum of proficiency levels. The user interface is well designed and intuitive, and all common software tools have existing implementation tools and intuitive platforms for cloud migration. Cognizant Cloud 360 is not as useful when most users are highly technically competent and use specialized, less common software tools that are to be migrated to the cloud platform. Cognizant is technically sound, but maybe not as much as some established competitors (Microsoft, IBM, Oracle, etc) and also may not have familiarity with lesser-known software applications.
Very good customer service team. Very responsive to inquiries, and willing to collaboratively develop solutions to software Platform integration challenges.
Very intuitive user interface. Layout for various tools and settings is well-conceived and implemented, and the software is ultimately very easy to navigate for even novice users.
Customizable resource library. The platform makes it easy to select tools that are needed without forcing you to subscribe to additional tools that are not needed.
Vendor lock-in, no easy migration path for example if you want to move some workloads to Azure, you'd not be able to lift and shift.
Only at an AWS resource perspective - cannot do desired state configuration at an OS level (which makes sense but be good if you could even as a separate feature within AWS Config).
Could improve in agility in the delivery life cycle. When customer demands change and abrupt changes in resources and configuration are required, the change order process is not as quick as desired.
Advanced technical competence and knowledge of a wide variety of specialized software applications is a bit lacking. Relative to some competitor software from Oracle, Microsoft, IBM, or HP, Cognizant isn’t as technically inclined and ready to handle issues with less common software tools.
Not as forthcoming with status updates as some competitors. In cases of interruptions or upcoming updates, Cognizant doesn’t disclose timely and detailed information unless it is specifically requested by the user.
The performance has never been an issue for us, the dashboard gives us real-time monitoring and the alert sends us the notification within less than a minute of it happening, this applies to all of the monitored resources on AWS. However we can't (or probably haven't figured out how to) integrate with any other third party services, so we can't really evaluate how it integrates with other services
Support is very timely and thorough in their responses to inquiries, and also is very willing to help in finding collaborative solutions to any technical challenges. Overall, the only negative is they may not be as equipped or ready to proactively handle some more customized requests as a more established competitor would be. This is more of a reflection of the software than the support team.
Despite the comparison it is not really apples to apples, the main purpose of the service is quite similar which is to monitor your application or services. In terms of AWS services, AWS Config provides more options to monitor and log your service on the infrastructure level which is very useful on that level and overall will give you more information about what is currently happening. Meanwhile PaperTrail is more suited to monitor and log your service and could only give you information on the application level.
Cognizant Cloud 360 has more of a modern look to it and most of the same functionality. I prefer the layout of Cognizant as I find it more intuitive for a variety of users, but Microsoft’s is also pretty well laid out. Microsoft is more established and has more experience in integrating a wide variety of applications, and so is more ready and equipped to handle less common application cloud integration.
Cognizant Cloud 360 has saved on overall hardware costs, as many resources have been migrated to the cloud platform and local storage and hardware systems are no longer needed.
There was an initial period of negative return as the migration was occurring, as some applications were interrupted, which in turn interrupted the flow of projects and inhibited the timely allocation of resources.
Another positive return can be measured in time savings, as users can more easily access applications from the central cloud source versus various locally customized network locations.
