- 最新
- 投票最多
- 评论最多
Hi Leolux,
I think you should verify by running the command "aws sts get-caller-identity" with the new credentials configured. [1]
And, as mentioned by @Victor, please confirm all the points, especially if the Access Key is active or not. [2]
If "Active", it should look like this (highlighted part):
References:
[1] https://docs.aws.amazon.com/cli/latest/reference/sts/get-caller-identity.html#examples
[2] https://repost.aws/knowledge-center/s3-access-key-error
已回答 3 年前
Hi, the command "aws sts get-caller-identity" executed with the new credentials returns three values for UserId, Account and Arn. I am not sure how this helps.
@IBAtulAnand: You shared a screenshot how the "active" status gets displayed. The problem is that my UI looks differently and I cannot extend the access key to check the status flag. So where can I find this page? IYou can see my screenshot and the status is active as well altough the UI looks not the same?
已回答 3 年前
My screenshot was taken on the address .console.aws.amazon.com/iamv2/home#/security_credentials
Thank you for the step by step guide. I checked all points but still the same issue. Therefore I even more think that the Security department has not correclty removed the account limitations that were removed according the them today.
已回答 3 年前
If you are using profiles and the AWS CLI make sure that your
.aws / credentials
file contains the correct key id and secret key.
已回答 3 年前

.console.aws.amazon.com/iamv2/home#/security_credentials and it looks differently because the UI is not the same. Where did you took the screenshot from?
Do I need to disable MFA authentication? Would that solve the issue that the active access key does not work?
@Leolux, I think you are looking at the correct place. You can see the access credentials from the "Security Credentials". Use this as a reference: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey
MFA should have no effect on AWS Credentials. Please check the credentials are correctly configured when you run the "aws sts get-caller-identity" command.
If not, try to reconfigure a new profile with the latest credential following this guide: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html