Message from CloudFormation about DNS zone mapping not using lazy: true
.
#31918
Labels
@aws-cdk/aws-cloudformation
Related to AWS CloudFormation
bug
This issue is a bug.
closed-for-staleness
This issue was automatically closed because it hadn't received any attention in a while.
needs-reproduction
This issue needs reproduction.
p2
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Describe the bug
Using this python class and these
parameters results in this
synthesized CloudFormation script.
The noteworthy parts are:
and
According to this CloudFormation user guide, alias records pointing to CloudFront distributions need to use
Z2FDTNDATAQYW2
as a hosted zone ID. From the variable naming I assume the mapping is included for a china specific workaround.The problem with this is that it leads to the following message from CloudFormation:
Normally it would be clear what to do, but as the affected code is auto-generated and not written by me, it is not possible for me to provide that flag.
Regression Issue
Last Known Working CDK Version
No response
Expected Behavior
I would either expect CDK to provide
lazy: true
or at least the message not to be shown. As there is nothing I can do to get rid of it the message is just spam and doesn't help me at all.Current Behavior
CloudFormation shows the message I quoted above and there is nothing that can be done about it.
Reproduction Steps
Create two stacks in different regions. Once defining a CloudFront distribution and the other defining a route53 alias record pointing to that distribution.
Possible Solution
It should be evaluated whether providing the
lazy: true
option would have any negative side effects and if not, it should just be added.If it's not possible to add this, a more sophisticated approach might be needed.
Additional Information/Context
No response
CDK CLI Version
2.164.1 (build bb9275c)
Framework Version
No response
Node.js Version
v20.5.1
OS
Ubuntu 24.04 LTS
Language
Python
Language Version
Does not apply
Other information
No response
The text was updated successfully, but these errors were encountered: