SYSTEM Cited by 1 source
Amazon ECR (Elastic Container Registry)¶
Amazon ECR is AWS's managed OCI-compatible container image registry: customers push Docker / OCI images to private (or public) repositories and pull them from any AWS compute substrate that consumes containers — EKS, ECS, Lambda, SageMaker, App Runner, Fargate, EC2, and more.
ECR exposes the standard OCI registry API, integrates with IAM for access control, and supports cross-region replication, image scanning for vulnerabilities, and a lifecycle-policy engine for image retention.
Role in hybrid ML platforms¶
ECR is the canonical shared image substrate for hybrid compute + serving ML platforms: the same Docker image, pushed once to ECR, is consumed by training jobs on SageMaker and by serving pods on EKS. One image → two substrates — this is what makes cross-platform base images distributable.
SOCI index storage¶
ECR is also where SOCI (Seekable OCI) indexes live. An SOCI index is computed once at push time and stored alongside the image in ECR; runtimes that support SOCI fetch the index first and stream image layers lazily. This is what powers concepts/lazy-container-image-loading — the 40–50% startup reduction Lyft saw for SageMaker Studio notebooks (Source: sources/2025-11-18-lyft-lyftlearn-evolution-rethinking-ml-platform-architecture).
Seen in¶
- sources/2025-11-18-lyft-lyftlearn-evolution-rethinking-ml-platform-architecture — ECR is the shared image registry that feeds both LyftLearn Compute (SageMaker) and LyftLearn Serving (EKS); one image trains and serves the same model.