
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Ryan Todd</title>
      <link>https://ryantodd.dev/blog</link>
      <description>Notes on AI, operational automation, cloud infrastructure, and platform engineering.</description>
      <language>en-us</language>
      <managingEditor>rmtodd618@gmail.com (Ryan Todd)</managingEditor>
      <webMaster>rmtodd618@gmail.com (Ryan Todd)</webMaster>
      <lastBuildDate>Thu, 21 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://ryantodd.dev/tags/infrastructure-as-code/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://ryantodd.dev/blog/splitting-cloudformation-stack-500-resource-limit</guid>
    <title>Splitting a CloudFormation Stack at the 500-Resource Limit</title>
    <link>https://ryantodd.dev/blog/splitting-cloudformation-stack-500-resource-limit</link>
    <description>AWS gives you 500 resources per CloudFormation stack. That sounds like plenty until a Serverless Framework service grows past ~60 Lambdas. This is the playbook I wish I had: how to see the wall coming, where to draw service boundaries, and how to actually do the migration without an outage.</description>
    <pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
    <author>rmtodd618@gmail.com (Ryan Todd)</author>
    <category>aws</category><category>cloudformation</category><category>serverless-framework</category><category>infrastructure-as-code</category><category>platform-engineering</category>
  </item>

    </channel>
  </rss>
