Overview of access management: Permissions and policies

By Ashwin Venugopal -

 







Policies & Accounts

If a single account is managed in AWS, then, the permissions can be easily defined via policies, whereas, it's very difficult to manage permissions for multiple accounts and might require IAM roles, resource-based policies, or Access Control Lists (ACLs) to manage the cross-account permissions. However, it's recommended to allow the use of AWS organizations service to manage the multiple accounts' permissions. 

Policies & Users

IAM users are actually the identities in the service and once created, they can't access anything until they are given permissions to do that via a created identity-based policy attached with the user or a group to which the user belongs. Hence, the actions or resources that are not permitted are denied by default.

Policies & Groups

Another way is to organize the IAM users into IAM groups and then attach a policy to it, which will allow the individual users to have their own credentials as well as all the permissions attached to that group. You can also attach multiple policies with different permissions to a group that can calculated according to the combination of policies. However, the initial rule of granting permissions for an action stays same.

Federated Users & Roles

As federated users doesn't have the benefits of permanent identities like an IAM user, an entity should be created to assign permissions to them which can be termed as role and capable of defining the permissions for that role. Hence, a federated user is linked with the role and will get the permissions that are defined to the role.

Identity-based & Resource-based Policies

As the name suggests, identity-based polices are the permission policies attached to an IAM identity, like, an IAM user, group, or role, and controls the actions, resources, and conditions in which the identity can perform  whereas, the resource-based policies are the permission policies attached to a resource, like, an Amazon S3 bucket or an IAM trust policy, and controls a specified principal's actions that can be performed on a particular resource under certain conditions. 

However, the IAM services supports only role trust policy which is a type of resource-based policy attached to an IAM role, hence, identity-based policy and trust policy both should be attached to an IAM role (it's both the identity & resource that supports resource-based policies). 













































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

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
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