Amazon ECR
Amazon Elastic Container Registry (ECR) is a fully managed container registry that makes it easy to store, manage, share, and deploy container images and artifacts. ECR eliminates the need to operate your own container repositories or worry about scaling the underlying infrastructure, and integrates with Amazon ECS and Amazon EKS for simplified development to production workflows.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Amazon ECR the way a machine reads it — 49 machine-readable artifacts across 6 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 ECR scores 71.9/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 ECR
Each block below is one kind of artifact we hold for Amazon ECR. 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 6
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 ECR Amazon ECR Amazon Elastic Container Registry (ECR) API API
The Amazon ECR Amazon Elastic Container Registry (ECR) API API from Amazon ECR — 1 operation(s) for amazon ecr amazon elastic container registry (ecr) api.
Amazon ECR #BatchGetImage API
The #BatchGetImage API from Amazon ECR — 1 operation(s) for #batchgetimage.
Amazon ECR #DeleteRepository API
The #DeleteRepository API from Amazon ECR — 1 operation(s) for #deleterepository.
Amazon ECR #DescribeRepositories API
The #DescribeRepositories API from Amazon ECR — 1 operation(s) for #describerepositories.
Amazon ECR #ListImages API
The #ListImages API from Amazon ECR — 1 operation(s) for #listimages.
Amazon ECR #PutImage API
The #PutImage API from Amazon ECR — 1 operation(s) for #putimage.
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 ECR Amazon Elastic Container Registry (ECR) 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 ECR Decommission Repository
Inventory a repository's images, then delete it with a force branch when images remain.
ARAZZOAmazon ECR Ensure Repository and Seed Image
Describe a repository, create it only when missing, then seed it with an image manifest.
ARAZZOAmazon ECR Image Inventory
Describe a repository, list its image IDs with pagination, and fetch image detail.
ARAZZOAmazon ECR Provision Repository
Create a container repository, confirm it exists, and inspect its current images.
ARAZZOAmazon ECR Publish Image
Confirm a repository exists, put an image manifest, then read the image back.
ARAZZOAmazon ECR Registry Audit
Page through every repository in a registry following the DescribeRepositories token loop.
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 Ecr 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 Ecr Finops
FINOPSFeatures 7
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.
Fully Managed Registry
Eliminate the need to operate your own container repositories or worry about scaling infrastructure.
Image Vulnerability Scanning
Automated vulnerability assessment via Amazon Inspector integration for continuous image security.
Lifecycle Policies
Automatically expire and delete images based on rules to reduce storage costs.
Cross-Account Replication
Replicate images to registries in other AWS accounts and regions for availability.
OCI Artifact Support
Store and manage OCI-compliant artifacts including Helm charts and SBOMs.
Image Signing
Sign and verify container images automatically without additional infrastructure.
Pull Through Cache
Cache upstream public registry images in ECR for reduced egress costs and improved availability.
Scroll within the panel for all 7 ·
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 Ecr 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 ECR API Rules
SPECTRALAmazon ECR 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 ECR Repository
JSON SCHEMACreateRepositoryResponse
JSON SCHEMADescribeRepositoriesResponse
JSON SCHEMARepository
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 Ecr Repository Structure
JSON STRUCTUREEcr Openapi Create Repository Response Structure
JSON STRUCTUREEcr Openapi Describe Repositories Response Structure
JSON STRUCTUREEcr Openapi Repository 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.
CI/CD Pipeline Integration
Store container images in ECR and deploy to ECS or EKS as part of automated pipelines.
Security and Compliance
Automated vulnerability scanning and image signing for security-compliant container deployments.
Multi-Region Deployments
Replicate images across regions for low-latency pulls and improved resilience.
Helm Chart Repository
Store Helm charts as OCI artifacts for Kubernetes application deployment management.
Image Lifecycle Management
Manage image retention policies to keep registries clean and reduce storage costs.
Resources
Every other property we hold for Amazon ECR — 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-ecr · machine-readable index on apis.io