Amazon Web Services Datalake API

The Datalake API from Amazon Web Services — 13 operation(s) for datalake.

GitHub OpenAPI

Operations 13

POST /v1/datalake/logsources/aws Amazon Web Services Createawslogsource #
POST /v1/datalake/logsources/custom Amazon Web Services Createcustomlogsource #
PUT /v1/datalake Amazon Web Services Updatedatalake #
PUT /v1/datalake/exceptions/subscription Amazon Web Services Updatedatalakeexceptionsubscription #
GET /v1/datalake/organization/configuration Amazon Web Services Getdatalakeorganizationconfiguration #
POST /v1/datalake/logsources/aws/delete Amazon Web Services Deleteawslogsource #
DELETE /v1/datalake/logsources/custom/{sourceName} Amazon Web Services Deletecustomlogsource #
POST /v1/datalake/delete Amazon Web Services Deletedatalake #
POST /v1/datalake/organization/configuration/delete Amazon Web Services Deletedatalakeorganizationconfiguration #
POST /v1/datalake/delegate Amazon Web Services Registerdatalakedelegatedadministrator #
POST /v1/datalake/sources Amazon Web Services Getdatalakesources #
POST /v1/datalake/exceptions Amazon Web Services Listdatalakeexceptions #
POST /v1/datalake/logsources/list Amazon Web Services Listlogsources #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/amazon-web-services:amazon-web-services-datalake-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

OpenAPI Specification

amazon-web-services-datalake-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Amazon Web Services securitylake Datalake API
  description: 'Amazon Security Lake is a fully managed security data lake service. You can use Security Lake to automatically centralize security data from cloud, on-premises, and custom sources into a data lake that''s stored in your Amazon Web Services account. Amazon Web Services Organizations is an account management service that lets you consolidate multiple Amazon Web Services accounts into an organization that you create and centrally manage. With Organizations, you can create member accounts and invite existing accounts to join your organization. Security Lake helps you analyze security data for a more complete understanding of your security posture across the entire organization. It can also help you improve the protection of your workloads, applications, and data.


    The data lake is backed by Amazon Simple Storage Service (Amazon S3) buckets, and you retain ownership over your data.


    Amazon Security Lake integrates with CloudTrail, a service that provides a record of actions taken by a user, role, or an Amazon Web Services service. In Security Lake, CloudTrail captures API calls for Security Lake as events. The calls captured include calls from the Security Lake console and code calls to the Security Lake API operations. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Security Lake. If you don''t configure a trail, you can still view the most recent events in the CloudTrail console in Event history. Using the information collected by CloudTrail you can determine the request that was made to Security Lake, the IP address from which the request was made, who made the request, when it was made, and additional details. To learn more about Security Lake information in CloudTrail, see the Amazon Security Lake User Guide.


    Security Lake automates the collection of security-related log and event data from integrated Amazon Web Services and third-party services. It also helps you manage the lifecycle of data with customizable retention and replication settings. Security Lake converts ingested data into Apache Parquet format and a standard open-source schema called the Open Cybersecurity Schema Framework (OCSF).


    Other Amazon Web Services and third-party services can subscribe to the data that''s stored in Security Lake for incident response and security data analytics.'
