Amazon Lambda · Arazzo Workflow

Amazon Lambda Teardown Event Source Mapping

Version 1.0.0

Locate an event source mapping in the list, confirm its details, then delete it.

1 workflow 1 source API 1 provider
View Spec View on GitHub ComputeEvent-DrivenFunction-as-a-ServiceFunctionsServerlessArazzoWorkflows

Provider

amazon-lambda

Workflows

teardown-event-source-mapping
List, confirm, and delete an event source mapping.
Lists event source mappings, takes the first returned mapping, reads its details by UUID, and deletes it.
3 steps inputs: EventSourceArn, FunctionName outputs: deletedState, targetUuid
1
listMappings
List the event source mappings, optionally filtered by function name or event source ARN, and take the first match.
2
confirmMapping
Read the full details of the selected mapping by UUID to confirm the target before deleting it.
3
deleteMapping
Delete the confirmed event source mapping by UUID.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Lambda Teardown Event Source Mapping
  summary: Locate an event source mapping in the list, confirm its details, then delete it.
  description: >-
    Cleanly removes an event source mapping. The workflow lists the existing
    mappings, selects the first one, reads its full details to confirm the target
    before any destructive action, and then deletes it. Every step spells out its
    request inline so the flow can be read and executed without opening the
    underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: eventSourceMappingsApi
  url: ../openapi/amazon-lambda-event-source-mappings-api-openapi.yml
  type: openapi
workflows:
- workflowId: teardown-event-source-mapping
  summary: List, confirm, and delete an event source mapping.
  description: >-
    Lists event source mappings, takes the first returned mapping, reads its
    details by UUID, and deletes it.
  inputs:
    type: object
    properties:
      FunctionName:
        type: string
        description: Optional function name filter when listing mappings.
      EventSourceArn:
        type: string
        description: Optional event source ARN filter when listing mappings.
  steps:
  - stepId: listMappings
    description: >-
      List the event source mappings, optionally filtered by function name or
      event source ARN, and take the first match.
    operationId: ListEventSourceMappings
    parameters:
    - name: FunctionName
      in: query
      value: $inputs.FunctionName
    - name: EventSourceArn
      in: query
      value: $inputs.EventSourceArn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      targetUuid: $response.body#/EventSourceMappings/0/UUID
    onSuccess:
    - name: foundMapping
      type: goto
      stepId: confirmMapping
      criteria:
      - context: $response.body
        condition: $.EventSourceMappings.length > 0
        type: jsonpath
    - name: noneFound
      type: end
      criteria:
      - context: $response.body
        condition: $.EventSourceMappings.length == 0
        type: jsonpath
  - stepId: confirmMapping
    description: >-
      Read the full details of the selected mapping by UUID to confirm the
      target before deleting it.
    operationId: GetEventSourceMapping
    parameters:
    - name: UUID
      in: path
      value: $steps.listMappings.outputs.targetUuid
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      state: $response.body#/State
      functionArn: $response.body#/FunctionArn
  - stepId: deleteMapping
    description: >-
      Delete the confirmed event source mapping by UUID.
    operationId: DeleteEventSourceMapping
    parameters:
    - name: UUID
      in: path
      value: $steps.listMappings.outputs.targetUuid
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deletedState: $response.body#/State
  outputs:
    targetUuid: $steps.listMappings.outputs.targetUuid
    deletedState: $steps.deleteMapping.outputs.deletedState

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/amazon-lambda-teardown-event-source-mapping-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.