<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Announcements on 61418</title><link>https://61418.io/announcements/</link><description>Recent content in Announcements on 61418</description><generator>Hugo</generator><language>en-us</language><copyright>© Copyright 2026, 61418</copyright><lastBuildDate>Thu, 28 May 2026 15:25:08 -0400</lastBuildDate><atom:link href="https://61418.io/announcements/index.xml" rel="self" type="application/rss+xml"/><item><title>elhaz will be featured during fwd:cloudsec North America 2026 conference</title><link>https://61418.io/announcements/fwd-cloud-sec/</link><pubDate>Thu, 28 May 2026 15:25:08 -0400</pubDate><guid>https://61418.io/announcements/fwd-cloud-sec/</guid><description>&lt;p&gt;&lt;a href="https://www.linkedin.com/in/alex-smolen-8a59a31/"&gt;Alex Smolen&lt;/a&gt; will be &lt;a href="https://pretalx.com/fwd-cloudsec-2026/talk/9LRLDS/"&gt;presenting&lt;/a&gt; at fwd:cloudsec North America 2026 in Bellevue, Washington on June 1st. Notably, Alex&amp;rsquo;s presentation will feature &lt;a href="https://github.com/61418/elhaz"&gt;elhaz&lt;/a&gt; as he walks the audience through local AI-sandboxing.&lt;/p&gt;
&lt;p&gt;Big thanks to Alex for featuring 61418&amp;rsquo;s work!&lt;/p&gt;
&lt;p&gt;61418 will be attending fwd:cloudsec North America 2026. Come and say hello!&lt;/p&gt;</description></item><item><title>elhaz featured in the latest TL;DR Sec newsletter</title><link>https://61418.io/announcements/elhaz-tldr-sec/</link><pubDate>Sat, 09 May 2026 20:01:26 -0400</pubDate><guid>https://61418.io/announcements/elhaz-tldr-sec/</guid><description>&lt;p&gt;&lt;a href="https://github.com/61418/elhaz"&gt;elhaz&lt;/a&gt; appeared in the latest &lt;a href="https://tldrsec.com/p/tldr-sec-327"&gt;TL;DR Sec newsletter&lt;/a&gt; on May 7th, 2026.&lt;/p&gt;
&lt;p&gt;This is the second time that a project maintained by 61418 has been featured in TL;DR Sec, the first time being boto3-refresh-session on &lt;a href="https://tldrsec.com/p/tldr-sec-282"&gt;June 5th, 2025&amp;rsquo;s newsletter&lt;/a&gt;. For that, we want to thank Clint Gibler for bringing attention to 61418&amp;rsquo;s projects, as well as Alex Smolen for his research into agent-credential isolation using elhaz.&lt;/p&gt;</description></item><item><title>elhaz featured in EngSecLab's blog for securely sandboxing AI agents</title><link>https://61418.io/announcements/elhaz-eng-sec-labs/</link><pubDate>Mon, 27 Apr 2026 22:58:57 -0400</pubDate><guid>https://61418.io/announcements/elhaz-eng-sec-labs/</guid><description>&lt;p&gt;&lt;a href="https://alexsmolen.com/"&gt;Alex Smolen&lt;/a&gt; of &lt;a href="https://engseclabs.com"&gt;EngSecLabs&lt;/a&gt; released a wonderful &lt;a href="https://engseclabs.com/blog/agent-credential-isolation/"&gt;blog post&lt;/a&gt; earlier today that is absolutely worth reading.&lt;/p&gt;
&lt;p&gt;There has been &lt;em&gt;a lot&lt;/em&gt; of discussion lately among security professionals about how to isolate AI agents from AWS credentials. In the above-linked blog post, Alex&amp;rsquo;s solution is to cleverly mount a Docker container with the Unix socket maintained by elhaz, install elhaz and the AWS CLI inside of that container, and create an AWS profile with a credential process which ingests temporary credentials emitted by the &lt;a href="https://61418.io/elhaz/cli/elhaz-export.html"&gt;elhaz export&lt;/a&gt; command. Alex&amp;rsquo;s technique places firm policy + identity guardrails around any agent sandboxed by that container, effectively treating elhaz as a credential proxy. In the post, Alex also mentions a tool named &lt;a href="https://github.com/engseclabs/trailtool"&gt;TrailTool&lt;/a&gt;, which he maintains, which he uses to actively monitor AWS actions by agents and institute an intent-based approach to permissioning.&lt;/p&gt;</description></item><item><title>boto3-refresh-session influenced new features in AWS CLI v2</title><link>https://61418.io/announcements/brs-influences-aws-cli/</link><pubDate>Mon, 13 Apr 2026 13:33:54 -0400</pubDate><guid>https://61418.io/announcements/brs-influences-aws-cli/</guid><description>&lt;p&gt;In September 2025, AWS released &lt;a href="https://github.com/aws/aws-cli/blob/5bffffcc1bd0aa0e73bdcc1cfe432b37563a58bb/CHANGELOG.rst#L2081"&gt;v2.30.3&lt;/a&gt; of AWS CLI v2, which is the developer version of the AWS CLI.&lt;/p&gt;
&lt;p&gt;Among many new features included in v2.30.3, the aws configure command was updated in two different ways:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The creation of a mfa-login command&lt;/li&gt;
&lt;li&gt;The introduction of a aws_session_token parameter&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://github.com/61418/boto3-refresh-session"&gt;boto3-refresh-session&lt;/a&gt;, among other projects maintained by different open source maintainers focused on AWS credentials and identity, influenced the creation of those new features. These features improve the experience of working with temporary credentials and OTP&amp;rsquo;s locally.&lt;/p&gt;</description></item><item><title>elhaz has been added to 61418's catalog</title><link>https://61418.io/announcements/elhaz/</link><pubDate>Sun, 22 Mar 2026 09:21:15 -0400</pubDate><guid>https://61418.io/announcements/elhaz/</guid><description>&lt;p&gt;&lt;a href="https://github.com/61418/elhaz"&gt;elhaz&lt;/a&gt; was written by &lt;a href="https://github.com/michaelthomasletts"&gt;Mike Letts&lt;/a&gt; and officially released by 61418 on March 22nd, 2026.&lt;/p&gt;
&lt;p&gt;elhaz is a local AWS credential broker daemon exposed over a Unix socket.&lt;/p&gt;
&lt;p&gt;Instead of a locally hosted HTTP metadata emulation service (ECS), which requires multiple processes for each assumed RoleArn, elhaz runs a single process (which accepts multiple concurrent connections) and serves automatically refreshed temporary AWS credentials on demand.&lt;/p&gt;
&lt;p&gt;It caches AWS sessions for however long the daemon is kept alive, which eliminates redundant session initializations and STS calls.&lt;/p&gt;</description></item><item><title>61418's application for a PyPI organization was approved</title><link>https://61418.io/announcements/pypi-org-approved/</link><pubDate>Sun, 15 Mar 2026 09:20:15 -0400</pubDate><guid>https://61418.io/announcements/pypi-org-approved/</guid><description>&lt;p&gt;We are proud to announce 61418&amp;rsquo;s application for an &lt;a href="https://pypi.org/org/61418/"&gt;organization&lt;/a&gt; on PyPI was approved.&lt;/p&gt;
&lt;p&gt;Going forward, all projects maintained by 61418 will be owned and stored by 61418&amp;rsquo;s organization on PyPI instead of individual user accounts.&lt;/p&gt;</description></item><item><title>boto3-refresh-session has been transferred to 61418</title><link>https://61418.io/announcements/boto3-refresh-session/</link><pubDate>Fri, 06 Mar 2026 05:20:11 -0500</pubDate><guid>https://61418.io/announcements/boto3-refresh-session/</guid><description>&lt;p&gt;&lt;a href="https://github.com/61418/boto3-refresh-session"&gt;boto3-refresh-session&lt;/a&gt; was written by &lt;a href="https://github.com/michaelthomasletts"&gt;Mike Letts&lt;/a&gt; in February 2025, and it was transferred to 61418&amp;rsquo;s catalog on March 6th, 2026.&lt;/p&gt;
&lt;p&gt;Since releasing, boto3-refresh-session has been downloaded approximately 185K times on PyPI, adopted and used by large companies like Netflix (at an enterprise scale), and featured in &lt;a href="https://github.com/61418/boto3-refresh-session#:~:text=Featured%20in%20TL%3BDR%20Sec"&gt;TL;DR Sec&lt;/a&gt; and &lt;a href="https://github.com/61418/boto3-refresh-session?tab=readme-ov-file#:~:text=Featured%20in%20CloudSecList"&gt;CloudSecList&lt;/a&gt;. Notably, boto3-refresh-session also uses &lt;a href="https://github.com/61418/boto3-client-cache"&gt;boto3-client-cache&lt;/a&gt; as a dependency.&lt;/p&gt;
&lt;p&gt;boto3-refresh-session fills a niche but underserved need in the AWS ecosystem, specifically for developers using the AWS Python SDK (boto3). Although boto3 automatically refreshes temporary AWS credentials when authenticated using an AWS profile, this is not so in serverless environments where AWS profiles are untenable and/or impractical, among various other scenarios. Not every developer runs into this problem; however, those who have run into this problem historically were forced to refresh temporary credentials themselves. boto3-refresh-session standardizes an out-of-the-box solution to this gap. More, by leveraging boto3-client-cache, developers managing multiple sessions and many different clients/resources can also worry less about memory management due to duplicative client/resource objects and slow initialization times.&lt;/p&gt;</description></item><item><title>boto3-client-cache has been transferred to 61418</title><link>https://61418.io/announcements/boto3-client-cache/</link><pubDate>Mon, 02 Mar 2026 03:08:26 -0500</pubDate><guid>https://61418.io/announcements/boto3-client-cache/</guid><description>&lt;p&gt;61418 is proud to announce its first project to enter the catalog: &lt;a href="https://pypi.org/project/boto3-client-cache/"&gt;boto3-client-cache&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;boto3-client-cache is a concurrency-safe, bounded cache for boto3 clients and resources with deterministic identity semantics and support for LRU and LFU eviction policies.
It was created by &lt;a href="https://github.com/michaelthomasletts"&gt;Mike Letts&lt;/a&gt; and officially transferred to 61418 in late February 2026.
It is also a core dependency for &lt;a href="https://pypi.org/project/boto3-refresh-session/"&gt;boto3-refresh-session&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This project was added to 61418&amp;rsquo;s catalogue because it brings clear value to everyone using the AWS Python SDK (boto3) due to the lack of native client and resource caching in boto3 (as mentioned below).&lt;/p&gt;</description></item><item><title>boto3-refresh-session featured in the latest TL;DR Sec newsletter</title><link>https://61418.io/announcements/boto3-refresh-session-tldr-sec/</link><pubDate>Thu, 05 Jun 2025 20:09:52 -0400</pubDate><guid>https://61418.io/announcements/boto3-refresh-session-tldr-sec/</guid><description>&lt;p&gt;&lt;a href="https://github.com/61418/boto3-refresh-session"&gt;boto3-refresh-session&lt;/a&gt; appeared in the latest &lt;a href="https://tldrsec.com/p/tldr-sec-282"&gt;TL;DR Sec newsletter&lt;/a&gt; on June 5th, 2025.&lt;/p&gt;
&lt;p&gt;Thank you for featuring 61418&amp;rsquo;s work, Clint Gibler!&lt;/p&gt;</description></item><item><title>boto3-refresh-session featured in the latest CloudSecList newsletter</title><link>https://61418.io/announcements/boto3-refresh-session-cloudseclist/</link><pubDate>Sun, 01 Jun 2025 20:09:52 -0400</pubDate><guid>https://61418.io/announcements/boto3-refresh-session-cloudseclist/</guid><description>&lt;p&gt;&lt;a href="https://github.com/61418/boto3-refresh-session"&gt;boto3-refresh-session&lt;/a&gt; appeared in the latest &lt;a href="https://cloudseclist.com/issues/issue-290/"&gt;CloudSecList newsletter&lt;/a&gt; on June 1st, 2025.&lt;/p&gt;
&lt;p&gt;Thank you for featuring 61418&amp;rsquo;s work, Marco Lancini!&lt;/p&gt;</description></item></channel></rss>