gimme-aws-creds

What it is and what it does

gimme-aws-creds is a command-line tool that bridges Okta identity management and AWS credential provisioning. It authenticates you to Okta using your username, password, and optional MFA token, then uses SAML to request temporary AWS credentials from AWS STS. The tool handles the complexity of SAML assertion exchange and lets you select which Okta AWS application and role to assume—useful when your organization has multiple AWS accounts or roles tied to different Okta apps.

The package depends on boto3 for AWS API calls, beautifulsoup4 and html5lib for parsing Okta's SAML responses, keyring for secure credential storage, and fido2 plus ctap-keyring-device for hardware security key support. It's designed for developers and operators who work in Okta-federated AWS environments and want to avoid storing permanent AWS keys locally.

Use it for:

• Obtain short-lived AWS credentials in CI/CD pipelines authenticated via Okta without embedding long-term keys.
• Rotate between multiple AWS accounts or roles within a single Okta tenant without manual credential management.
• Authenticate to AWS CLI and SDKs using Okta MFA (including hardware keys) as the sole credential source.
• Simplify onboarding for teams already using Okta by reusing existing identity without AWS IAM user creation.
• Audit AWS access through Okta's centralized login logs rather than AWS key rotation records.

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

A CLI tool that obtains temporary AWS credentials by authenticating through Okta via SAML, eliminating the need to manage long-lived AWS keys for Okta-integrated environments.

Yes, if your organization uses Okta for identity and has configured SAML integration with AWS. The tool solves a real operational problem—eliminating long-lived AWS keys in Okta-federated environments—and is actively maintained with no known vulnerabilities. The 823-day gap since the last release is a minor concern but does not block adoption for stable use cases; verify that your Okta and AWS setup match the documented prerequisites before deploying.

Install

gimme-aws-creds on PyPI

pip install gimme-aws-creds

uv add gimme-aws-creds

poetry add gimme-aws-creds

Installing gimme-aws-creds

Before you install

Low friction install with a pure-Python wheel. The package is actively maintained with a recent commit (2026-06-02) and has been stable since its 2018 release, though the last PyPI release was over a year ago (2024-05-13).

License in practice

Apache License v2.0 is permissive, allowing commercial and private use with minimal restrictions—suitable for most organizational deployments.

Quickstart

pip install gimme-aws-creds

from gimme_aws_creds import cli

# Run as CLI: gimme-aws-creds --help

Requires Python 3.7 or later; Okta SAML integration with AWS must already be configured in your Okta tenant.

Verify before relying

• Whether the 823-day gap since last release (2024-05-13) indicates the project is in maintenance-only mode or if active development has shifted.
• Support status for MFA methods beyond FIDO2 and Okta Verify (e.g., SMS, email, hardware tokens).
• Whether the tool supports AWS cross-account role assumption or only single-account credentials.

Package facts

Evidence: gimme_aws_creds-2.8.2-py2.py3-none-any.whl

Tags

More Security packages