<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS IAM on Support Tools</title><link>https://support.tools/tags/aws-iam/</link><description>Recent content in AWS IAM on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/aws-iam/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Actions Secrets: OIDC, Environments, SHA Pins</title><link>https://support.tools/post/enterprise-github-actions-security-secret-management-guide-2025/</link><pubDate>Sun, 25 May 2025 16:34:42 -0500</pubDate><guid>https://support.tools/post/enterprise-github-actions-security-secret-management-guide-2025/</guid><description>&lt;p&gt;Most GitHub Actions secret leaks are not clever. A long-lived AWS key sits in repository secrets for three years, a &lt;code&gt;pull_request_target&lt;/code&gt; workflow checks out a fork and runs its &lt;code&gt;npm install&lt;/code&gt; with that key in the environment, or a tag on a popular action gets repointed to malicious code. This guide fixes each of those with concrete workflow YAML, in the order that removes the most risk first.&lt;/p&gt;</description></item></channel></rss>