Managing Access Keys for IAM Users

By Ashwin Venugopal -

 







Managing Access Keys (Console)

An IAM user's access keys can be managed via AWS Management Console.

To create, modify, or delete your own IAM user access keys (console)

  1. Sign-in to the IAM console via AWS account ID or account alias, your IAM username, and password.
  2. Select your username and My Security Credentials in the navigation bar on the upper right.
  3. Now expand the Access Keys (access key ID and secret access key) section.
  4. You can perform any of the following tasks-

  • Select Create New Access Key in order to create an access key; while, if you want to copy and paste the key somewhere else to secure it, then, select Show Access Key.
  • If you want to disable an active access key, choose Make Inactive.
  • If you would like to reenable an inactive access key, choose Make Active.
  • Choose Delete, to delete your access key.

To create, modify, or delete another IAM user's access keys (console)

  1. Firstly, sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, choose Users in the navigation pane.
  3. Select the username whose access keys you want to manage, and then the Security Credentials tab.
  4. You can do the following in the Access Keys section:
  • Select Create New Access Key in order to create an access key, and then, Download.csv file to save its ID and secret access to a CSV file on your computer.
  • If you want to disable an active access key, choose Make Inactive.
  • If you would like to reenable an inactive access key, choose Make Active.
  • Choose Delete, to delete your access key.

To list the access keys for an IAM user (console)

  1. First of all, sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, choose Users in the navigation pane.
  3. Select the required username and then the Security Credentials tab. The user's access keys and the status of each key is displayed.

Note: However, only the user's access key ID is visible and the secret access key can only be retrieved when key is created.

To list the access key IDs for multiple IAM users (console)

  1. Sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, choose Users in the navigation pane.
  3. If required, you can also add the Access Key ID  column to the users table.
  4. The Access Key ID column shows each access key ID followed by its state.

This information may help in viewing and copying the access keys for the users having one or two access keys. The column will display None for the users with no access key.

To find which IAM user owns a specific access key (console)

  1. You have to sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, choose Users in the navigation pane.
  3. Type or paste the access key ID of the required user in the search box.
  4. If you want, you can also add the Access key ID  column to the users table.

Managing Access Keys (AWS CLI)

The following commands can be run to manage an IAM user's access keys from the AWS CLI-
  1. To create an access key: aws iam create-access-key.
  2. To disable or reenable an access key: aws iam update-access-key.
  3. To list a user's access keys: aws iam list-access-keys.
  4. To determine when an access key was most recently used: aws iam get-access-key-last-used.
  5. To delete an access key: aws iam delete-access-key.

Managing Access Keys (AWS API)

The following operations should be called to manage an IAM user's access keys from the AWS API-
  1. To create an access key: CreateAccessKey.
  2. To disable or reenable an access key: UpdateAccessKey.
  3. To list a user's access keys: ListAccessKeys.
  4. To determine when an access key was last used: GetAccessKeyLastUsed.
  5. To delete an access key: DeleteAccessKey.

























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