HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
saml-to
assume-aws-role-action
TypeScript2022–2022
saml-to / assume-aws-role-action

assume-aws-role-action

Assume AWS IAM Roles using SAML.to in GitHub Actions

2Distinct people
3Mentions
0Explicit recommenders
182GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Assume AWS IAM Roles using SAML.to in GitHub Actions

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2022-01-18 19:50:19 UTC to 2022-01-18 21:58:14 UTC.

0122022-01-18 19:00:00 UTC to 2022-01-18 20:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 18, 19:002022-01-18 20:00:00 UTC to 2022-01-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 18, 20:002022-01-18 21:00:00 UTC to 2022-01-18 22:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 18, 21:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 18, 19:002022-01-18 19:00:00 UTC2022-01-18 20:00:00 UTC110
Jan 18, 20:002022-01-18 20:00:00 UTC2022-01-18 21:00:00 UTC000
Jan 18, 21:002022-01-18 21:00:00 UTC2022-01-18 22:00:00 UTC202

What Hacker News says

3 sources
Some observations: * it seems your package.json is still from an old iteration: https://github.com/saml-to/assume-aws-role-action/blob/main/... * it was super opaque where this relative import comes from: https://github.com/saml-to/assume-aws-role-action/blob/main/... but after some sniffing around, it seems to be some openapi generation magick https://github.com/saml-to/assume-aws-role-action/blob/main/... against one of your own API endpoints https://github.com/saml-to/assume-aws-role-action/blob/main/... which seems to mean that using this toy is not "self contained" in the way that `sts:AssumeRoleWithWebIdentity` is
In Show HN: Stop Putting AWS Credentials in GitHub Secrets
Hey orf! You are correct this GitHub action is at its core is very similar! Even though the initial instructions don't prescribe it, the biggest differentiator is that SAML.to supports a centralized permissions configuration across all repositories for a user, project or organization: https://github.com/saml-to/assume-aws-role-action/blob/main/... Also, this action is the tip of the iceberg of what SAML.to aims to provide (check out https://saml.to), for example: - Store Role Assumption and Privileges as Code (the saml-to.yml config file) - A command line interface to login and assume roles - Free (or affordable) for small teams or individuals - Additional Automations, Webhooks, SCIM, etc Let me know if you have any comments on this and thanks for the question!
In Show HN: Stop Putting AWS Credentials in GitHub Secrets
cnuss·Jan 18, 2022Submission

Show HN: Stop Putting AWS Credentials in GitHub Secrets

Greetings! I've created a GitHub action that works that allows GitHub Actions to exchange a GitHub token for AWS Access Credentials. I've cultivated a few examples of it in action: https://github.com/saml-to/aws-assume-role-action-examples I've always found management of AWS Credentials has been a pain. So this setting up this Action works like this: 1) A SAML Identity Provider is created in AWS 2) A Role in AWS is set up to trust that Identity Provider 3) A config file is added to the repository indicating which role can be assumed 4) The GitHub Action exchanges the Repo Secret for AWS Credentials using the SAML.to backend for the exchange Let me know what you think! I'm Happy to take questions and comments here or on Gitter: https://gitter.im/saml-to/assume-aws-role-action
88 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.