Introduction

A Lambda function does not automatically have a public HTTP URL just because it exists. The URL comes from the HTTP-facing service you attach to it, most commonly API Gateway or a Lambda Function URL. So the answer to "where do I find the URL?" depends on which integration you created.

Case 1: You Used API Gateway

If your Lambda function is exposed through API Gateway, the URL lives in the API Gateway resource, not in the Lambda function itself.

Typical API Gateway endpoint formats look like this:

• REST or HTTP API endpoint such as https://abc123.execute-api.us-east-1.amazonaws.com
• optionally followed by a stage name such as /prod
• optionally followed by a route such as /users

So the effective URL might be:

https://abc123.execute-api.us-east-1.amazonaws.com/prod/users

In the AWS console, you find it by opening API Gateway and viewing the deployed API or stage.

Case 2: You Used A Lambda Function URL

AWS also supports Lambda Function URLs, which are simpler than API Gateway for basic direct HTTP access.

If you enabled a Function URL, the URL is attached directly to the Lambda function. It usually looks like this:

https://abcdefg.lambda-url.us-east-1.on.aws/

In the console, open the Lambda function and look for the Function URL section.

Why People Get Confused

The confusion usually comes from mixing three different layers:

• the Lambda function itself
• API Gateway routes and stages
• Lambda Function URLs

A Lambda function is compute. It does not become a web endpoint until some HTTP entry point is configured.

That is why one Lambda may have:

• no HTTP URL at all
• an API Gateway URL
• a Function URL
• several different URLs through multiple integrations

Example: API Gateway + Lambda

A minimal event handler in Node.js might look like this:

1export const handler = async (event) => {
2  return {
3    statusCode: 200,
4    headers: { "Content-Type": "application/json" },
5    body: JSON.stringify({ ok: true, path: event.rawPath ?? null })
6  };
7};

This code can serve HTTP traffic, but the URL still comes from the gateway or function URL resource, not from the handler code.

Example: Invoking A Found URL

Once you know the endpoint, test it explicitly.

curl https://abcdefg.lambda-url.us-east-1.on.aws/

or, for API Gateway:

curl https://abc123.execute-api.us-east-1.amazonaws.com/prod/users

If that fails, the issue is usually deployment, permissions, authorizers, or route configuration, not the Lambda handler alone.

How To Check Programmatically

If you are using infrastructure as code, the URL is often an output value or an attribute from the gateway or function URL resource.

For example, in CloudFormation or similar tooling, you typically export:

• API endpoint URL
• stage URL
• Lambda Function URL

That makes the URL easy to retrieve after deployment rather than hunting through the console manually.

Security And Access Mode Matter

Finding the URL is only part of the story. You also need to know whether the endpoint is public, IAM-protected, or fronted by some other access control.

A URL existing does not mean it is anonymously callable.

For example:

• API Gateway may require authorizers or API keys
• Function URLs can use public access or IAM auth

So if you get 403 instead of a response, the URL may be correct but the access mode may not match your request.

Common Pitfalls

A common mistake is looking only in the Lambda console when the function is actually exposed through API Gateway. In that setup, the public URL belongs to API Gateway.

Another issue is assuming the console automatically creates a web endpoint. A plain Lambda function with no HTTP integration has no browser-friendly URL.

Developers also sometimes forget the stage portion of an API Gateway URL. Hitting the base host without the deployed stage or route can make the endpoint seem missing.

Finally, do not confuse a Lambda ARN with a callable HTTP URL. They identify the same function in different systems, but they are not interchangeable.

Summary

• A Lambda function gets an HTTP URL only through an HTTP-facing integration such as API Gateway or a Lambda Function URL.
• If you used API Gateway, find the endpoint in API Gateway, including stage and route.
• If you enabled a Function URL, find it in the Lambda function's Function URL settings.
• The Lambda code does not determine the public URL by itself.
• Check access controls as well as the endpoint string when debugging HTTP invocation issues.