1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
I tried creating an ACM certificate for "eu-central-1" using the following CloudFormation template.
However, I was unable to reproduce the same problem you experienced.
I have successfully created an SSL certificate for my AWS account.
It's possible this is a temporary issue, so how about trying again after some time?
If the error persists for more than a day, I recommend contacting AWS support.
Inquiries regarding "Account and billing" are free of charge.
https://console.aws.amazon.com/support
AWSTemplateFormatVersion: "2010-09-09"
Parameters:
record01:
Type: String
Description: domain name
hostedzoneid:
Type: String
Description: Route53 hostedzone id
Resources:
# ------------------------------------------------------------#
# ACM
# ------------------------------------------------------------#
ACM:
Type: AWS::CertificateManager::Certificate
Properties:
DomainName: !Ref record01
DomainValidationOptions:
- DomainName: !Ref record01
HostedZoneId: !Ref hostedzoneid
SubjectAlternativeNames:
- !Sub "*.${record01}"
ValidationMethod: DNS
Relevant content
asked 7 years ago
- AWS OFFICIALUpdated 2 years ago

Hello, I did contact support already. I was able to reproduce the problem multiple times and we believe it is region bound. I am in eu-central-1.
We can pinpoint the moment when a change was introduced in cloudformation:
Handler fingerprint (before/after) Before 2026-06-09 (old handler): no "Eventual consistency check initiated" stack event; certificates issued normally (e.g. 2026-06-08 16:18 UTC, stack idr-backend-dev-IDRRestApi, issued in ~2.5 min). From 2026-06-09 (new handler): "Eventual consistency check initiated" event appears immediately after "Resource creation Initiated"; the resource then fails exactly 31.0 +/- 0.1 s after that event, in every failure.
We have deployed many ACM certificates before this happened and we've seen consistent failures ever since.
I also deployed CloudFormation using the same region as you, "eu-central-1," but I haven't been able to reproduce the problem. By the way, is it possible to issue certificates via CloudFormation in other regions?