IAM User Groups

By Ashwin Venugopal -

 










Characteristics

Some of the important characteristics of user groups are as follows:
  1. A user group may consist of many users and a user can also belong to the multiple user groups.
  2. User groups can't be nested; they can contain only users, not other user groups.
  3. No default user group containing all the users in the AWS account is automatically available, instead, you have to create it and link each user to it.
  4. The number and size of IAM resources in an AWS account is limited.

Creating IAM User Groups

In order to do that, firstly, you have to create the group, then give it the permissions accordingly, and add users to the group, thus, completing the process.

To create an IAM User group & attach policies (console)

  1. Similar to the processes discussed before, you have to sign-in to the AWS Management Console and then open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, you can choose the User groups and then Create group in the navigation pane.
  3. Type the name of the group for the User group name.
  4. Choose the number of users you want to add to the group from the list of users.
  5. Now, from the list of policies, choose the policy you would like to apply to all the members of the group.
  6. Finally, you can Create group.

To create IAM user groups (AWS CLI or AWS API)

  1. AWS CLI: aws iam create-group.
  2. AWS API: CreateGroup.























































































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

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more