saml2aws
awslogs
saml2aws | awslogs | |
---|---|---|
12 | 8 | |
2,021 | 4,773 | |
0.8% | - | |
9.1 | 6.7 | |
7 days ago | 18 days ago | |
Go | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
saml2aws
- CLI tool to login and retrieve AWS temporary credentials using a SAML IDP
- Script or software that automatically populate specific profile in ~/.aws/credentials
-
Completions plugin `saml2aws`
related: message on saml2aws repo
-
Securing the AWS CLI
If you have an external identity provider, you can add a SAML provider in IAM and use saml2aws locally. The session duration can be configured on the role.
-
don't want to store access key and secret key in plain text in the .aws/credentials file or variables
Or if you have an existing IdP you can use https://github.com/Versent/saml2aws and https://github.com/makethunder/awsudo. By setting up a central account that you put in your trust policy which users can assume roles.
- Script for cli commands with MFA and multiple accounts
-
Show HN: Authenticate into AWS right from your terminal window
In my company everything goes through Active Directory and we use saml2aws [1] to generate credentials with two factor involved. It works quite well for us. We even use this for our artists to create local builds of our games since we keep all important secrets and such in aws secrets mananger. We scope access to said secrets with custom roles and tags.
[1] https://github.com/Versent/saml2aws
- How do you get CLI credentials for a federated role?
-
Getting CLI credentials for an AWS account that is not under your AWS SSO organization
Technically I guess it should be possible with something like saml2aws, but it doesn't support AWS as an IdP yet.
-
saml2aws-multi: a simple tool providing an easy-to-use command line interface for saml2aws
saml2aws-multi is a simple tool I created for using saml2aws more effectively on day-to-day tasks. saml2aws-multi provides an easy-to-use command line interface to support login and retrieve AWS temporary credentials for multiple roles of different accounts with saml2aws.
awslogs
-
Logging in Python Like a Pro
Using the official CLI (aws logs get-log-events) or https://github.com/jorgebastida/awslogs is pretty close to SSH-ing and grepping.
- Tail log groups with CW Logs Insights?
-
I use cw, which is OSS to tail AWS CloudWatch Logs
cw is a native executable targeting your OS, and not needed external dependencies such as pip and npm. Compared to awslogs which is famous helpful tool for CloudWatch Logs1, cw is written in golang and faster.
-
What are you using to analyze/visualize CloudFront logs?
Its a command line tool but some people I know also use awslogs
-
Ask HN: Does anyone else find the AWS Lambda developer experience poor?
Not a full solution, but when I was doing this I really got to love the awslogs utility:
https://github.com/jorgebastida/awslogs
It allows you to stream Cloudwatch logs from the command line, so you can grep them, save them to files, etc... (The web based Cloudwatch interface is terrible.)
Another suggestion is to try to modularize the core business logic in your lambda such that you separate the lambda-centric stuff from the rest of it. Obviously, though, if "the rest of it" is hitting other AWS services, you're going to hit the same testing roadblock.
Or you can try mocking, which may or may not provide much value for you. There's a python library for that, (moto), but it's not 100% up to date wrt AWS services/interfaces, last I had checked. Might be worth a try though.
https://github.com/spulec/moto
-
Datadog alternatives
Cloudwatch Logs is pretty meh visually, but awslogs can give you a pretty good `tail -f`-like experience, and Insights is pretty good. Cloudwatch Metric Filters give you a 'StatsD'-like experience, in that you can log out a certain message or code and then use its appearance as a metric.
-
Cloud watch logs from console always show tail. How to show head without having to click ‘show more’ over and over again?
Check out https://github.com/jorgebastida/awslogs , you can define a `--start`, and it also has a `--watch`, and can be piped the `grep` or whatever you want. It's a pretty flexible tool.
-
DevOps tools you should have on your belt
📖 awslogs - a simple command-line tool for querying groups, streams, and events from Amazon CloudWatch logs.
What are some alternatives?
gimme-aws-creds - A CLI that utilizes Okta IdP via SAML to acquire temporary AWS credentials
Loguru - Python logging made (stupidly) simple
awsume - A utility for easily assuming AWS IAM roles from the command line.
cw - The best way to tail AWS CloudWatch Logs from your terminal
aws-toolkit-vscode - Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
GoAccess - GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through your browser.
aws-extend-switch-roles - Extend your AWS IAM switching roles by Chrome extension, Firefox add-on, or Edge add-on
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
aws-runas - aws-runas rewritten in Go
aws-codebuild-docker-images - Official AWS CodeBuild repository for managed Docker images http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html
leapp - Leapp is the DevTool to access your cloud
faasd - A lightweight & portable faas engine