<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ansible on 🛠️ blog.yrhsk.work</title>
    <link>https://blog.yrhsk.work/tags/ansible/</link>
    <description>Recent content in Ansible on 🛠️ blog.yrhsk.work</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 27 Apr 2026 12:04:31 +0300</lastBuildDate>
    <atom:link href="https://blog.yrhsk.work/tags/ansible/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ansible on EC2 without SSH: connecting via AWS SSM Session Manager</title>
      <link>https://blog.yrhsk.work/posts/ansible-connection-via-aws-ssm/</link>
      <pubDate>Mon, 27 Apr 2026 12:04:31 +0300</pubDate>
      <guid>https://blog.yrhsk.work/posts/ansible-connection-via-aws-ssm/</guid>
      <description>&lt;p&gt;I really like using &lt;a href=&#34;https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html&#34;&gt;AWS SSM Session Manager&lt;/a&gt; for EC2 instances management whenever it&amp;rsquo;s possible, and recently faced a case where the requirement was to use Ansible for configuration management of EC2 instances, but without opening SSH access to them. That sounded like a good use case for SSM Session Manager, but I had to do some research to figure out how to make it work with Ansible.&lt;/p&gt;
&lt;p&gt;I ended up using two approaches - one with a static inventory for a single instance, and another with dynamic discovery for a fleet of instances. Both are based on the &lt;a href=&#34;https://docs.ansible.com/ansible/latest/collections/community/aws/aws_ssm_connection.html&#34;&gt;&lt;code&gt;community.aws.aws_ssm&lt;/code&gt;&lt;/a&gt; connection plugin, which uses SSM Session Manager under the hood to connect to the target instances without SSH. The main difference is how the inventory is built - either hardcoded with instance IDs or dynamically discovered via EC2 API queries.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
