- Newest
- Most votes
- Most comments
Yes, the region is correct. We've been using aws for over a year now and the problem started last weekend. We also use other services such as DynamoDB and API Gateway that appear to be unaffected.
@secondabhi_aws we use the basic plan and from what I understand we can't open tech support cases without a subscription to that. If this is true, is there any other free way to solve this problem? It doesn't seem to be a problem caused by us, as things have worked fine for a year or so.
Thanks for the 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.
I have the same issue. All of my functions also fail
I didn't make any changes.
My EC2 instance is working, so problem is only with AWS lambda
EDIT: solution:
I had a support case from AWS(no email, only notification in console) that said I had a security breach for one of my Access keys. I had to resolve that issue and then functions came back.
How long did it take for the lambdas to come back? I just resolved mine, but they're still gone.
I got the same issue. How did you manage? Tell me process
Make sure you are looking at the correct region and that you have the correct permissions.
Also, make sure that time on your system is correct. Sometimes, if the time is off, when the client signs the request, the signature may be invalid.
I am having the same issue. The user has AdministratorAccess and Full Lambda. Are there any other permissions that may be missing? Also, this happened immediately after a support case on suspicious activity was resolved.
Try using the CLI to list the functions:
aws lambda list-functionsI am using root account and I tried to switch to different region and the issue still there
Hi,
You can also check the status of any service event through Personal Health Dashboard.
I'd suggest you to log out and log back in and see if problem still persists or not. If you still see the same error, I'd suggest you to log AWS Support Case.
Hope you find this information helpful.
Comment here if you have additional questions, happy to help.
Abhishek
Hi I am found nothing suspicious on Health dashbroad.
The same error exists for me as well. is it related to the free tier plan?
I also have the same problem as a bove, please give me solution =(((((
Hi All, I have the same issue wiht lambda functions. Did anyone able to resolve this?
Hi, I am having the same issue and if someone can help me regarding this it would be great!
Hi All I having same issue , appreciate if someone support to resolve it, I can not create a basic lambda function on the console.
Hi , I also have the same issue. Some of my production environment was there. And I cant access it right now. It happened all of a sudden. I didn't even make any change there.
This just happened to me now. All of my lambda functions are gone in all regions. I cannot view them or make calls to them!!
Could be either permissions related (https://repost.aws/knowledge-center/granular-access-lambda), or related to newly created accounts. For latter, I d suggest to contact AWS Support
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago

I absolutely get it, there is no fault at your end. I also understand, you can't open support case with the basic support plan. Such type of issue are not long persistent, I believe it should have been gone by now. Are you still facing the issue.
@secondabhi_aws I'm also having the exact same issue right now. For 2 3 hours, I can't access my code in lambda. It says "Unknown Error" and my code in Lambda doesn't work. Can you also help me?
@secondabhi_aws - I'm also having the issue, has this been resolved?
I am seeing the same issue right now.
How did it get resolved for everyone here?