- Newest
- Most votes
- Most comments
Hello.
I have also experienced similar errors in the past.
At that time, I was able to resolve the issue by contacting AWS Support.
https://repost.aws/ja/questions/QUPpcS3wYaR12wHug50trqQQ/unknown-error-in-lambda
If the same error occurs even after clearing your browser's cache or accessing in an incognito window, I recommend contacting AWS Support at "Account and billing".
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Please inquire from the URL below.
https://console.aws.amazon.com/support
If your account has been marked as 'compromised' by AWS security, you will suddenly lose access to Lambda, even if using the root account, and get this error. You must resolve the account compromised issue before your access to Lambda will be reinstated. We are trying to have this error message improved.
Note: you should already have email communications from AWS Fraud regarding what steps you need to take to restore your account (and Lambda access). If not, please raise a non-technical (no charge) case following this URL https://support.console.aws.amazon.com/support/home?region=us-east-1#/case/create?issueType=customer-service&serviceCode=account-management&categoryCode=account-verification which will be passed to the security team to process.
There is no point in raising a technical support case - only the security team can remove the 'compromised' attribute from your account.
Relevant content
asked 3 years ago
asked 3 years ago
asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 4 months ago

Thank you! I submitted/responded to the ticket.