# Versent/saml2aws

CLI tool which enables you to login and retrieve AWS temporary credentials using a SAML IDP

Repository: https://github.com/Versent/saml2aws
Canonical: https://ross.abutalabs.com/products/saml2aws
Homepage: https://github.com/Versent/saml2aws
Language: Go
License: MIT
License Family: permissive
Topics: aws, saml, adfs, osx, windows, linux, macos, macosx
Last push: 2025-11-20T01:19:52+00:00

## Health v2 (maintenance only)
Score: 49/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 53, release rhythm 16, longevity 100
- inputs: {"age_days": 3643, "days_push": 287, "days_rel": 538, "gap_med": 143, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2241, forks 620 (observed 2026-08-28T04:06:29.785345+00:00)

## What it is
saml2aws is a Go CLI tool that authenticates against SAML-based identity providers such as ADFS and PingFederate and exchanges the SAML assertion with AWS STS to obtain temporary AWS credentials. It saves those credentials to an AWS profile so users can seamlessly use the AWS CLI and SDKs with federated single sign-on.

## Use cases
- log in to AWS CLI using my company's SAML single sign-on
- get temporary AWS credentials from ADFS
- authenticate AWS CLI with PingFederate
- assume an AWS role via SAML assertion from the command line
- avoid long-lived AWS access keys by using federated SSO credentials
- configure multiple AWS accounts behind one SAML identity provider
- use AWS CLI with corporate identity provider credentials

## When to choose
- your organization uses a SAML 2.0 identity provider like ADFS, PingFederate, or Okta for AWS access
- you want short-lived STS credentials instead of static IAM keys
- you need a scriptable, cross-platform CLI for federated AWS login
- you manage multiple AWS accounts and roles through one SSO flow

## When to avoid
- your organization uses AWS IAM Identity Center (AWS SSO) natively, where the built-in aws sso login is simpler
- you need OIDC/OAuth-based federation rather than SAML
- you want a GUI-based SSO experience rather than a terminal tool
- you don't use AWS

## Facets
- artifact type: cli-tool
- maturity: active
- function: auth, cli, security
- domain: cloud-computing, security, developer-tools
- platform: windows, cli, cross-platform
- tags: aws, saml, sso, adfs, pingfederate, sts, temporary-credentials, federated-identity, go, command-line, linux, macos

## Member repositories
- Versent/saml2aws (main) score 49

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:29.785345+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:44:06.021552+00:00, confidence not recorded.
  - readme: https://github.com/Versent/saml2aws (fetched 2026-08-28T04:06:29.785345+00:00, sha c9c303ce884b)
  - homepage: https://github.com/Versent/saml2aws (fetched 2026-08-29T10:24:21.261034+00:00, sha 84b53594745a)
- Data as of 2026-08-30T08:39:29.467469+00:00.