Managing Access Keys for IAM Users

By Ashwin Venugopal -

 






Resetting Lost or Forgotten Passwords or Access Keys for AWS

The lost or forgotten passwords or access keys cannot be retrieved from IAM, however, they can be reset via following methods:
  • AWS account root user password- The root user password can be reset from the AWS Management Console.

  • AWS account access keys- The new account access keys can be created without disabling the existing ones and they can also be deleted when not in use anymore.

  • IAM user password- You can ask your administrator to reset your IAM password if you have forgotten it.

  • IAM user access keys- If you have permission you can create your own access keys in case you forget them and its instructions can be given at Managing access keys (console). However, if you don't have the permissions you have to ask your administrator to create the new ones and not to delete the old ones if they are still in use.

Resetting a Lost or Forgotten Root User Password

In case you forget your root user password, you can reset it from the AWS Management Console.

To reset your root user password

  • Use your AWS account email address to sign-in to the AWS Management Console as the root root user and then select Next.

  • Now select Forgot your password?.

  • Write the email address linked with the account and then provide the CAPTCHA text, after that choose Continue.

  • Look for the message from Amazon Web Services in the email related with your AWS account which will generally have an address ending like @amazon.com or aws.amazon.com and follow its instructions. However, check your spam if you don't see it in inbox.



























































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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more