Amazon Security Lake
Amazon Security Lake is a service that automatically centralizes an organization's security data from cloud, on-premises, and custom sources into a purpose-built data lake stored in your own Amazon S3. It manages the data lifecycle to help you optimize storage and supports OCSF (Open Cybersecurity Schema Framework) for normalized security data analysis.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Amazon Security Lake the way a machine reads it — 46 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon Security Lake scores 75.3/100 (exemplar), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon Security Lake
Each block below is one kind of artifact we hold for Amazon Security Lake. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon Security Lake Data Lakes API
Data lake creation and management
Amazon Security Lake Log Sources API
AWS and custom log source management
Amazon Security Lake Subscribers API
Subscriber management for data access
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Amazon Security Lake API
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Amazon Security Lake API
OPEN COLLECTIONArazzo Workflows 7
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Amazon Security Lake Decommission Data Lake
Resolve a data lake, update its configuration, then delete its configuration object.
ARAZZOAmazon Security Lake Offboard Subscriber
Confirm a subscriber exists, then delete it and verify it is removed from the list.
ARAZZOAmazon Security Lake Onboard AWS Log Source
Add a natively supported AWS service as a log source and confirm it is collecting.
ARAZZOAmazon Security Lake Provision Data Lake
Create a Security Lake data lake, confirm it is listed, and inspect its collecting sources.
ARAZZOAmazon Security Lake Provision Subscriber
Create a subscriber, confirm its identity and status, and verify it is listed.
ARAZZOAmazon Security Lake Register Custom Source
Register a third-party custom log source and confirm it appears in the source list.
ARAZZOAmazon Security Lake Rename Subscriber
Find a subscriber by name, confirm it, and update its name and description.
ARAZZOScroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Security Lake Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Automatic Data Centralization
Automatically centralizes security data from AWS services, third-party tools, and custom sources into a single data lake.
OCSF Normalization
Converts security data to the Open Cybersecurity Schema Framework (OCSF) for standardized analysis across tools.
Apache Parquet Format
Stores all security data in Apache Parquet format optimized for analytical query performance.
Multi-Account Support
Centralizes security data across an entire AWS Organization from all accounts and regions.
Lifecycle Management
Automatically manages storage lifecycle with configurable retention and tiering policies.
Subscriber Access
Grant third-party SIEMs and analytics tools direct query access to your security data lake.
Native AWS Integration
Native connectors for CloudTrail, VPC Flow Logs, Route 53, Security Hub, and EKS audit logs.
Custom Log Sources
Ingest custom and third-party security data sources in OCSF format.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Security Lake Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon Security Lake API Rules
SPECTRALAmazon Security Lake API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Security Lake Data Lake Structure
JSON STRUCTUREAmazon Security Lake Log Source Structure
JSON STRUCTUREAmazon Security Lake Subscriber Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Security Data Centralization
Aggregate all security data from across a multi-account AWS environment into one queryable data lake.
SIEM Integration
Provide SIEM platforms like Splunk, Sumo Logic, and Microsoft Sentinel direct access to normalized security data.
Threat Hunting
Enable security analysts to query normalized OCSF data for threat hunting and forensic investigation.
Compliance Data Retention
Retain security logs in a cost-optimized data lake for compliance audit requirements.
Security Analytics
Run advanced analytics and ML models against normalized security data for anomaly detection.
Multi-Cloud Security Data
Centralize security data from on-premises and other cloud providers alongside AWS security data.
Resources
Every other property we hold for Amazon Security Lake — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 13
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 13 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-security-lake · machine-readable index on apis.io