Root User - Lambda Functions are Gone!

This issue of not being able to see your Lambda functions as a root user and encountering "Access denied" and "UnknownError" messages is not uncommon. There are several potential reasons for this problem:

1. Region Check: Ensure you're in the correct AWS region where your Lambda functions were originally created. Lambda functions are region-specific, so if you're in a different region, they won't be visible.

2. Temporary Account Block: Your account may have experienced a temporary block due to a suspected malicious access attempt. This can cause functions to become temporarily inaccessible, even for the root user.

3. Service Health: There might be ongoing issues or outages with Lambda in your region. It's worth checking the AWS Service Health Dashboard to see if there are any reported problems.

4. Browser/Device Issue: Try accessing your Lambda functions from a different browser or device to rule out any local issues.

5. Organizations and SCP: If your AWS account is managed by Organizations, check that Lambda operations are not prohibited by Service Control Policies (SCPs).

Given that you're experiencing this issue as a root user and can't perform Lambda operations, it's likely that there might be a problem with your AWS account itself. In this case, the best course of action is to contact AWS Support directly. You can open a support case under the "Account and billing" category, which can be done free of charge. AWS Support will be able to investigate any account-specific issues that might be causing this problem and provide you with a resolution.

While waiting for a response from AWS Support, you might want to check your CloudTrail event history (if accessible) to see if there are any clues about recent activities or changes related to your Lambda functions.
Sources
Not able to see my lambda functions | AWS re:Post
Access denied in creating lambda function | AWS re:Post

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