Amazon Security Lake · Arazzo Workflow

Amazon Security Lake Offboard Subscriber

Version 1.0.0

Confirm a subscriber exists, then delete it and verify it is removed from the list.

1 workflow 1 source API 1 provider
View Spec View on GitHub Data LakeSecuritySIEMThreat DetectionArazzoWorkflows

Provider

amazon-security-lake

Workflows

offboard-subscriber
Confirm a subscriber, delete it, and verify removal from the account list.
Reads a subscriber by ID, branches on its status, deletes it, and lists subscribers to confirm removal.
3 steps inputs: subscriberId outputs: deletedSubscriberId, subscribers
1
getSubscriber
Read the subscriber by ID to confirm it exists and capture its current status before deletion.
2
deleteSubscriber
Delete the confirmed subscriber and remove it from Amazon Security Lake.
3
listSubscribers
List the remaining subscribers for the account to confirm the subscriber has been removed.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Security Lake Offboard Subscriber
  summary: Confirm a subscriber exists, then delete it and verify it is removed from the list.
  description: >-
    Offboards a data subscriber from Amazon Security Lake in a verified
    sequence. The workflow reads the subscriber by ID to confirm it exists,
    branches on whether the subscriber is active or already deactivated, deletes
    the subscriber, and then lists subscribers to confirm it has been removed.
    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: subscribersApi
  url: ../openapi/amazon-security-lake-subscribers-api-openapi.yml
  type: openapi
workflows:
- workflowId: offboard-subscriber
  summary: Confirm a subscriber, delete it, and verify removal from the account list.
  description: >-
    Reads a subscriber by ID, branches on its status, deletes it, and lists
    subscribers to confirm removal.
  inputs:
    type: object
    required:
    - subscriberId
    properties:
      subscriberId:
        type: string
        description: The ID of the subscriber to offboard.
  steps:
  - stepId: getSubscriber
    description: >-
      Read the subscriber by ID to confirm it exists and capture its current
      status before deletion.
    operationId: GetSubscriber
    parameters:
    - name: subscriberId
      in: path
      value: $inputs.subscriberId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      subscriberId: $response.body#/subscriberId
      subscriberStatus: $response.body#/subscriberStatus
    onSuccess:
    - name: subscriberActive
      type: goto
      stepId: deleteSubscriber
      criteria:
      - context: $response.body
        condition: $.subscriberStatus == "ACTIVE"
        type: jsonpath
    - name: subscriberDeactivated
      type: goto
      stepId: deleteSubscriber
      criteria:
      - context: $response.body
        condition: $.subscriberStatus == "DEACTIVATED"
        type: jsonpath
  - stepId: deleteSubscriber
    description: >-
      Delete the confirmed subscriber and remove it from Amazon Security Lake.
    operationId: DeleteSubscriber
    parameters:
    - name: subscriberId
      in: path
      value: $steps.getSubscriber.outputs.subscriberId
    successCriteria:
    - condition: $statusCode == 204
    outputs:
      deletedSubscriberId: $steps.getSubscriber.outputs.subscriberId
  - stepId: listSubscribers
    description: >-
      List the remaining subscribers for the account to confirm the subscriber
      has been removed.
    operationId: ListSubscribers
    parameters:
    - name: maxResults
      in: query
      value: 50
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      subscribers: $response.body#/subscribers
  outputs:
    deletedSubscriberId: $steps.deleteSubscriber.outputs.deletedSubscriberId
    subscribers: $steps.listSubscribers.outputs.subscribers

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-security-lake-offboard-subscriber-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.