Amazon CloudTrail
AWS CloudTrail enables governance, compliance, operational auditing, and risk auditing of your AWS account by tracking user activity and API usage across AWS environments, hybrid setups, and multicloud deployments with immutable audit trails.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amazon CloudTrail the way a machine reads it — 50 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 CloudTrail scores 59.1/100 (developing), with a separate agent-readiness read of 58/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 CloudTrail
Each block below is one kind of artifact we hold for Amazon CloudTrail. 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 CloudTrail Event Data Stores API
Operations for managing CloudTrail Lake event data stores
Amazon CloudTrail Events API
Operations for looking up and querying events
Amazon CloudTrail Trails API
Operations for creating and managing CloudTrail trails
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
amazon-cloudtrail-mcp.yml
MCP SERVERFeatures 5
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.
Event Aggregation
Consolidate activity events from AWS, external providers, on-premises, and SaaS into a unified audit trail.
Immutable Audit Logs
Store audit-worthy events immutably to ensure tamper-proof compliance records.
CloudTrail Insights
Detect unusual API activity patterns with anomaly detection on management and data events.
SQL Query Support
Investigate issues using SQL queries or natural language with Amazon Athena integration.
Multi-Region Trails
Create trails that capture events from all AWS regions in a single S3 bucket.
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 Cloudtrail 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 CloudTrail API Rules
SPECTRALAmazon CloudTrail API Rules
SPECTRALJSON Schema 9
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.
Amazon CloudTrail Event
JSON SCHEMACreateEventDataStoreRequest
JSON SCHEMACreateEventDataStoreResponse
JSON SCHEMACreateTrailRequest
JSON SCHEMACreateTrailResponse
JSON SCHEMADescribeTrailsResponse
JSON SCHEMAListEventDataStoresResponse
JSON SCHEMALookupEventsRequest
JSON SCHEMALookupEventsResponse
JSON SCHEMAScroll within the panel for all 9 ·
JSON Structure 8
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.
Cloudtrail Create Event Data Store Request Structure
JSON STRUCTURECloudtrail Create Event Data Store Response Structure
JSON STRUCTURECloudtrail Create Trail Request Structure
JSON STRUCTURECloudtrail Create Trail Response Structure
JSON STRUCTURECloudtrail Describe Trails Response Structure
JSON STRUCTURECloudtrail List Event Data Stores Response Structure
JSON STRUCTURECloudtrail Lookup Events Request Structure
JSON STRUCTURECloudtrail Lookup Events Response Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 8
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.
Scroll within the panel for all 8 ·
Security Posture 3
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 4
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.
Compliance Auditing
Demonstrate adherence to SOC, PCI DSS, and HIPAA regulations with audit logs.
Security Monitoring
Record and monitor user and API activity for security incident detection.
Operational Debugging
Investigate operational issues by querying historical API activity.
Governance
Track who made changes to AWS resources and when for governance accountability.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Amazon S3
Store CloudTrail logs in S3 buckets with lifecycle management.
Amazon Athena
Query CloudTrail logs using SQL via Athena integration.
Amazon CloudWatch
Stream CloudTrail events to CloudWatch Logs for real-time monitoring.
AWS Lambda
Trigger Lambda functions based on CloudTrail events for automated response.
AWS Security Hub
Send CloudTrail findings to Security Hub for centralized security management.
Resources
Every other property we hold for Amazon CloudTrail — 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 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
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 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-cloudtrail · machine-readable index on apis.io