<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Route53 on FivexL. Cloud Engineering Specialists</title>
    <link>/tags/route53/</link>
    <description>Recent content in Route53 on FivexL. Cloud Engineering Specialists</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>info@fivexl.io (FivexL)</managingEditor>
    <webMaster>info@fivexl.io (FivexL)</webMaster>
    <lastBuildDate>Wed, 19 Feb 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/route53/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Unexpectedly Hard: Overcoming Pitfalls in aws_acm_certificate setup</title>
      <link>/blog/aws_acm_certificate/</link>
      <pubDate>Wed, 19 Feb 2025 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author>
      <guid>/blog/aws_acm_certificate/</guid>
      <description>Encountering the “Invalid for_each argument” and “UnsupportedCertificate” errors when configuring AWS ACM certificates via Terraform is surprisingly common. By removing dynamic for_each logic based on unknown attributes and using the aws_acm_certificate_validation resource to wait for certificate issuance, you can sidestep these pitfalls and ensure successful integration with resources like ELB listeners.</description>
    </item>
  </channel>
</rss>
