AWS Lambda 403 and weird errors everywhere
I'm unable to use AWS Lambda and to find a reasonable explanation.
- Dashboard shows error box with empty message
- Create form shows a spinner for 10 seconds and then stops and nothing happens
- API returns
{"message": null} - The user has enough permissions to use Lambda
I can just ask if someone faced something similar, since support doesn't want to answer my ticket.
Thanks
- 最新
- 投票最多
- 评论最多
Thanks for all the answers.
Luckily this issue has now been resolved. Turns out my account was compromised (maybe me logging in from another country) and contacting support (though a hidden chat) unlocked the resources and solved the issue.
Thanks.
Any chance you could point me in the direction of that hidden chat?? I'm having the exact same problem, both error in the browser and deploying from a serverless.js app 🙃
Based on the error the user does not have the right permissions. Try providing the user/role either of the following 2 AWS Managed policies based on your requirement.
The AWSLambda_ReadOnlyAccess policy grants read-only access to Lambda, Lambda console features, and other related AWS services. This policy was created by scoping down the previous policy AWSLambdaReadOnlyAccess.
The AWSLambda_FullAccess policy grants full access to Lambda, Lambda console features, and other related AWS services. This policy was created by scoping down the previous policy AWSLambdaFullAccess.
https://docs.aws.amazon.com/lambda/latest/dg/security_iam_troubleshoot.html
相关内容
AWS 官方已更新 4 个月前- AWS 官方已更新 3 年前
Is your lambda code shareable here? Otherwise can you confirm the code returns a correct message? Does it happen even with a simple hello world?
There's no code, It happens just by accessing "AWS Lambda > Functions", and also when creating a Function from scratch or just using the "Hello World" blueprint example. Also, tried creating a brand new user (non-root) with all the permissions and still the same issue.
The user you are logged in with, what IAM permissions has associated? Does this happen even with an user with full admin access? Have you tried to other regions? If so, the only reason left is that either disturbances in the region your account is created or something aws support must look into.