<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Prosyon Research</title><link>https://research.prosyon.ca/topics/security/</link><description>Recent content in Security on Prosyon Research</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://research.prosyon.ca/topics/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Two-Phase ACM Validation with External DNS</title><link>https://research.prosyon.ca/papers/external-dns-acm-flow/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate><guid>https://research.prosyon.ca/papers/external-dns-acm-flow/</guid><description>&lt;h2 id="the-deadlock"&gt;The deadlock&lt;/h2&gt;
&lt;p&gt;A CloudFront distribution with a custom domain needs an &lt;strong&gt;issued&lt;/strong&gt; ACM
certificate in &lt;code&gt;us-east-1&lt;/code&gt;. ACM issues a DNS-validated certificate only after a
specific &lt;code&gt;CNAME&lt;/code&gt; appears in the domain&amp;rsquo;s zone.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; When Terraform owns the
zone, it writes that record in the same apply. When the zone is &lt;strong&gt;external&lt;/strong&gt;,
Terraform cannot — and a single apply that both requests the certificate and
builds the distribution cannot complete, because:&lt;/p&gt;</description></item></channel></rss>