ECR document

README.md

@@ -47,7 +47,7 @@ Following are some highlights of Kraken:
 - **Highly available**. No component is a single point of failure.
 - **Secure**. Support uploader authentication and data integrity protection through TLS.
 - **Pluggable storage options**. Instead of managing data, Kraken plugs into reliable blob storage
-  options, like S3, GCS, HDFS or another registry. The storage interface is simple and new options
+  options, like S3, GCS, ECR, HDFS or another registry. The storage interface is simple and new options
   are easy to add.
 - **Lossless cross cluster replication**. Kraken supports rule-based async replication between
   clusters.
@@ -79,7 +79,7 @@ talk](https://www.youtube.com/watch?v=waVtYYSXkXU) at KubeCon + CloudNativeCon.
   - Connects to peers returned by tracker to download content
 - Origin
   - Dedicated seeders
-  - Stores blobs as files on disk backed by pluggable storage (e.g. S3, GCS)
+  - Stores blobs as files on disk backed by pluggable storage (e.g. S3, GCS, ECR)
   - Forms a self-healing hash ring to distribute load
 - Tracker
   - Tracks which peers have what content (both in-progress and completed)
@@ -92,7 +92,7 @@ talk](https://www.youtube.com/watch?v=waVtYYSXkXU) at KubeCon + CloudNativeCon.
   - Mapping of human readable tag to blob digest
   - No consistency guarantees: client should use unique tags
   - Powers image replication between clusters (simple duplicated queues with retry)
-  - Stores tags as files on disk backed by pluggable storage (e.g. S3, GCS)
+  - Stores tags as files on disk backed by pluggable storage (e.g. S3, GCS, ECR)
 
 # Benchmark
 

docs/CONFIGURATION.md

@@ -180,7 +180,7 @@ As shown in this example, if 3 announce requests to one tracker fail with networ
 
 # Configuring Storage Backend For Origin And Build-Index
 
-Storage backends are used by Origin and Build-Index for data persistence. Kraken has support for S3, GCS, HDFS, http (readonly), and Docker Registry (readonly) as [backends](https://github.com/uber/kraken/tree/master/lib/backend).
+Storage backends are used by Origin and Build-Index for data persistence. Kraken has support for S3, GCS, ECR, HDFS, http (readonly), and Docker Registry (readonly) as [backends](https://github.com/uber/kraken/tree/master/lib/backend).
 
 Multiple backends can be used at the name time, configured based on namespaces of requested blob and tag  (for docker images, that means the part of image name before ":").
 
@@ -203,6 +203,12 @@ Example origin config that uses multiple backends:
 >        download_url: http://test-domain:9000/download?sha256=%s
 >        download_backoff:
 >          enabled: true
+> - namespace: ecr-images/.*
+>   backend:
+>     registry_tag:
+>       address: 123456789012.dkr.ecr.<region>.amazonaws.com
+>       security:
+>         credsStore: 'ecr-login'
 > - namespace: s3-images/.*
 >   backend:
 >     s3: