<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssm on ferkakta.dev</title><link>https://ferkakta.dev/tags/ssm/</link><description>Recent content in Ssm on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Thu, 12 Feb 2026 10:00:00 -0600</lastBuildDate><atom:link href="https://ferkakta.dev/tags/ssm/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon WorkSpaces are invisible to SSM and CloudWatch (and how to fix it)</title><link>https://ferkakta.dev/workspaces-ssm-cloudwatch-bootstrap/</link><pubDate>Thu, 12 Feb 2026 10:00:00 -0600</pubDate><guid>https://ferkakta.dev/workspaces-ssm-cloudwatch-bootstrap/</guid><description>&lt;p&gt;I spent an afternoon arguing with Windows about whether I was allowed to be root on a machine I created. Six hours and six layers of undocumented workarounds later, I got CMMC-compliant audit logging on a desktop that doesn&amp;rsquo;t know it exists.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;
&lt;p&gt;WorkSpaces don&amp;rsquo;t show up in AWS Systems Manager. They&amp;rsquo;re not EC2 instances — no instance profile, no metadata endpoint, no identity. SSM Agent is pre-installed but thinks it&amp;rsquo;s nobody. CloudWatch Agent has no credentials and doesn&amp;rsquo;t know what region it&amp;rsquo;s in.&lt;/p&gt;</description></item></channel></rss>