How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Amazon Security Lake Data Lakes API

Data lake creation and management

Amazon Security Lake Data Lakes API is one of 3 APIs that Amazon Security Lake publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Data Lakes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 3 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2018-05-10.

Requests are made against a single base URL, https://securitylake.{region}.amazonaws.com.

4 operations 2 paths 5 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2018-05-10
Base URL
https://securitylake.{region}.amazonaws.com
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

Amazon Security Lake Data Lakes API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (AWSSignatureV4). By default, every request must be authenticated.

  • AWSSignatureV4 — AWS Signature Version 4 authentication

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Data Lakes 4

Data lake creation and management

POST
/v1/datalake
Amazon Security Lake Create Data Lake
CreateDataLake body → 200400500
GET
/v1/datalake
Amazon Security Lake List Data Lakes
ListDataLakes 1 param → 200
PUT
/v1/datalake/{dataLakeArn}
Amazon Security Lake Update Data Lake
UpdateDataLake 1 param body → 200
DELETE
/v1/datalake/{dataLakeArn}
Amazon Security Lake Delete Data Lake
DeleteDataLake 1 param → 204400

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are DataLake (6 properties), CreateDataLakeRequest (2 properties), ListDataLakesResponse (1 property), UpdateDataLakeRequest (1 property). Each schema is shown below with its type and property counts.

CreateDataLakeResponse
object
1 property
UpdateDataLakeRequest
object
1 property
CreateDataLakeRequest
object
2 properties 1 required
ListDataLakesResponse
object
1 property
DataLake
object
Represents an Amazon Security Lake data lake configuration.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amazon-security-lake-data-lakes-api-openapi.yml Raw ↑

Other APIs Amazon Security Lake publishes across the network.

Amazon Security Lake Log Sources API
Amazon Security Lake Subscribers API
Where this information came from

This is an independent, third-party profile of Amazon Security Lake Data Lakes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.