<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux on Jesse Builds Software</title>
    <link>https://jessemcdowell.ca/tags/linux/</link>
    <description>Recent content in Linux on Jesse Builds Software</description>
    <generator>Hugo</generator>
    <language>en-CA</language>
    <lastBuildDate>Sat, 07 Mar 2026 11:03:30 -0800</lastBuildDate>
    <atom:link href="https://jessemcdowell.ca/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Copying Files to AWS ECS Fargate Instance via Base64</title>
      <link>https://jessemcdowell.ca/2026/01/copying-files-to-aws-ecs-fargate-instance-via-base64/</link>
      <pubDate>Sun, 04 Jan 2026 19:57:57 -0700</pubDate>
      <guid>https://jessemcdowell.ca/2026/01/copying-files-to-aws-ecs-fargate-instance-via-base64/</guid>
      <description>&lt;p&gt;I recently needed to copy a few small text files into a container running in AWS Fargate. I assumed it would be an easy matter of copying it through the terminal session, but that is, unfortunately, not the case.&lt;/p&gt;&#xA;&lt;p&gt;I was accessing the containers via the &lt;code&gt;aws ecs execute-command --interactive --comand &amp;quot;bash&amp;quot;&lt;/code&gt; mechanism. If you&amp;rsquo;re not familiar, this is a quick way to get a terminal inside an ECS container running in any cluster. It&amp;rsquo;s especially helpful when you have containers that do not receive incoming traffic from the internet. It is almost like SSH, but it is not exactly SSH. And one of the limitations is that there is no equivalent to &lt;code&gt;scp&lt;/code&gt;. There is also no ability to forward ports, so you can&amp;rsquo;t use it to access SSH either.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
