Summary
In this chapter, we explored how we can use ECR to store, cache, and replicate container images. Using ECR comes at a cost, which is made up of the total size of all images in your repository and egress costs, but by using the scan-on-push capability of ECR we can identify and resolve critical dependencies as well as optimize the size of the image, supporting a better security posture and more cost-effective images.
There are also more advanced features of ECR that allow us to support a DR strategy or deploy applications across multiple regions using cross-region replication as well as caching public images from the ECR public repositories or Quay. Finally, we looked at how you can configure IAM and repository policies to control access to the images inside and pull those images into EKS.
In the next chapter, we will look at how you can use the AWS storage driver to provide stateful storage to Pods as a source of your applications and Pods.
