AWS Config vs. SUSE Manager

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

In our specific use case, SUSE Manager is extremely useful. We're having a large landscape that is divided into intake, development, quality and production with a couple of different SUSE flavours that need to be automatically rolled out, configured, patched and maintained, everything from up to date repositories that are cloned on a daily basis straight from SUSE.

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

• Manages patch levels for most Linux OS by: date, group, cloud or custom channels
• Uses a lite version of Salt to run commands or scripts on any numbers of servers at once.
• Allows the joining of groups inside SUSE Manager to quickly access or work with servers so grouped.

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

Incentivized

• The cloning of patches when using the content lifecycle module in a multi-environment landscape with many SLES flavours is a bit cumbersome.
• More premade saltstate for default applications are always nice to have.
• Upgrading SUMA could be easier, especially when a Postgres upgrade is also required.

Incentivized

I am expanding the use of SUSE Manager throughout our organization and can't imagine going back to the "wild wild west" we had before.

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

SUSE Manager provided a top-tier support person on site to us for two days to help integration. We did all the standard stuff they help with before he arrived. We were able to use him to get all the tricky stuff identified and solved in the short time we had. Had they sent us a lower-tier guy, it would have been a waste. I was impressed they sent such knowledgeable person.

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

The other competitors also have a good platform and service, but we went with SUSE due to cost. The price was best and we needed to keep under a certain budget. The functionality was perfect for what we needed so we took the step forward. This allows us to manage our Linux environment within the manager and update or deploy specific tasks to each as needed.

Incentivized

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

Incentivized

• Manages patch levels for most Linux OS by: date, group, cloud or custom channels
• Make it easy to audit our own infrastructure.
• Allows the joining of groups inside SUSE Manager to quickly access or work with servers so grouped.
• 24/7 support team.
• Automatic deployment.

Incentivized