Amazon EFS
Amazon Elastic File System (EFS) provides a simple, serverless, set-and-forget elastic file system for use with AWS cloud services and on-premises resources. EFS is built to scale on demand to petabytes without disrupting applications, growing and shrinking automatically as you add and remove files.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Amazon EFS the way a machine reads it — 43 machine-readable artifacts across 1 API, 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 EFS scores 71.3/100 (exemplar), with a separate agent-readiness read of 48/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 EFS
Each block below is one kind of artifact we hold for Amazon EFS. 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 1
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 EFS 2015 02 01 API
The 2015 02 01 API from Amazon EFS — 3 operation(s) for 2015 02 01.
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.
Open 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 EFS Amazon Elastic File System (EFS) API
OPEN COLLECTIONArazzo Workflows 6
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 EFS Decommission File System
Confirm a file system has no mount targets, then delete the file system.
ARAZZOAmazon EFS Find or Create File System
Look up a file system by creation token and create it only if it does not already exist.
ARAZZOAmazon EFS Inspect File System Topology
Describe a file system and enumerate its mount targets to audit its network topology.
ARAZZOAmazon EFS Multi-AZ Mount Targets
Create a file system, wait until available, then attach mount targets in two Availability Zones.
ARAZZOAmazon EFS Provision File System
Create an EFS file system, wait for it to become available, then attach a mount target.
ARAZZOAmazon EFS Provision Mount Target
Verify a file system is available, create a mount target, then poll until the mount target is available.
ARAZZOPricing 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 Efs 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.
Amazon Efs Finops
FINOPSFeatures 6
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.
Elastic Scalability
Automatically grows and shrinks as you add and remove files with no provisioning required.
Multiple Storage Classes
Standard, Infrequent Access, and Archive storage classes with automatic lifecycle management.
Multi-AZ Replication
Data automatically replicated across multiple Availability Zones for 99.999999999% durability.
Concurrent Access
Thousands of EC2 instances and Lambda functions can access the same file system simultaneously.
EFS Access Points
Application-specific entry points with customized directory access and POSIX permissions.
AWS Backup Integration
Centralized backup management for EFS file systems with policy-based retention.
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 Efs 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 EFS API Rules
SPECTRALAmazon EFS API Rules
SPECTRALJSON Schema 4
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 EFS FileSystem
JSON SCHEMADescribeFileSystemsResponse
JSON SCHEMAFileSystem
JSON SCHEMAMountTarget
JSON SCHEMAJSON Structure 4
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 Efs Filesystem Structure
JSON STRUCTUREEfs Openapi Describe File Systems Response Structure
JSON STRUCTUREEfs Openapi File System Structure
JSON STRUCTUREEfs Openapi Mount Target Structure
JSON STRUCTUREExamples 4
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 5
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.
Containerized Application Storage
Persistent shared storage for containerized applications running on ECS or EKS.
Machine Learning
Shared training data storage accessible simultaneously by multiple compute instances.
Content Management
Shared file storage for web servers and CMS platforms requiring concurrent file access.
DevOps and Code Sharing
Centralized code and configuration storage accessible by development teams and CI/CD pipelines.
Big Data Analytics
High-throughput shared storage for analytics workloads requiring parallel data access.
Resources
Every other property we hold for Amazon EFS — 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 5
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
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 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-efs · machine-readable index on apis.io