IAM Roles

By Ashwin Venugopal -

 







Roles Terms & Concepts

Role

It's an IAM identity created in your account with some specific permissions, and although IAM roles are similar to an IAM user in some aspects, they are always intended to be assumable by anyone who needs it instead of being uniquely associated with one person. Roles can be used by following:
  1. An IAM user in the same AWS account as the role.
  2. An IAM user in a different AWS account than the role.
  3. A web service offered by AWS like Amazon Elastic Compute Cloud (EC2).
  4. An external user authenticated by an external identity provider (IdP) service that is compatible with SAML 2.0 or OpenID Connect, or a custom-built identity broker.

AWS Service Role

It's a role assumed by any service in order to perform actions in your account on your behalf, hence, you have to always define a role for the service to assume while setting-up some AWS service environments.

AWS Service Role for an EC2 Instance

This is a special type of role that an application running on an Amazon EC2 instance can easily assume to perform actions in your account. This role is always assigned to the EC2 instance when it's launched.

AWS Service Linked Roles

It's a unique type of service role linked directly with an AWS service and they are generally predefined by the service having all the required permissions needed by a service to call the other AWS services on your behalf.

Role Chaining

If you use a role to assume a second role via AWS CLI or AWS API, then it is called role chaining. However, it also limits your AWS CLI or AWS API role session to a maximum of one hour.

Delegation

If you would like to grant permissions to others to allow access to your resources, then, delegation can help you in setting up trust between the two accounts. The first one owns the resource (i.e. the trusting account) and second one contains the users in need of access to that resource (i.e. trusted account) and they can be any one of the following:
  1. The same account.
  2. Separate accounts that are both under your organization's control.
  3. Two accounts owned by different organizations.

Federation

It's related to the creation of a trust relationship between an external identity provider and AWS and whenever you use OIDC and SAML 2.0 to configure a trust relationship between these two, the user is assigned to an IAM role. The user also receives temporary credentials to access your AWS resources.

Federated User

You can also use the existing identities from AWS Directory Service, your enterprise user directory, or a web identity provider (instead of creating an IAM user), also known as federated users.

Trust Policy

It's a JSON policy document defining the principals that you trust to assume the role. A role trust policy is a required resource-based policy attached with a role in IAM.

Permissions Policy

This document is in JSON format, and defines the actions as well as resources the roles can use. It's written according to the rules of the IAM policy language.

Permissions Boundary

As the name suggests, it's an advanced feature limiting the maximum permissions that an identity-based policy can grant to a role. However, a permissions boundary is not applied to a service-linked role.

Principal

It can perform actions and access resources in AWS. It can be an AWS account root user, an IAM user, or a role. In order to access a resource, the permissions can be granted in one of the two ways:
  1. You can attach a permissions policy to a user (directly, or indirectly through a group) or to a role.
  2. The services supporting resource-based policies can help in identifying the principal via principal element of a policy attached to the resource.

Role for Cross-account Access

 It's a role that can grant access to a resource in one account to a trusted principal in a different account.




































Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more

Threat Hunting in Microsoft Sentinel (part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Introducing the Microsoft Sentinel Hunting Page Threat hunting is a series activities performed while investigating and as there are no guidelines to perform it, the available tools on the Microsoft Sentinel can be introduced to perform better in your investigations. Firstly, you have to choose the Hunting link in the Microsoft Sentinel navigation menu to get to the Hunting page which is divided into the following sections: The header bar- It is located at the top of the page as usual and contains Refresh as well as timespan drop down menu. The New Query button can help you with creating a new query and the Run all queries button can run all the hunting queries in the background while also updating the hunting query list section with the number of results found.  The summary bar- Here, you can view the total number of queries available to run, the total number of bookmarks, the number of results from running live
Read more