Amazon Security Lake · Arazzo Workflow

Amazon Security Lake Onboard AWS Log Source

Version 1.0.0

Add a natively supported AWS service as a log source and confirm it is collecting.

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

Provider

amazon-security-lake

Workflows

onboard-aws-log-source
Enable an AWS-native log source and verify it is registered and collecting.
Adds a natively supported AWS log source for the given accounts and regions, branches on whether any entries failed, lists the region's log sources to confirm registration, and reads the data lake source snapshot.
3 steps inputs: accounts, regions, sourceName, sourceVersion outputs: dataLakeSources, failed, sources
1
createAwsLogSource
Add the natively supported AWS service as a Security Lake log source for the requested accounts and regions.
2
listLogSources
List the log sources in the current region to confirm the AWS source has been registered.
3
getDataLakeSources
Read the data lake source snapshot for the supplied accounts to confirm the lake is collecting data from the newly added AWS source.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon Security Lake Onboard AWS Log Source
  summary: Add a natively supported AWS service as a log source and confirm it is collecting.
  description: >-
    Onboards a natively supported AWS service (such as CloudTrail management
    events or VPC flow logs) into Amazon Security Lake and verifies it is in
    place. The workflow adds the AWS log source for the requested accounts and
    regions, checks that no entries failed, lists the log sources in the region
    to confirm the source is registered, and reads back the data lake source
    snapshot to confirm the lake is collecting from 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: logSourcesApi
  url: ../openapi/amazon-security-lake-log-sources-api-openapi.yml
  type: openapi
workflows:
- workflowId: onboard-aws-log-source
  summary: Enable an AWS-native log source and verify it is registered and collecting.
  description: >-
    Adds a natively supported AWS log source for the given accounts and regions,
    branches on whether any entries failed, lists the region's log sources to
    confirm registration, and reads the data lake source snapshot.
  inputs:
    type: object
    required:
    - accounts
    - regions
    - sourceName
    properties:
      accounts:
        type: array
        description: AWS account IDs to enable the log source for.
        items:
          type: string
      regions:
        type: array
        description: AWS regions to enable the log source in.
        items:
          type: string
      sourceName:
        type: string
        description: The native AWS source name (e.g. CLOUD_TRAIL_MGMT, VPC_FLOW).
      sourceVersion:
        type: string
        description: The version of the AWS log source to enable.
  steps:
  - stepId: createAwsLogSource
    description: >-
      Add the natively supported AWS service as a Security Lake log source for
      the requested accounts and regions.
    operationId: CreateAwsLogSource
    requestBody:
      contentType: application/json
      payload:
        sources:
        - accounts: $inputs.accounts
          regions: $inputs.regions
          sourceName: $inputs.sourceName
          sourceVersion: $inputs.sourceVersion
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      failed: $response.body#/failed
    onSuccess:
    - name: noFailures
      type: goto
      stepId: listLogSources
      criteria:
      - context: $response.body
        condition: $.failed.length == 0
        type: jsonpath
    - name: someFailed
      type: goto
      stepId: listLogSources
      criteria:
      - context: $response.body
        condition: $.failed.length > 0
        type: jsonpath
  - stepId: listLogSources
    description: >-
      List the log sources in the current region to confirm the AWS source has
      been registered.
    operationId: ListLogSources
    parameters:
    - name: maxResults
      in: query
      value: 50
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      sources: $response.body#/sources
      nextToken: $response.body#/nextToken
  - stepId: getDataLakeSources
    description: >-
      Read the data lake source snapshot for the supplied accounts to confirm
      the lake is collecting data from the newly added AWS source.
    operationId: GetDataLakeSources
    requestBody:
      contentType: application/json
      payload:
        accounts: $inputs.accounts
        maxResults: 25
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      dataLakeSources: $response.body#/dataLakeSources
  outputs:
    failed: $steps.createAwsLogSource.outputs.failed
    sources: $steps.listLogSources.outputs.sources
    dataLakeSources: $steps.getDataLakeSources.outputs.dataLakeSources

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-onboard-aws-log-source-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.