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
- EKS Cluster – Enable Secrets Encryption
- 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 – 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
CloudFront Distribution – Require TLS 1.2 for Viewers
Secure Configuration Checks > AWS
This check ensures that CloudFront viewers connect using TLS 1.2 or newer. Older protocol versions have known weaknesses and should not be accepted.
Check Details
- Resource: CloudFront Distribution
- Check: Require TLS 1.2 for CloudFront viewers (
MinimumViewerTLS) - Risk: Weak protocol versions can be attacked to expose traffic
Remediation via AWS Console
-
Log in to the AWS Management Console and open the Amazon CloudFront console.
-
Navigate to Distributions in the left navigation pane and select the affected distribution.
-
Open the General tab, locate the Settings section, and click Edit.
-
Check the Custom SSL certificate configuration:
- If a custom SSL/TLS certificate is configured and Clients that Support Server Name Indication (SNI) is selected, locate Security policy (minimum SSL/TLS version) and select TLSv1.2_2025 or TLSv1.3_2025. You can also select TLSv1.2_2021 if required by your security policy.
- If the distribution uses the default CloudFront certificate (*.cloudfront.net), the security policy is automatically set to TLSv1, and you cannot change it manually. To use a newer security policy, configure an alternate domain name and associate a custom SSL/TLS certificate issued through AWS Certificate Manager (ACM) in the region. Then configure the certificate to use SNI.
-
Click Save changes and wait for the distribution deployment to complete.
-
Verify that the updated security policy is applied to the distribution.
Note: Distributions using the default CloudFront certificate cannot be configured with a newer minimum TLS security policy. A custom SSL/TLS certificate with SNI support is required. Distributions using legacy client support with dedicated IP addresses must be reviewed for compatibility, as newer TLS security policies may not be available with that configuration.
Remediation via AWS CLI
-
Log in to the AWS Management Console and click the CloudShell icon (
>_) in the top-right corner.
-
Download the current distribution configuration:
aws cloudfront get-distribution-config \ --id <distribution-id> > dist-config.json
-
Confirm that the distribution uses a custom certificate:
jq '.DistributionConfig.ViewerCertificate' dist-config.json
If
CloudFrontDefaultCertificateistrue, add a custom certificate first. -
Set the minimum protocol version:
ETAG=$(jq -r '.ETag' dist-config.json) jq '.DistributionConfig | .ViewerCertificate.MinimumProtocolVersion = "TLSv1.2_2021"' \ dist-config.json > updated-config.json
-
Apply the updated configuration:
aws cloudfront update-distribution \ --id <distribution-id> \ --if-match "$ETAG" \ --distribution-config file://updated-config.json
-
Verify the new minimum protocol version:
aws cloudfront get-distribution-config \ --id <distribution-id> \ --query 'DistributionConfig.ViewerCertificate.MinimumProtocolVersion'
Replace <distribution-id> with your distribution ID, for example E1ABCDEF234567.
CloudFront is global, so CloudShell works in any region.
Updated on 03 November, 2026