IAM Identities (users, user groups, and roles) (part 1)

By Ashwin Venugopal -

 





To read part 2, please click here





AWS Account Root User

As stated before, whenever an AWS account is created, a single sign-in identity called the AWS account root user is provided that has complete access to all the AWS services as well as the resources in the account. It can also be accessed by signing in via the same email address and password that were used in the beginning to create the account.

Note: It is strongly recommended to not use the root user for your everyday tasks, instead, the root user credentials must be locked away securely and should only be used to perform a few account and service management tasks.

IAM Users

It's an entity that can be created in AWS which also represents the person or service who uses the IAM user to interact with AWS. A user in AWS mainly consists of a name, a password to sign into the AWS management console, and up to two access keys that can be used with the API or CLI. Its primary purpose is to enable the people to successfully sign in to the AWS Management Console for any type of interactive tasks or make programmatic requests to AWS services via API or CLI. 

IAM User Groups

As the name suggests, an IAM user group is a collection of IAM users that can be used to specify permissions in order to make them easier to use or manage for those users. Through a user group, policies can attached to multiple users at a time and it cannot be identified as Principal in a resource-based policy. After an identity-based policy is attached to a user group, all the users in that group receives same permissions from them.

IAM Roles

Similar to a user, IAM roles is an identity with permission policies that also defines what the identity is supposed to do in AWS. As the roles doesn't have any specified credentials, any IAM user can assume them accordingly (in order to temporarily take on different permissions) for a specific task. They can also be assigned to a federated user after AWS determines which role is mapped to the user.

Temporary Credentials in IAM

Although they are primarily used with IAM roles, they also be requested to have more restricted set of permissions to save you from accidently performing the non-permitted tasks by the more restricted credentials. They are more beneficial as they can be expired automatically after a particular period of time set by you.





To read part 2, please click here



































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