Managing IAM User Groups (Part 1)

By Ashwin Venugopal -

 




To read part 2, please click here




Listing IAM User Groups

You can easily list all the user groups in your account, however, if you use AWS API or AWS CLI, then, the user groups will be listed with a particular path prefix.

To list all the user groups in your account

Do any of the following:
  1. AWS Management Console- Choose User groups in the navigation pane.
  2. AWS CLI- aws iam list-groups.
  3. AWS API- ListGroups.

To list the users in a specific user group

Do any of the following:

  1. AWS Management Console- Choose User groups, the group's name, and then Users tab, in the navigation pane.
  2. AWS CLI- aws iam get-group.
  3. AWS API- GetGroup.

To list all the user groups that a user is in

Do any of the following:

  1. AWS Management Console- Choose Users, the username, and then the Groups tab, in the navigation pane.
  2. AWS CLI- aws iam list-groups-for-user.
  3. AWS API- ListGroupsForUser.

Adding & Removing Users in an IAM User Group

User groups can be utilized to apply same permissions policies across multiple users at once; after that, users can be smoothly added or removed from an IAM user group, which can be helpful whenever people leave and enter your organization.

Add or Remove a User in a User Group (Console)

The AWS Management Console can be used to add or remove a user from a user group.

To add a user to an IAM user group (console)

  1. Firstly, sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, select the User groups and the group's name in the navigation pane.
  3. Choose the Users tab and then Add users. Choose the check box next to the users you would like to add.
  4. After that you can Add users.

To remove a user from an IAM group (console)

  1. You have to sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, you can select the User groups and the group's name in the navigation pane.
  3. Choose the Users tab and then Choose the check box next to the users you want to remove
  4. After that you can Remove users.

Add or Remove a User in a User Group (AWS CLI)

The AWS CLI can be used to add or remove a user from a user group.

To add a user to an IAM user group (AWS CLI)

In order to do that, use aws iam add-user-to-group command.

To remove a user from an IAM user group (AWS CLI)

In order to do that, use aws iam remove-user-from-group command.

Add or Remove a User in a User Group (AWS API)

The AWS API can be used to add or remove a user from a user group.

To add a user to an IAM group (AWS API)

In order to do that, perform AddUserToGroup operation.

To remove a user from an IAM user group (AWS API)

In order to do that, perform RemoveUserFromGroup operation.






To read part 2, please click here

















Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can...
Read more