I am going to choose two things because I can't choose between them. First is the ease of integration with other identity systems. It's fairly easy to get something like your HR system (Rippling in my case). The other is the truly granular access control which lets you give very specific access to custom roles for various automated systems to do what they need to and nothing more. If you keep on top of that as you go and don't grant `*` permissions, it makes going through compliance checks on the platform much easier because there's no need to worry about small components of your system going rogue, because they just can't.

Implementation can be challenging. AWS has better tools than they used to for checking permissions but if your code performs different actions on different paths then you really need to be thorough in your testing to make sure you have the permissions you need. For example, if you only report errors via alarms then you need to make sure you're injecting faults in your tests. Otherwise you will have some very fiddly problems to solve where things fail unexpectedly. I would say this is most of the cost of implementation, just getting the permissions right as you build.

Overall it was really very much good, you are not see any bug or production issue.

IAM is one of the most advanced technology to give access to the users and some of the providers and vendors will only provide the access for users as per the applications but AWS managed in this way that if a service needs a resource we need to provide access for read as well as write both so it was too good when comes security

There is no AI BOT or assistent who hear the requirements and create role for the customers, clients or customers needs to create role test the application then only they will satisfied so it was just a good thing if they create a bot .

In AWS there is always a way to get something done. When dealing with user, service principals and co. you will find a way.

In comparison to its competitors, AWS does not make things easily discoverable in the UI. You can do it through the CLI tools and consoles, but the learning curve can be very steep.

Very happy with AWS IAM. Without it, it would be very difficult to manage our AWS ecosystem in an efficient and secure way.

Able to create one user or service account in AWS that has access to all of the resources it needs to do its work. Whether, it's an individual, web application, reporting tool, or countless other uses, you are able to assign access to only what that user needs with access keys and quickly remove that access when it is no longer needed.

Requires the build out of Groups and Policies when not using the built in options. This can slow down user creation.

En términos generales, IAM me ha brindado una excelente experiencia en la administración de accesos y permisos en AWS, ofreciendo una funcionalidad robusta y flexibilidad a la hora de cumplir con los requerimientos de los clientes finales.

IAM es un servicio robusto que permite brindar protección a los diferentes recursos que se encuentren desplegados en AWS, evitando el accesso y uso no autorizado de los mismos. Otro beneficio es la gran flexibilidad que brinda para adaptarse a los requerimientos de seguridad de diferentes clientes.

Considero que se necesita mejorar la interfaz para ser más intuitiva para los usuarios, además de que sería importante mejorar la funcionalidad de creación de políticas de IAM a través de un asistente virtual