QRMR, AWS terminal login tool
Work secure using MFA according to best practices, and efficiently with AWS terminal tools like aws cli, aws-shell, terraform, etc.
Highly opinionated Amazon Web Services (AWS) terminal login toolkit, focused on enforcing and simplifying AWS Multi-Factor Authentication (MFA).
Written in Python 3, backwards compatible with Python 2, thanks to futures!
Currently being heavily tested in production against AWS multi-account setup (Well-Architected Framework) on macOS High Sierra.
Feels most at home using virtualenv, of course.
How it works:
Stores your AWS IAM credential profile in ~/.qrmr/credentials.ini;
Prompts for MFA OTP code;
Uses AWS STS to retrieve and store fresh SessionToken and temporary Access Key ID and Secret Access Key using your credential profile.
Near future:
Manage ~/.aws/credentials and ~/.aws/config files
Unit Tests :)
Because you probably just want to start using it:
Installation of QRMR:
pip install qrmr
Setup of AWS Credentials:
qrmr setup
Refreshing your SessionToken and temporary keys:
qrmr refresh
Be cool:
aws s3 ls
REMEMBER: set environment variable AWS_PROFILE in your shell or virtualenv to make life easier:
export AWS_PROFILE=iam_user_name
Find out more features by running:
qrmr --help
Find us on: https://gitlab.com/qrmr/qrmr
Resources:
License / Copyright / Disclaimer:
(c)Copyright 2017 - 2018, all rights reserved by QRMR / ALDG / Alexander L. de Goeij.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Metadata
Release files for qrmr 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qrmr-0.4.2.tar.gz | 8.4 kB | Without provenance | Details for qrmr-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qrmr-0.4.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for qrmr-0.4.2-py2.py3-none-any.whl |
Total release size: 20.1 kB
Release files / qrmr-0.4.2.tar.gz
| Download URL | qrmr-0.4.2.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45ae1e0cd9707a635614c164a13ed969cafbcc5088e6c4d09fecb7d46c5fb504
|
|
BLAKE2b-256 checksum How to use checksums |
e92a80241b95ed87db8e9439caa2c0db2c89c360f9e5d8322a4c5a3689a13b79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / qrmr-0.4.2-py2.py3-none-any.whl
| Download URL | qrmr-0.4.2-py2.py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
53580bb941b80400b5401a8b1877df0fcd0c155341252cd1031882580e5a2be8
|
|
BLAKE2b-256 checksum How to use checksums |
0c7188fc45b5be3aac33eace1e98be45149a6bc52d2631379f53c65760e99dea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for qrmr 0.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.