Now proactively manage your ECR API use with CloudWatch Metrics and Service Quotas

Posted on: Mar 4, 2020

Amazon Elastic Container Registry (ECR) today introduced three new enhancements that help you see and proactively manage API usage when pushing and pulling container images. First, you now get up-to-the minute API metrics in Amazon CloudWatch Usage Metrics for the number of times you push and pull images, giving you the operational visibility you need. Second, you can now view approved account-level API quotas (also known as limits) using AWS Service Quotas, making it easier to see and request quota increases from the same place. Third, these new API metrics are automatically tracked against your quotas so you can trend and alarm as usage approaches limits, helping you manage utilization and identify anomalous activity. 

With AWS Service Quotas, you can easily view and manage quotas as your container workloads grow. ECR API quotas are the maximum number of sustained ECR commands you can make per second. You can view default and your approved per-account ECR quotas, and more easily request increases using Service Quotas in your account. To learn more, visit Service Quotas documentation

CloudWatch collects ECR API metrics such as BatchGetImage counts which equates to the number of images pulled. Each such API metric lets you see the rate at which you use these ECR commands to push and pull images. These metrics are also integrated with your API quotas, automatically tracking usage and helping you proactively manage utilization. You can learn more by reading CloudWatch Usage Metrics documentation

With API usage in CloudWatch and metrics integrated with per-account quotas, ECR gives you the observability you need to easily and proactively manage API operations when running container workloads on AWS. These new enhancements are available where ECR, CloudWatch Metrics and Service Quotas are available, consult the AWS Region table for more details. To learn more about these new ECR monitoring capabilities, visit our documentation page.