tags:
- name: Datalake
paths:
  /v1/datalake/logsources/aws:
    POST:
      summary: Amazon Web Services Createawslogsource
      description: Adds a natively supported Amazon Web Service as an Amazon Security Lake source. Enables source types for member accounts in required Amazon Web Services Regions, based on the parameters you specify. You can choose any source type in any Region for either accounts that are part of a trusted organization or standalone accounts. Once you add an Amazon Web Service as a source, Security Lake starts collecting logs and events from it. You can use this API only to enable natively supported Amazon Web Services as a source. Use CreateCustomLogSource to enable data collection from a custom source.
      operationId: amazonWebServicesCreateAwsLogSource
      tags:
      - Datalake
  /v1/datalake/logsources/custom:
    POST:
      summary: Amazon Web Services Createcustomlogsource
      description: Adds a third-party custom source in Amazon Security Lake, from the Amazon Web Services Region where you want to create a custom source. Security Lake can collect logs and events from third-party custom sources. After creating the appropriate IAM role to invoke Glue crawler, use this API to add a custom source name in Security Lake. This operation creates a partition in the Amazon S3 bucket for Security Lake as the target location for log files from the custom source. In addition, this operation also creates an associated Glue table and an Glue crawler.
      operationId: amazonWebServicesCreateCustomLogSource
      tags:
      - Datalake
  /v1/datalake:
    PUT:
      summary: Amazon Web Services Updatedatalake
      description: Specifies where to store your security data and for how long. You can add a rollup Region to consolidate data from multiple Amazon Web Services Regions.
      operationId: amazonWebServicesUpdateDataLake
      tags:
      - Datalake
  /v1/datalake/exceptions/subscription:
    PUT:
      summary: Amazon Web Services Updatedatalakeexceptionsubscription
      description: Updates the specified notification subscription in Amazon Security Lake for the organization you specify.
      operationId: amazonWebServicesUpdateDataLakeExceptionSubscription
      tags:
      - Datalake
  /v1/datalake/organization/configuration:
    GET:
      summary: Amazon Web Services Getdatalakeorganizationconfiguration
      description: Retrieves the configuration that will be automatically set up for accounts added to the organization after the organization has onboarded to Amazon Security Lake. This API does not take input parameters.
      operationId: amazonWebServicesGetDataLakeOrganizationConfiguration
      tags:
      - Datalake
  /v1/datalake/logsources/aws/delete:
    POST:
      summary: Amazon Web Services Deleteawslogsource
      description: Removes a natively supported Amazon Web Service as an Amazon Security Lake source. You can remove a source for one or more Regions. When you remove the source, Security Lake stops collecting data from that source in the specified Regions and accounts, and subscribers can no longer consume new data from the source. However, subscribers can still consume data that Security Lake collected from the source before removal. You can choose any source type in any Amazon Web Services Region for either accounts that are part of a trusted organization or standalone accounts.
      operationId: amazonWebServicesDeleteAwsLogSource
      tags:
      - Datalake
  /v1/datalake/logsources/custom/{sourceName}:
    DELETE:
      summary: Amazon Web Services Deletecustomlogsource
      description: Removes a custom log source from Amazon Security Lake, to stop sending data from the custom source to Security Lake.
      operationId: amazonWebServicesDeleteCustomLogSource
      tags:
      - Datalake
  /v1/datalake/delete:
    POST:
      summary: Amazon Web Services Deletedatalake
      description: When you disable Amazon Security Lake from your account, Security Lake is disabled in all Amazon Web Services Regions and it stops collecting data from your sources. Also, this API automatically takes steps to remove the account from Security Lake. However, Security Lake retains all of your existing settings and the resources that it created in your Amazon Web Services account in the current Amazon Web Services Region. The DeleteDataLake operation does not delete the data that is stored in your Amazon S3 bucket, which is owned by your Amazon Web Services account. For more information, see the Amazon Security Lake User Guide.
      operationId: amazonWebServicesDeleteDataLake
      tags:
      - Datalake
  /v1/datalake/organization/configuration/delete:
    POST:
      summary: Amazon Web Services Deletedatalakeorganizationconfiguration
      description: Turns off automatic enablement of Amazon Security Lake for member accounts that are added to an organization in Organizations. Only the delegated Security Lake administrator for an organization can perform this operation. If the delegated Security Lake administrator performs this operation, new member accounts won't automatically contribute data to the data lake.
      operationId: amazonWebServicesDeleteDataLakeOrganizationConfiguration
      tags:
      - Datalake
  /v1/datalake/delegate:
    POST:
      summary: Amazon Web Services Registerdatalakedelegatedadministrator
      description: Designates the Amazon Security Lake delegated administrator account for the organization. This API can only be called by the organization management account. The organization management account cannot be the delegated administrator account.
      operationId: amazonWebServicesRegisterDataLakeDelegatedAdministrator
      tags:
      - Datalake
  /v1/datalake/sources:
    POST:
      summary: Amazon Web Services Getdatalakesources
      description: Retrieves a snapshot of the current Region, including whether Amazon Security Lake is enabled for those accounts and which sources Security Lake is collecting data from.
      operationId: amazonWebServicesGetDataLakeSources
      tags:
      - Datalake
  /v1/datalake/exceptions:
    POST:
      summary: Amazon Web Services Listdatalakeexceptions
      description: Lists the Amazon Security Lake exceptions that you can use to find the source of problems and fix them.
      operationId: amazonWebServicesListDataLakeExceptions
      tags:
      - Datalake
  /v1/datalake/logsources/list:
    POST:
      summary: Amazon Web Services Listlogsources
      description: Retrieves the log sources in the current Amazon Web Services Region.
      operationId: amazonWebServicesListLogSources
      tags:
      - Datalake