Signing in to the AWS Management Console as an IAM user or root user

By Ashwin Venugopal -

 







Sign in As the Root User

You must know the following information before signing-in to an AWS account:

Requirements-

  1. The email address used to create the AWS account.
  2. The password for the root user.

To sign in to an AWS account as the root user:

  • Firstly, open https://console.aws.amazon.com/.
  • The main sign-in page will appear as saying select the Root user, enter the email address linked to your account, and then select Next.
  • Now you can enter your password and sign-in.

Sign-in as an IAM User

As seen above, for this one also, you must have the following information:

Requirements:

  1. One of the two- the account alias or the 12 digit AWS account ID.
  2. User name for your IAM user.
  3. Password for your IAM user.

A root user or an IAM administrator should either provide the AWS account ID or an AWS account alias to an IAM user while an IAM user can easily log in either with a sign-in URL or the main sign-in page.

To sign in to an AWS account as an IAM user using an IAM user's sin-in URL 

  1. Open a browser and enter the following URL after replacing account_alias_or_id with account alias or account ID given by your administrator- 

  https://account_alias_or_id.signin.aws.amazon.com/console/

       2. Now you can enter your IAM user name as well as password and sign in. 

To sign in to an AWS account as an IAM user using the main sign-in page

  1. Firstly, open https://console.aws.amazon..com/.
  2. After that, you have to choose IAM user, enter the account alias or account ID, and choose Next.
  3. Now you can enter your IAM user name and password and sign-in.

However, if you have already signed-in as an IAM user for another AWS account before via this browser, or if you want sign-in as a root user, then, you must pick Sign in using root user email in order to go back to the main sign-in page.

















































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 groups of computers, re
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 of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more