<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devops on How It Works</title>
    <link>https://backend.how/tags/devops/</link>
    <description>Recent content in Devops on How It Works</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>pg@backend.how (Pratik)</managingEditor>
    <webMaster>pg@backend.how (Pratik)</webMaster>
    <copyright>backend.how © 2026 by Pratik is licensed under CC BY-SA 4.0</copyright>
    <lastBuildDate>Fri, 09 Aug 2024 16:42:51 +0530</lastBuildDate>
    <atom:link href="https://backend.how/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>🔧 Lost SSH Access to Ec2 ?</title>
      <link>https://backend.how/posts/lost-ssh-access-to-ec2/</link>
      <pubDate>Fri, 09 Aug 2024 16:42:51 +0530</pubDate><author>pg@backend.how (Pratik)</author>
      <guid>https://backend.how/posts/lost-ssh-access-to-ec2/</guid>
      <description>&lt;p&gt;Losing SSH access to an Amazon EC2 instance can be a frustrating experience, especially when common solutions like EC2 Instance Connect or Session Manager are unavailable. In this blog post, we&amp;rsquo;ll explore a lesser-known but effective method to regain access by leveraging EC2 user data.&lt;/p&gt;&#xA;&lt;h1 id=&#34;why-this-method-works&#34;&gt; &#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#why-this-method-works&#34;&gt;&#xA;    &lt;span class=&#34;h-text&#34;&gt; Why This Method Works &lt;/span&gt; &#xA;    &lt;span class=&#34;pound&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&#xA;&lt;p&gt;EC2 user data is a feature that allows you to pass scripts or cloud-config directives to an instance at launch time. These scripts run with root privileges when the instance boots. By modifying the user data to include your SSH key, you can ensure that your key is added to the authorized_keys file of a specific user, granting you SSH access.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
