Getting set up with IAM

By Ashwin Venugopal -

 







Overview

AWS IAM offers secured control and access to your AWS and account resources while simultaneously keeping your account credentials private. As a well known fact IAM offers you a variety of advantages while without it, you either have to create an AWS account or the security credentials of an AWS account should be shared by your employees; moreover, you also can't control the tasks a particular user can do via particular AWS resources.

Using IAM to Give Users Access to Your AWS Resources

The following measures can be taken to control access to your AWS resources:

Type of Access

Why would I use it?

Access for users in your AWS account.

If you want to add/create users via IAM and manage their permissions.

Non-AWS user access via identity federation between your authorization system and AWS.

If you have non-AWS users who requires access to your AWS resources.

Cross-account access between AWS accounts.

If you want to share access to particular AWS resources with users having other AWS accounts.

 

Do I need to Sign Up for IAM?

Although it's unnecessary to sign up to use IAM as it is free of cost, it's necessary to create an AWS account in order to use it. IAM only works with AWS products that are integrated with IAM. Now, if you want to sign up for AWS, you have to:

  1. Open https://portal.aws.amazon.com/billing/signup.
  2. Follow the online instructions.

You might also receive a phone call for a verification code. After signing up with AWS account, an AWS account root user is created who has access to all the AWS services and resources in the account and it's more secure to provide administrative access to an administrative user while using the root user for the tasks that requires root user only.


















































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