Other Articles
- IAM - Enable User MFA
- IAM - Enforce Key Rotation
- IAM - Enforce Active Key Limit
- IAM - Disable Unused User Credentials
- IAM - Enforce Group Permission
- IAM - Enforce Password Length
- IAM - Prohibit Password Reuse
- IAM - Check Root Access Keys Existence
- IAM - Enable Root MFA
- IAM - Establish Support Role
- IAM - Enable Key Rotation
- Purge Expired Certificates
- EC2 Volume – Enable EBS Volume Backup
- EC2 Volume – Enable EBS Encryption
- EFS – Enable EFS Storage Backup
- S3 Bucket – Enable S3 Bucket Versioning
- S3 Bucket – Enable S3 Bucket Encryption
- S3 Bucket – Block S3 Bucket Public Access
- RDS DB Instance – Encryption of Storage
- RDS DB Instance – Enable Deletion Protection
- RDS DB Instance – Enable Auto Minor Version Upgrade
- DynamoDB Table – Enable Table Encryption
- DynamoDB Table – Enable Table Point In Time Recovery
- DynamoDB Table – Enable Table Deletion Protection
- OpenSearch Domain – Enable Encryption at Rest
- RDS DB Cluster – Retain Backups for 7 Days
- RDS DB Cluster – Encryption of Storage
- RDS DB Cluster – Enable Deletion Protection
- EC2 Instance – Monitor CPU Utilization
- ECS Service – Monitor CPU Utilization
- ECS Service – Monitor Memory Utilization
- RDS DB Instance – Monitor Free Storage Space
- RDS DB Instance – Monitor CPU Utilization
- SQS Queue – Monitor Message Age
- SQS Queue – Monitor Message Visibility
- DynamoDB Table – Monitor Table Read Capacity
- DynamoDB Table – Monitor Table Write Capacity
- DynamoDB Table – Monitor Table Latency
- Enable CloudTrail
- Encrypt CloudTrail Logs
- EC2 VPC – Ensure Flow Logs are Enabled
- EKS Cluster – Enable Control Plane Logging
- CloudWatch Log Group – Enable KMS Encryption
- CloudWatch Log Group – Configure Retention
- Load Balancer – Enable Access Logs
- RDS DB Instance – Block Public Access
- EC2 Security Group – Restrict Public SSH and RDP Access
- EC2 Security Group – Restrict Public Database Access
- EKS Cluster – Restrict Public Endpoint
- EC2 VPC – Restrict Default Security Group Traffic
- Load Balancer – Redirect HTTP Traffic to HTTPS
- Load Balancer – Use Strong TLS Policies
- OpenSearch Domain – Enable Node-to-Node Encryption
- OpenSearch Domain – Enforce HTTPS
- OpenSearch Domain – Restrict Public Access
- RDS DB Cluster – Block Public Access
- EC2 Instance – Enable Deletion Protection
- ECS Service – Enable Auto Scaling
- Load Balancer – Enable Deletion Protection
- Enable AWS Security Hub
- Enable GuardDuty
- CloudFront Distribution – Enforce HTTPS for Viewers
- CloudFront Distribution – Require TLS 1.2 for Viewers
- CloudFront Distribution – Associate a WAF Web ACL
- CloudFront Distribution – Protect S3 Origin Access
- KMS Key – Avoid Pending Deletion
- SNS Topic – Enable Encryption
- SNS Topic – Restrict Topic Policy Access
EKS Cluster – Enable Secrets Encryption
Secure Configuration Checks > AWS
This check ensures that the Kubernetes secrets of an Amazon EKS cluster are encrypted with an AWS KMS key. Secrets often hold passwords, tokens and certificates. Envelope encryption with a key that you control adds a second layer of protection for this data at rest.
Check Details
- Resource: EKS Cluster
- Check: Enable EKS cluster secrets encryption (
SecretsEncryptionEnabled) - Risk: Anyone who gets access to the cluster data store or its backups can read the secrets in clear text
Remediation via AWS Console
-
Open the Amazon EKS console and select the affected cluster.
-
Open the Configuration tab. Under Cluster configuration, click Manage.
-
Open Envelope encryption and verify that the encryption key is set to AWS owned.
-
If your security policy requires a customer-managed KMS key, configure the required key.
-
Repeat for every affected cluster.
Note: Kubernetes 1.28 and later automatically use envelope encryption with an AWS-owned KMS key. No manual configuration is required unless a customer-managed key is mandated by your security policy.
Remediation via AWS CLI
-
Log in to the AWS Management Console and click the CloudShell icon (
>_) in the top-right corner.
-
List the clusters that do not encrypt secrets:
for c in $(aws eks list-clusters --query 'clusters[]' --output text); do aws eks describe-cluster --name "$c" --output json | \ jq -r '.cluster | select(([.encryptionConfig[]? | select(.resources | index("secrets"))] | length) == 0) | .name' doneThe command covers one region. Add
--region <region>to eachawscommand to check another. -
If you do not have a KMS key yet, create a symmetric key and note its ARN. Skip this step if you already have one:
aws kms create-key \ --description "EKS secrets encryption" \ --query 'KeyMetadata.[KeyId,Arn]' \ --output text aws kms enable-key-rotation --key-id <kms-key-id>
-
Enable secrets encryption on the cluster:
aws eks associate-encryption-config \ --cluster-name <cluster-name> \ --encryption-config '[{"resources":["secrets"],"provider":{"keyArn":"<kms-key-arn>"}}]'Wait for the update to finish:
aws eks wait cluster-active --name <cluster-name>
-
Verify the encryption configuration:
aws eks describe-cluster \ --name <cluster-name> \ --query 'cluster.encryptionConfig'
Replace <cluster-name> with the name of the cluster, for example prod-cluster.
Replace <kms-key-id> and <kms-key-arn> with the ID and ARN of your key, for example arn:aws:kms:us-east-1:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab.
Repeat steps 4 and 5 for each cluster.
Updated on 03 November, 2026