Creating a Lambda Web Function

To create a Web Function and endpoint (console)

1. Open the Lambda console at https://console.aws.amazon.com/lambda/.

2. In the navigation pane, choose Web Functions.

3. Choose Create Web Function.

4. Under Basic information, do the following:

   1. For Function name, enter a name for your Web Function.

   2. For Runtime, keep the default runtime.

   3. For Code source, keep Hello World template to start from a preconfigured example application. To deploy your own code instead, choose Upload ZIP file or Amazon S3.

5. Under Endpoint configuration, do the following:

   1. For Endpoint name, enter a name for the endpoint.

   2. For Type, keep Home-Region. A Home-Region endpoint runs in a single Region, which makes it the simplest configuration for your first Web Function. For multi-Region options, see Lambda Web Function endpoints.

      Note

      You can't change the endpoint type after creation.

   3. For Authentication type, choose Application-managed authentication. With this option, Lambda forwards all requests to your app, so your app handles authentication. To restrict access instead, choose IAM authentication, which requires callers to sign requests. Requests to HomeRegion and PerRegion endpoints use AWS Signature Version 4 (SigV4). Requests to MultiRegion endpoints use Signature Version 4a (SigV4a). For more information, see Lambda Web Function endpoint access control.

   4. For Auto deployment, keep Latest revision. With this mode, Lambda automatically routes all traffic to each new revision after it becomes Active. For manual traffic control with revision weights, choose Disabled. For more information, see Deployment patterns.

6. (Optional) Expand Additional configurations to override the default settings. By default, Lambda creates an execution role with permission to upload logs to Amazon CloudWatch, and an Amazon S3 bucket in your account to store your code. In this section you can instead choose an existing IAM role or your own Amazon S3 bucket, and you can also configure encryption with a customer managed key, the maximum concurrency per environment, environment variables, and tags.

7. Choose Create Web Function.

To deploy and test a starter Web Function

1. Run the following command:

   aws lambda-web deploy --name my-web-app --hello-world

   --hello-world writes the starter files to ./my-web-app, creating the directory if it does not exist. The starter contains server.ts, a TypeScript HTTP server, and package.json, README.md, and AGENTS.md.

2. When the deployment is complete, copy the endpoint URL from the output. The URL looks similar to the following:

   https://bcdfghjklmnpqrst.b7t.lambda-web.us-east-1.on.aws

3. Send a request to the endpoint URL that you copied in the previous step. Replace endpoint-url with that URL:

   curl endpoint-url

   The starter returns a response similar to the following:

   {"message":"Hello from Lambda Web!","path":"/"}

To create a Web Function with the API commands (AWS CLI)

1. Create a .zip deployment package from your app directory, with your entry file at the root of the package. Upload the package to an Amazon S3 bucket that meets the requirements in Prerequisites. The following commands create the package and use the AWS CLI to upload it.

   cd my-app
   zip -r ../my-app.zip .
   aws s3 cp ../my-app.zip s3://amzn-s3-demo-bucket/my-app.zip

2. Use the following AWS CLI command to create the Web Function with its first revision and endpoint. In revisionConfig, buildConfig specifies the code location and runtime, and serviceConfig specifies the execution role. The endpointConfig property defines the endpoint.

   aws lambda-web create-web-function \
       --function-name my-web-app \
       --revision-config '{
         "buildConfig": {
           "codeConfig": {
             "s3Object": { "bucket": "amzn-s3-demo-bucket", "key": "my-app.zip" }
           },
           "runtimeConfig": { "runtime": "nodejs24.x" }
         },
         "serviceConfig": {
           "executionRoleArn": "arn:aws:iam::111122223333:role/my-web-app-execution-role"
         }
       }' \
       --endpoint-config '{
         "endpointName": "my-endpoint",
         "endpointType": "HomeRegion",
         "authType": "ApplicationManaged",
         "autoDeploymentMode": "LatestRevision"
       }'

   The autoDeploymentMode property is optional. If you omit it, the default is Disabled, and the endpoint doesn't route traffic to new revisions automatically. Note the revisionId of the revision in the response.

3. Wait until the revision is Active. Replace rev-abc12 with the revision ID from the previous step.

   aws lambda-web wait web-function-revision-active \
       --function-name my-web-app \
       --revision-id rev-abc12

4. Get the endpoint's details.

   aws lambda-web get-web-function-endpoint \
       --function-name my-web-app \
       --endpoint-name my-endpoint

   When the endpoint's state is Active, send requests to its domainName. The response looks like the following excerpt.

   {
       "endpointName": "my-endpoint",
       "endpointType": "HomeRegion",
       "domainName": "bcdfghjklmnpqrst.b7t.lambda-web.us-east-1.on.aws",
       "authType": "ApplicationManaged",
       "autoDeploymentMode": "LatestRevision",
       "state": "Active",
       "updateStatus": "Successful"
   }

To deploy a change with the API commands (AWS CLI)

• Upload a new package and create a revision. A revision is a complete snapshot, so pass the full buildConfig and serviceConfig each time.

  aws s3 cp ../my-app.zip s3://amzn-s3-demo-bucket/my-app.zip
  aws lambda-web create-web-function-revision \
      --function-name my-web-app \
      --build-config '{
        "codeConfig": {
          "s3Object": { "bucket": "amzn-s3-demo-bucket", "key": "my-app.zip" }
        },
        "runtimeConfig": { "runtime": "nodejs24.x" }
      }' \
      --service-config '{
        "executionRoleArn": "arn:aws:iam::111122223333:role/my-web-app-execution-role"
      }'

  Because the endpoint has autoDeploymentMode set to LatestRevision, it routes all traffic to the new revision after the revision becomes Active. If you set autoDeploymentMode to Disabled, you route traffic with update-web-function-endpoint and revision weights instead. For more information, see Deployment patterns.