As a DevOps engineer, I primarily use AWS services like EC2 instances, S3, Auto Scaling Group, CLB, Route 53, and database services. I also use KMS Key for encryption, and these are the services I use daily.
I used AWS Identity and Access Management for creating, modifying, and deleting users and integrating with one or more other directories. It is used to synchronize with other directories and create new identities for users who need specialized access to organizational tools. Additionally, while creating users, we provide specific permissions.
I use AWS Identity and Access Management mostly as a team leader managing twenty to twenty-five client accounts, primarily on AWS. I handle their accounts and ensure proper access by creating IAM users and roles, assigning specific privileges, particularly when juniors need to work only on certain services like EC2.
I used AWS Identity and Access Management to create a user authenticator and manage subdomains with access to the operating system. I assigned group policies and rules regarding their usage. Additionally, I used IAM for managing group policies and individual policies as part of my cybersecurity domain studies.
Group Manufacturing Head at Cerulean Information Technology
Real User
Top 10
2024-10-11T15:32:00Z
Oct 11, 2024
I am a cloud engineer and DevOps engineer. I mainly use AWS Identity and Access Management (IAM) for setting some policies for developers, such as granting limited access to specific resources as part of managing permissions. Additionally, roles, policy management, and monitoring and logging are essential, and integration with services like EC2, Lambda, S3, and others.
Learn what your peers think about AWS Identity and Access Management. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
AWS Identity and Access Management allows organizations to manage user permissions, secure access controls, and simplify authentication. It supports multi-factor authentication, integrates with AWS services, and provides robust role-based access management.
AWS Identity and Access Management is instrumental for organizations in defining detailed policies, monitoring activity, and maintaining compliance. With its strong security controls, granular permission settings, and seamless...
As a DevOps engineer, I primarily use AWS services like EC2 instances, S3, Auto Scaling Group, CLB, Route 53, and database services. I also use KMS Key for encryption, and these are the services I use daily.
I used AWS Identity and Access Management for creating, modifying, and deleting users and integrating with one or more other directories. It is used to synchronize with other directories and create new identities for users who need specialized access to organizational tools. Additionally, while creating users, we provide specific permissions.
I use AWS Identity and Access Management mostly as a team leader managing twenty to twenty-five client accounts, primarily on AWS. I handle their accounts and ensure proper access by creating IAM users and roles, assigning specific privileges, particularly when juniors need to work only on certain services like EC2.
I used AWS Identity and Access Management to create a user authenticator and manage subdomains with access to the operating system. I assigned group policies and rules regarding their usage. Additionally, I used IAM for managing group policies and individual policies as part of my cybersecurity domain studies.
I am a cloud engineer and DevOps engineer. I mainly use AWS Identity and Access Management (IAM) for setting some policies for developers, such as granting limited access to specific resources as part of managing permissions. Additionally, roles, policy management, and monitoring and logging are essential, and integration with services like EC2, Lambda, S3, and others.