Files
spinifex/docs/coverage/ecr
Julian Sommer c24636c734 docs: put the not-applicable operations back in the one table
Splitting them into a second table repeated a reason on every row that shared
it and separated an operation from the rest of the surface it belongs to. One
table carries every operation the platform answers, served or refused, and the
reasons return to numbered footnotes below it.
2026-09-15 10:53:37 +10:00
..

title, seoTitle, description, category, sections, tags
title seoTitle description category sections tags
ECR API Coverage Elastic Container Registry API Coverage — Spinifex Docs The Amazon ECR API operations Spinifex implements, alongside the OCI distribution endpoint that carries the image layers, and those the platform will not. Coverage
overview
aws
compatibility
coverage
ecr
containers
registry

ECR API Coverage

Overview

Spinifex implements 19 operations in the ECR 2015-09-21 API model.

Two endpoints, one registry

Repository metadata is served over the AWS API on the gateway endpoint. Image data moves over the OCI Distribution /v2/ endpoint on that same host, authenticated by the bearer token GetAuthorizationToken mints for docker login.

The split explains the stubs below. The layer-transfer operations — BatchCheckLayerAvailability, InitiateLayerUpload, UploadLayerPart, CompleteLayerUpload and GetDownloadUrlForLayer — are registered stubs because the /v2/ endpoint carries that traffic instead. A client using docker or any OCI-compatible tool never calls them.

Registry replication is a stub for the same kind of reason: a deployment is a single registry, with no cross-region peer to replicate to.

Operations

Operation Status
BatchCheckLayerAvailability 🟡 Stub
BatchDeleteImage ✅ Implemented
BatchGetImage ✅ Implemented
BatchGetRepositoryScanningConfiguration ⛔ Not applicable 1
CompleteLayerUpload 🟡 Stub
CreateRepository ✅ Implemented
DeleteLifecyclePolicy ✅ Implemented
DeleteRepository ✅ Implemented
DeleteRepositoryPolicy ✅ Implemented
DescribeImageScanFindings ⛔ Not applicable 1
DescribeImages ✅ Implemented
DescribeRegistry 🟡 Stub
DescribeRepositories ✅ Implemented
GetAuthorizationToken ✅ Implemented
GetDownloadUrlForLayer 🟡 Stub
GetLifecyclePolicy ✅ Implemented
GetLifecyclePolicyPreview ✅ Implemented
GetRegistryPolicy 🟡 Stub
GetRegistryScanningConfiguration ⛔ Not applicable 1
GetRepositoryPolicy ✅ Implemented
InitiateLayerUpload 🟡 Stub
ListImages ✅ Implemented
ListTagsForResource ✅ Implemented
PutImage ✅ Implemented
PutImageScanningConfiguration ⛔ Not applicable 1
PutImageTagMutability ✅ Implemented
PutLifecyclePolicy ✅ Implemented
PutRegistryPolicy 🟡 Stub
PutRegistryScanningConfiguration ⛔ Not applicable 1
PutReplicationConfiguration 🟡 Stub
SetRepositoryPolicy ✅ Implemented
StartImageScan ⛔ Not applicable 1
StartLifecyclePolicyPreview ✅ Implemented
TagResource 🟡 Stub
UntagResource 🟡 Stub
UploadLayerPart 🟡 Stub
GetImageScanningConfiguration 🔒 Outside the pinned model
ListRepositories 🔒 Outside the pinned model
ReplicateImage 🔒 Outside the pinned model

Notes

  1. Image scanning is an AWS-hosted vulnerability service with no equivalent here, so a finding set would always be empty.