capabilities.work

Tear a Function Down in Dependency Order

A 5-step recipe with AWS Lambda. We can help you get access.

Recipe · 5 steps

Tear a Function Down in Dependency Order

with AWS Lambda · IT Infrastructure Management

Remove a function's event source mapping and URL, then delete the function.

  1. Confirm the function exists and capture its ARN before anything is deleted, so a mistyped name fails before it can detach resources belonging to some other function.
  2. List the event source mappings pointed at this function. These are independent resources that survive the function's deletion, so they must be enumerated before it disappears and their UUIDs become hard to recover.
  3. Delete the mapping so Lambda stops polling the event source. Deletion is asynchronous and returns 202 while the mapping drains in-flight records.
  4. Remove the public HTTPS endpoint. A function with no URL configured returns 404 here, which is a successful outcome for a teardown, so the flow continues to the deletion either way.
  5. Delete the function itself. Qualifier is deliberately omitted so that every version and alias is removed rather than a single version, leaving nothing behind.
What you'll need to have ready
  • functionName: The name or ARN of the function to tear down.
For your developer

Arazzo workflow aws-lambda:function-teardown, 5 operations: GetFunction → ListEventSourceMappings → DeleteEventSourceMapping → DeleteFunctionUrlConfig → DeleteFunction. Specs on APIs.io.

More recipes with AWS Lambda

Release a Version Behind an AliasShift Canary Traffic Across Two VersionsDeploy a Function and Verify It RunsWire an Event Source to a FunctionAudit a Function's Versions, Aliases, and Event SourcesExpose a Function Over an HTTPS Function URLFind a Compatible Layer Version to AttachWarm a Release with Provisioned ConcurrencyPublish a Layer Version and Attach It to a FunctionCap a Function with Reserved Concurrency