Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

AWS IAM error : 'Your authentication information is incorrect. Please try again'

I am getting the error after I create an IAM user with AdministratorAccess or AmazonEC2FullAccess:

Your authentication information is incorrect. Please try again

I was able to create a user without a problem two weeks ago, while having active users. Now adding more new users gives me this error. I have tried creating new users using Copy permissions from existing user too but these new users also error out. (Picture of aws iam steps taken with error)

I apologize if this is a duplicate but an answer to a previous post of how to log in with new iam user did not solve my issue. I added

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "*",
            "Resource": "*"
        }
    ]
}

to inline policy JSON for this user but it still did not help.

like image 862
thuy Avatar asked May 16 '18 19:05

thuy


People also ask

How do I resync my MFA?

In the navigation pane, choose Users, and then choose the name of the user whose MFA device needs to be resynchronized. Choose the Security credentials tab. Next to Assigned MFA device, choose Manage. In the Manage MFA device wizard, choose Resync, and then choose Continue.

Why my AWS account is not working?

You can't sign in to an AWS account because you're using incorrect credentials (email address, user name, or password), or you forgot the credentials that you use to sign in to an AWS account. You received a notification that there is an issue with your AWS account (for example, that it's closed or suspended).

How do I authenticate AWS account?

To authenticate from the console as a root user, you must sign in with your email address and password. As an IAM user, provide your account ID or alias, and then your user name and password. To authenticate from the API or AWS CLI, you must provide your access key and secret key.


1 Answers

I end up switching to use Autogenerated password option and my users are now able to get in. retest using the custom password and it's working now too. Something must of gotten fix on AWS.

like image 57
thuy Avatar answered Nov 25 '22 18:11

thuy