Ensure ECR repositories do not allow public access
Private ECR repositories should not have public access enabled.
Security Impact
Public repositories expose container images to anyone.
How to Remediate
Use ECR Public for intentionally public images. Keep private repositories private.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Elastic Container Registry (ECR) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ecr-6
- Service
- Elastic Container Registry (ECR)
- Category
- Public Access
- Severity
- CRITICAL
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Elastic Container Registry (ECR) Checks
View all checksEnsure ECR repositories have image scanning enabled
Ensure ECR repositories have image immutability enabled
Ensure ECR repositories are encrypted with KMS CMK
Ensure ECR repositories have lifecycle policies
Ensure ECR repository policies are restrictive