ECR repository should use KMS encryption
Medium
AWS
General
aws-ecr-repository-encryption
Applies to
AWS::ECR::Repository
What CGPulse checks
A resource passes this rule when encryptionType must equal KMS. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure KMS encryption for enhanced key management and audit capabilities. In AWS Console: ECR > Repositories > create repo with KMS encryption. See: https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html
Terraform
resource "aws_ecr_repository" "{name}" {
encryption_configuration {
encryption_type = "KMS"
kms_key = aws_kms_key.{name}.arn
}
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled