ACM Certificate Validation Hardening

What this rule checks

Detects ACM certificates using email validation or with certificate transparency logging disabled.

How to fix it

1. 1Use DNS validation for automated certificate renewal
2. 2Enable certificate transparency logging to detect misissuance

import * as acm from 'aws-cdk-lib/aws-certificatemanager';

new acm.Certificate(this, 'Cert', { domainName: 'example.com' });

import * as acm from 'aws-cdk-lib/aws-certificatemanager';

new acm.Certificate(this, 'Cert', {
  domainName: 'example.com',
  validation: acm.CertificateValidation.fromDns(),
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

Intentional? Suppress this finding

Sometimes a flag is deliberate — a genuinely public endpoint, say. You can dismiss acm-certificate-email-validation and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "acm-certificate-email-validation", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::acm-certificate-email-validation',
  reason: 'Why this is intentional',
});

Use the rule ID acm-certificate-email-validation shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →