- Newest
- Most votes
- Most comments
Hello.
I have noticed that all my user have this iam iam::471112587442 although they have different "Path": "/", "UserName": "RootRoni", "UserId": "AIDAW3MD7TCZF623LKSOG", username , is this why I cannot create phone number or lambda functions ?
"iam::471112587442" is the ARN of the IAM user.
It has nothing to do with Lambda not being able to create it.
Could you please share the exact error message you get when creating the Lambda?
Also, depending on the content of the error message, it may not be possible for the user to resolve the issue, so please contact AWS Support via "Account and billing".
Resources for Europe (London) Create function Access denied You don't have permission to perform this action. UnknownError
And in the create lambda function I just get UnknownError
Even when I try to using 1. Use a blueprint 2. Execution role Choose a role that defines the permissions of your function. To create a custom role, go to the IAM console . Create a new role with basic Lambda permissions. 3 . UnknownError
And in the create lambda function I just get UnknownError
Lambda's UnknownError is most likely an issue on the AWS side, so please contact AWS Support by opening a case under "Account and billing". https://repost.aws/questions/QUPpcS3wYaR12wHug50trqQQ/unknown-error-in-lambda
I have noticed that all my user have this iam iam::471112587442 although they have different "Path": "/", "UserName": "RootRoni", "UserId": "AIDAW3MD7TCZF623LKSOG", username , is this why I cannot create phone number or lambda functions ?
Relevant content
- asked a year ago
- Accepted Answerasked 6 years ago
- asked 3 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
Even going to here https://eu-west-2.console.aws.amazon.com/lambda/home?region=eu-west-2#/functions give me UnknowError , should I close my account and Start again , although I have done alot of work here , If nothing connects , or any Services work , then is no point in being here , wasting days and days , when I should actually be working