Ensure Route 53 alias records are used instead of CNAME where possible
Alias records provide better performance, are free of charge, and can be created at the zone apex (root domain), unlike CNAME records.
Security Impact
CNAME records add DNS lookup overhead and cannot be used at zone apex, limiting architectural options.
How to Remediate
Use alias records when pointing to AWS resources (CloudFront, ELB, S3, etc.). Reserve CNAME for external or non-AWS resources.
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 Amazon Route 53 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 AWS Best Practices compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-route53-11
- Service
- Amazon Route 53
- Category
- Best Practices
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Route 53 Checks
View all checksEnsure Route 53 hosted zones have query logging enabled
Ensure DNSSEC is enabled for Route 53 domains
Ensure Route 53 domains have auto-renewal enabled
Ensure Route 53 domains have transfer lock enabled
Ensure Route 53 domains have privacy protection enabled