ECR for container image registry in AWS - Time & Space Complexity

Time Complexity: ECR for container image registry

O(n)

Understanding Time Complexity

We want to understand how the time to push or pull container images to AWS ECR changes as the number of images grows.

How does the number of images affect the operations needed?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

aws ecr create-repository --repository-name my-app
aws ecr batch-check-layer-availability --repository-name my-app --layer-digests layer1 layer2
aws ecr put-image --repository-name my-app --image-tag v1 --image-manifest file://manifest.json
aws ecr list-images --repository-name my-app
aws ecr batch-delete-image --repository-name my-app --image-ids imageTag=v1
    

This sequence creates a repository, checks image layers, uploads an image, lists images, and deletes an image in ECR.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Uploading images with put-image and checking layers with batch-check-layer-availability.
• How many times: Once per image or image layer during push operations.

How Execution Grows With Input

As the number of images increases, the number of API calls to upload and check layers grows roughly in proportion.

Input Size (n)	Approx. API Calls/Operations
10	About 10 uploads and layer checks
100	About 100 uploads and layer checks
1000	About 1000 uploads and layer checks

Pattern observation: The operations grow linearly as the number of images increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to push or manage images grows directly with the number of images.

Common Mistake

[X] Wrong: "Uploading multiple images happens all at once, so time stays the same no matter how many images."

[OK] Correct: Each image requires separate API calls and data transfer, so time increases as images increase.

Interview Connect

Understanding how operations scale with input size helps you design efficient cloud workflows and explain your reasoning clearly in interviews.

Self-Check

"What if we batch multiple image uploads in one API call? How would the time complexity change?"

Practice

1. What is the primary purpose of AWS Elastic Container Registry (ECR)?

easy

A. To store and manage container images securely

B. To run containerized applications

C. To monitor AWS cloud resources

D. To provide virtual machines for deployment

Solution

1. Step 1: Understand ECR's role

   AWS ECR is designed to store container images safely and manage them.

2. Step 2: Differentiate from other services

   Running containers is done by ECS or EKS, not ECR. Monitoring and VMs are unrelated.

3. Final Answer:

   To store and manage container images securely -> Option A

4. Quick Check:

   ECR = Container image storage [OK]

Hint: ECR stores images, ECS/EKS run containers [OK]

Common Mistakes:

• Confusing ECR with ECS or EKS
• Thinking ECR runs containers
• Assuming ECR monitors resources

2. Which AWS CLI command correctly creates a new ECR repository named my-app?

easy

A. aws ecr make-repo --repository my-app

B. aws ecr new-repository --name my-app

C. aws ecr create-repository --repository-name my-app

D. aws ecr init-repository --repo my-app

Solution

1. Step 1: Recall AWS CLI syntax for ECR

   The correct command to create a repository is aws ecr create-repository --repository-name <name>.

2. Step 2: Check options for correctness

   Options B, C, and D use invalid commands or flags not recognized by AWS CLI.

3. Final Answer:

   aws ecr create-repository --repository-name my-app -> Option C

4. Quick Check:

   Create repo command = aws ecr create-repository --repository-name my-app [OK]

Hint: Use 'create-repository' with '--repository-name' flag [OK]

Common Mistakes:

• Using incorrect command verbs like 'new' or 'make'
• Wrong flag names like '--name' or '--repo'
• Assuming 'init-repository' is valid

3. Given this AWS CLI command output snippet after pushing an image to ECR, what does the imageScanStatus value IN_PROGRESS indicate?

{
  "imageId": {"imageTag": "v1"},
  "imageScanStatus": {"status": "IN_PROGRESS"}
}

medium

A. The image scan for vulnerabilities is currently running

B. The image scan has completed with no issues

C. The image push failed due to scan errors

D. The image is not scanned because scanning is disabled

Solution

1. Step 1: Understand imageScanStatus meaning

   The status IN_PROGRESS means the scan is currently running on the image.

2. Step 2: Eliminate other options

   Completed scans show COMPLETE, failures show FAILED, and disabled scanning shows no status.

3. Final Answer:

   The image scan for vulnerabilities is currently running -> Option A

4. Quick Check:

   IN_PROGRESS = scan running [OK]

Hint: IN_PROGRESS means scan is running, not done [OK]

Common Mistakes:

• Assuming IN_PROGRESS means scan passed
• Confusing scan failure with in-progress status
• Thinking scanning is disabled

4. You tried to push a container image to ECR but got an error: denied: Your authorization token has expired. What is the most likely fix?

medium

A. Restart the AWS CLI tool

B. Delete the repository and create a new one

C. Change the image tag and push again

D. Run aws ecr get-login-password again to refresh credentials

Solution

1. Step 1: Identify cause of authorization token error

   ECR login tokens expire after 12 hours, so pushing images requires fresh tokens.

2. Step 2: Refresh credentials properly

   Running aws ecr get-login-password and logging in again refreshes the token.

3. Final Answer:

   Run aws ecr get-login-password again to refresh credentials -> Option D

4. Quick Check:

   Expired token fix = refresh login [OK]

Hint: Refresh ECR login token before pushing images [OK]

Common Mistakes:

• Deleting repository unnecessarily
• Changing image tag won't fix auth
• Restarting CLI doesn't refresh token

5. You want to ensure that only images with specific tags can be overwritten in your ECR repository. Which ECR feature helps enforce this?

hard

A. VPC endpoints

B. Image tag immutability

C. Lifecycle policies

D. Cross-region replication

Solution

1. Step 1: Understand tag immutability

   Image tag immutability prevents overwriting images with the same tag, protecting specific versions.

2. Step 2: Differentiate from other features

   Lifecycle policies manage image cleanup, VPC endpoints control network access, replication copies images across regions.

3. Final Answer:

   Image tag immutability -> Option B

4. Quick Check:

   Prevent tag overwrite = immutability [OK]

Hint: Use tag immutability to block overwrites [OK]

Common Mistakes:

• Confusing lifecycle policies with immutability
• Thinking VPC endpoints control tags
• Assuming replication affects tag overwrite