AWS Config vs BMC Track-It!

• It can help you define rules for provisioning and configuring of your AWS. We use it for this purpose.
• It maintains configuration history. So you can use the AWS Management Console, API, or CLI to obtain details of past configurations
• It gives you a configuration snapshot of all of your AWS resources and you can store it in AWS S3.
• You can integrate it with AWS CloudTrail to correlate configuration changes to particular events in your account.

Read full review

• The software is simple to use. There doesn't seem to be a lot of bells and whistles which could be attractive to some users.
• It includes email notifications where users are able to respond to an email and it updates the ticket.
• The system gives you the ability to customize your view so that you only need to see that tickets that are relevant to you or your group.

Read full review

• 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).

Read full review

• Care must be taken when configuring automatic replies otherwise you can end up in an endless loop of emails if response goes to another auto-responder. This will cause tickets to automatically be generated with every reply and then it takes a while to clean up the unwanted tickets.
• The support model is prohibitively expensive if you let support lapse and then need support once again. This is because they expect you to pay for all of the previous versions/years between when you last paid for support and their current version. This means that if there have been 3 versions of the software since you last had support, they expect you to pay for the 3 versions even if you did not use them. This is a primary reason why we are looking at alternative ticketing systems currently.
• It would be nice to have the ability to selectively kick a user our of a ticket without having to kick them entirely out of the application.

Read full review

• Security awareness. With multiple teams deploying provides easy visibility on any security risks. Security breaches would have a substantial impact on business so a vital investment with little costs.

Read full review

• We were able to consolidate down to one ticketing system and build it to fit our needs without any extra add ons.
• Adoption did have some trouble with people trying to manipulate the data entry system to match the reports they wanted. This resulted in some wasted time as the system was reset and those individuals were removed from the implementation team.
• This was able to eliminate many spreadsheets for tracking project work. This eliminated 'lost' projects and work and kept progress going forward.
• The built in reporting replaced hours of work creating reports out of spreadsheets and emails.
• We moved our help documents to their Solutions knowledge base and were able to eliminate a separate wiki server for holding that information.

Read full review