<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Ssm on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/aws-ssm/</link><description>Recent content in Aws-Ssm on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 10 Sep 2026 14:43:05 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/aws-ssm/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Systems Manager expands EC2 unmanaged-instance diagnosis categories</title><link>https://curadevops.metacog.co.kr/insights/2026-09-10-aws-systems-manager-now-diagnoses-more-issues-that-cause-ec2/</link><pubDate>Thu, 10 Sep 2026 14:43:05 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-10-aws-systems-manager-now-diagnoses-more-issues-that-cause-ec2/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> SSM now surfaces six additional root-cause categories (IAM, agent version, OS config, etc.) for unmanaged EC2 instances, reducing time-to-resolution for fleet onboarding issues. No migration or deadline; worth noting for teams that struggle to diagnose why instances fall out of SSM management.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>