Amazon Cognito vs. Avigilon Access Control Manager (ACM)

Well Suited

1. B2C mobile and web apps with a high number of users.
2. Cheaper and cost-effective.
3. If the other pieces of the infra are already using AWS services like Lambda, S3, Pinpoint, etc.

Not Suited For:

1. Advanced use-cases (Biometrics based authentication) Email, and other MFA channels.
2. For any use-cases needing SCIM.
3. Customized flows of SSO, and MFA will need a layer on Lambda and other AWS services.

Incentivized

There are simpler systems out there for card access. The simpler systems are not as granular. There a lot of card access pieces to ACM. ACM also requires a server so if you want a cloud based solution, this is not an option. It's best if you have staff or a local company to support the hardware and software.

Incentivized

• Strong integration with React.js and client-side applications
• Easy to bridge Cognito identities with the rest of the AWS ecosystem
• Easy to store user profile data directly in Cognito rather than having to build additional services/endpoints
• Easy integration with AWS Lambda to extend and add sophistication to the service

Incentivized

• Integrate with burg systems
• Granular for time access
• Flexible with many types of badges

Incentivized

• Amazon Cognito has a bit of a learning curve. You need to learn its concepts and terminology. The documentation does not describe some topics comprehensively.
• Some Console screens would benefit from improved search and filtering options.
• When another AWS product (e.g., SageMaker) configures Cognito on your behalf, it is not clear what you're getting. For example, the expiration of a temporary password was configured but never communicated.

Incentivized

• How you set up integration with burg systems
• SSO
• Making door double taps easier to set up

Incentivized

Amazon Cognito is easy to use and implement if you don't need to implement custom policies. But if your security team requires something outside the box, then implementation becomes complicated and you risk wasting time. There is no option for customizable regex for passwords, which is a major deficiency. The standard password policy, allow to choose the length of the password, if it should contains at least one number, one special character, one uppercase letter and one lowercase letter.

Community support is excellent, many times even better and quicker then the offical AWS support. I really cannot recommend community support enough! Apart from that the service is relativily easy to use and does not have a huge learning curve. Examples are easy to follow and will help you start using the service.

Incentivized

They are ideal tools to create a secure and unique login experience for our applications. Thanks to its API authorization, Amazon Cognito ensures connections to applications that are secure.It is easy to use and provides easy access to files and applications that you need to complete your goal.

Incentivized

Some systems out there are not too granular. They also lacked integration with Google, which we need. With that being said ACM can sometimes make setup too complicated. Double-tap cards for instance take many steps to set up. In other systems it's a one-click setup. ACM is also compatible with Mercury boards. This is a big reason to choose ACM because the boards are not proprietary.

Incentivized

• ROI is great for Amazon Cognito Overall.
• It is included in the AWS Free Tier so you can use it for a good amount without paying, so the software can be tested beforehand.
• The paid pricing is also affordable, so a positive impact on ROI.

Incentivized

• card access can help to limit physical keys
• Less staff to unlock doors for events, because now they are scheduled by one person
• Licensing and installation costs are pricey

Incentivized