<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lambda-Microvms on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/lambda-microvms/</link><description>Recent content in Lambda-Microvms on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 16 Sep 2026 15:13:50 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/lambda-microvms/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Step Functions auto-adds SDK integrations for new services at launch</title><link>https://curadevops.metacog.co.kr/insights/2026-09-16-aws-step-functions-adds-new-aws-service-integrations-automat/</link><pubDate>Wed, 16 Sep 2026 15:13:50 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-16-aws-step-functions-adds-new-aws-service-integrations-automat/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AWS is closing the gap between service launch and orchestration availability automatically, which is relevant context when evaluating Step Functions as the org&amp;rsquo;s standard workflow orchestration layer; no strategic decision is forced here, but it reduces a prior limitation worth knowing about.&lt;/li>
&lt;/ul></description></item></channel></rss>