Permitting IAM Users to Change their Own Passwords

By Ashwin Venugopal -

 







To Allow All IAM Users Change Their Own Passwords

  • Firstly, sign-in to the AWS Management Console and open IAM Console at https://console.aws.amazon.com/iam/.

  • Choose Account Settings in the navigation pane.

  • If your account uses the default password policy, you have to select Change Password policy in the password policy section. However, if you use custom password policy, you have to choose Change.

  • Now, select Allow users to change their own password and then Save changes which allows all the users in the account access to the iam: ChangePassword action for only their user and to the iam: GetAccountPasswordPolicy action.

  • Provide the users with the instructions for changing their passwords. 

To Allow Selected IAM Users Change Their Own Passwords

  • First of all, sign-in to the AWS Management Console and open IAM Console at https://console.aws.amazon.com/iam/.

  • Choose Account Settings in the navigation pane.

  • Don't select Change Password policy in the password policy section as it will allow all the users to change their passwords.

  • If the users who are allowed to change their passwords doesn't exist, then, create them.

  • An IAM group of the users with permissions to change their passwords should be created and then the users from the previous step should be added with them. (optional)

  • Now, assign a policy that can allow access to the ChangePassword action, letting the users to change only their own passwords from the console, the AWS CLI, Tools for Windows PowerShell, or the API. The access to the GetAccountPasswordPolicy action is also provided which helps the users to view the current password policy.

  • Provide the users with the instructions for changing their passwords. 

How an IAM User Changes Their Own Password?

If the permission for changing your own IAM user password is already given, then, a special page present in the AWS Management Console (along with the AWS CLI or AWS API) can be used to do this.

To Change Your Own IAM User Password (Console)

  1. Firstly, sign-in to the IAM console via your AWS account ID or account alias, IAM username, and password.
  2. Now, select a username, and then My Security Credentials in the upper right navigation bar.
  3. Choose Change password on the AWS IAM Credentials.
  4. After that, you can enter your current password for Current Password as well as New password for the new one and then Confirm it. Select Change Password.

How IAM Users Change Their Own Password (AWS CLI or AWS API)?

The following methods shows how IAM users can use the AWS CLI or AWS API to change their own password.

To Change Your Own IAM Password Use:

  1. AWS CLI: aws iam change-password.
  2. AWS API: ChangePassword
































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