EKS cluster must have envelope encryption for secrets
High
AWS
General
aws-eks-cluster-encryption
Applies to
AWS::EKS::Cluster
What CGPulse checks
A resource passes this rule when encryptionConfig must be set true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure a customer-managed KMS key for full control over encryption key lifecycle. In AWS Console: EKS > Clusters > create with KMS encryption. See: https://docs.aws.amazon.com/eks/latest/userguide/enable-kms.html
Terraform
resource "aws_eks_cluster" "{name}" {
encryption_config {
resources = ["secrets"]
provider {
key_arn = 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