AWS Config vs. Oracle Enterprise Manager Cloud Control

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

I wish I had an option to give it a 9.5 :) OEM Cloud Control is very well suited if you have a system with multiple implementations of Oracle Database Enterprise Edition. If you are willing to pay for the huge license cost which is typical with Oracle, then you will love to use OEM Cloud Control to monitor your entire ERP solution including web servers, applications, network, storage, and physical servers. It is not worth the buck if your's is a small implementation. Your DBA's should be able to work without depending on OEM Cloud Control.

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

• Oracle Enterprise Manager is a "one stop shop" for all of our management needs. This is helpful because it minimizes the management of the management software itself. There are less upgrades and connectivity issues to handle. And there are "plug-ins" for additional products we use like Blue Medora's one for PostgreSQL.
• Managing administrative jobs can be burdensome in a shop with dozens of servers and databases. OEM Cloud Control makes it easy since you can view all the jobs for all servers in one place. It is easy to filter on jobs with problems or the like so that you can quickly look at the logs and fix the issues.
• Tuning PL/SQL is much easier using OEM Cloud Control. Most DBAs are familiar with trace files and TKPROF, but not having to do those things at a command line smooths the process out. The graphical interface makes it easier to show developers exactly what the issues are. This makes for less finger-pointing and quicker resolution of performance problems.
• Proactive management is easier using OEM Cloud Control. Before having the gui, I had a collection of scripts that I would have to install on each database server, then set up cron jobs to run them. When Oracle was upgraded, those scripts might have to be updated on each and every server. OEM Cloud Control has those things built in. You can choose exactly which metrics are important to you. And you can keep performance graphs up all day on a second monitor to let you instantly see when something might cause a problem.

Incentivized

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

Incentivized

• Oracle Enterprise Manager Cloud Control can do a better job in actively managing (as opposed to monitoring) non-Oracle IT components including non-Oracle database, middleware, and storage.
• The UI is less responsive and sometimes slow and the user experience could certainly be improved.
• There is also an issue with positioning as other Oracle products sometimes come with their own versions of management console so it is hard to justify paying for Oracle Enterprise Manager Cloud Control separately or as a new attachment.

Incentivized

I wanted to give it a 10 but the heavily loaded solution makes it slow to load and refresh pages. Even bouncing the OEM Cloud Control takes around 10 mins which is quite long.

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

Since OEM Cloud Control comes free with Enterprise Edition, we have mostly worked on OEM Cloud Control. I did have my fair share of experience with DBArtisan. It's good and lighter than OEM Cloud Control. It sort of removes your need to even go to SQLPLUS command line most of the time. But it is way behind OEM Cloud Control in terms of features.

Incentivized

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

Incentivized

• Freed up DBAs and SAs by automating much of their antiquated manual processes.
• We are limited by our own desire to use and learn all of the features within OEM.

Incentivized