How to list all your Lambda functions across every AWS region

You know there's a Lambda function somewhere, but the Lambda console only shows one region at a time. If you're looking at Ohio and the function lives in Ireland, the list just looks empty. Accounts collect functions in odd places over the years: a tutorial someone ran in Oregon, a Lambda@Edge function that has to live in N. Virginia, something a teammate deployed close to customers. Nothing in the console tells you which regions to check.

In the AWS console

The plain way is to open Lambda → Functions and change the region menu at the top right, one region at a time. Most accounts have 17 regions turned on, so that's 17 page loads.

Two faster ways:

• Tag Editor. Open Resource Groups & Tag Editor → Tag Editor, set Regions to All regions and Resource types to AWS::Lambda::Function, and click Search resources. You get every function in one table, with its region, whether or not it has tags.
• Resource Explorer. If it's been turned on in your account (it needs a one-time setup that indexes every region), search for resourcetype:lambda:function.

Both give you names and regions, nothing more. To see a function's runtime, when it last changed or whether it's failing, you're back to opening each one in its own region.

With the AWS CLI

aws lambda list-functions also works on one region at a time, so loop over the regions your account has turned on:

for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
  aws lambda list-functions --region "$region" \
    --query 'Functions[].[FunctionName, Runtime, LastModified]' --output text |
    awk -v r="$region" '{print r "\t" $0}'
done

Each line is the region, the function's name, its runtime and when it last changed. Functions deployed as container images show None as their runtime.

A few notes:

• describe-regions returns only the regions turned on for your account, which are the only ones that can have anything in them.
• The CLI follows pagination for you, so a region with hundreds of functions comes back complete.
• You need lambda:ListFunctions and ec2:DescribeRegions. AWS's ReadOnlyAccess policy has both.

The list doesn't say whether anything is failing. For one function, CloudWatch can count its errors per hour:

aws cloudwatch get-metric-statistics --region eu-west-1 \
  --namespace AWS/Lambda --metric-name Errors \
  --dimensions Name=FunctionName,Value=image-resizer \
  --start-time 2026-10-02T00:00:00Z --end-time 2026-10-03T00:00:00Z \
  --period 3600 --statistics Sum

That's one function in one region per command, which doesn't scale to "is everything OK?". For reading the errors themselves, see how to see a Lambda function's logs and recent errors.

Or in Cloud GUI

Cloud GUI's Functions page does the loop for you: it looks in every region at once and shows all your functions in one list, each with its calls and errors for the last 24 hours. Click one to see its settings, the names of its environment variables (never the values) and an hourly chart. It's read-only, and free for one AWS account. Here's exactly how it gets access.