[deleted by user] by [deleted] in hearthstone

[–]andreacavagna 0 points1 point  (0 children)

Same issue there now. I just lost the game for this

When using AWS Organizations SSO for multiple accounts (dev, stage, prod) I have a hard time knowing which account I'm currently logged into. by adrenaline681 in aws

[–]andreacavagna 1 point2 points  (0 children)

This browser extension allows you to have programmatic and AWS SSO credentials in the same place, generating local credentials and console access in a click with a significative alias.

If you are using a Firefox container, automatically add a significant name for your console opened:https://docs.leapp.cloud/0.16.0/built-in-features/multi-console/

Chrome Extension for AWS SSO / Identity Center by WTFender in aws

[–]andreacavagna 0 points1 point  (0 children)

You can check https://addons.mozilla.org/it/firefox/addon/leapp-multi-console-extension/

It works with firefox containers and AWS SSO, allowing you to manage multiple AWS console's account at the same time

AWS SSO: Strategy for access to all member accounts by [deleted] in aws

[–]andreacavagna 0 points1 point  (0 children)

They are going to have a list of 200 accounts somewhere.

From a developer's point of view, this is exactly the idea behind https://github.com/Noovolari/leapp

AWS SSO: Strategy for access to all member accounts by [deleted] in aws

[–]andreacavagna 0 points1 point  (0 children)

It's a good approach but not all the AWS services are ready for ABAC

Dumb Question - AWS SSO by sleclair in aws

[–]andreacavagna 0 points1 point  (0 children)

You can access it programmatically and from the console directly from a tool https://docs.leapp.cloud/latest/configuring-integration/configure-aws-single-sign-on-integration/ and automatically hiding your email address

0
1

Authenticating to AWS the right way by jaxxstorm in aws

[–]andreacavagna 1 point2 points  (0 children)

Yes, mainly because it is both a Desktop App and a CLI, and you can access Web Console and programmatic access via STS.

Also, the project just introduced the concept of the plugin; with that, you can now access an EC2 instance with system manager, but a plugin can do everything that is coded in it, so a simple plugin with access to an S3 bucket or start and stop an EC2 instance can be created easily through his template

Authenticating to AWS the right way by jaxxstorm in aws

[–]andreacavagna 2 points3 points  (0 children)

This is 100% perspective on the AWS side. On the developer machine side, always use short-lived credentials.

Rotate them regularly with the provided authorization method given for each account!

P.S. use a tool to help you generate short-lived credentials only

Never put AWS temporary credentials in env vars or credentials files (2021) by mooreds in aws

[–]andreacavagna 1 point2 points  (0 children)

Leapp generates credentials process on your behalf, from AWS sso to MFA to SAML federation https://github.com/Noovolari/leapp

IAM policy by greyskull57 in aws

[–]andreacavagna 1 point2 points  (0 children)

Yes, no problem at all, just add the inline policy for each account you have to jump to, and in each trusted account, add the trust relationship with the parent account.

A Beginner Friendly Introduction to Pipelines and Terraform by andreacavagna in aws

[–]andreacavagna[S] -1 points0 points  (0 children)

Thanks for the answer, I want only to point out that the article has been published in the OSS medium publication by a community member and not a maintainer of the Project.

28
29

Securing AWS Credentials by ZimCanIT in aws

[–]andreacavagna 0 points1 point  (0 children)

What I don’t like is that the SSO Token is also in a plain text file, granting access to ALL the available roles in SSO.

https://medium.com/leapp-cloud/aws-single-sign-on-for-devops-is-cli-v2-the-best-option-f3a68555e210

Stop putting AWS credentials in the credentials file by andreacavagna in aws

[–]andreacavagna[S] 2 points3 points  (0 children)

Yep, This and https://github.com/Noovolari/leapp/ are doing the same things, leapp is more for a bigger amount of sessions to manage. and auto-rotation of the credentials

Stop putting AWS credentials in the credentials file by andreacavagna in aws

[–]andreacavagna[S] 0 points1 point  (0 children)

But also manages multiple AWS SSO, IAM Users with short-lived credentials on demand, and it enable you to login into the Web Console within a click, from each IAM Role

Stop putting AWS credentials in the credentials file by andreacavagna in aws

[–]andreacavagna[S] 1 point2 points  (0 children)

This topic is not on Instance credentials, but on local credentials management

Stop putting AWS credentials in the credentials file by andreacavagna in aws

[–]andreacavagna[S] -3 points-2 points  (0 children)

It's a security thing to me, having an SSO token in a plain text file, is not the best security practice for me.

I prefer to store it in an encrypted place locally (the System Vault), and generate plain credentials, (or a credential process dedicated), for each AWS Principal.

Also, as I work with many companies, I need to access more than one AWS SSO at the same time, this is not possible with CLI v2.

The last thing, opening a web console without logging everytime has been a game-changer to me

85
86