aws-assume-role | open source project published by The Scale Factory | AWS library

by scalefactory Ruby Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | aws-assume-role Summary

aws-assume-role is a Ruby library typically used in Cloud, AWS applications. aws-assume-role has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This is an open source project published by The Scale Factory. We currently consider this project to be hibernating. These are projects that we’re no longer prioritising, but which we keep ticking over for the benefit of the few customers we support who still use them. :information_source: We’re not regularly patching these projects, or actively watching for issues or PRs. We’ll periodically make updates or respond to contributions if one of the team has some spare time to invest. aws-assume-role is a utility intended for developer and operator environments who need to use 2FA and role assumption to access AWS services. aws-assume-role can store both AWS access keys and ephemeral session tokens in OS credential vaults - Keychain on OSX and Keyring on Gnome.

Support

Quality

Security

License

Reuse

Support

aws-assume-role has a low active ecosystem.

It has 37 star(s) with 7 fork(s). There are 6 watchers for this library.

It had no major release in the last 6 months.

There are 3 open issues and 10 have been closed. On average issues are closed in 33 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of aws-assume-role is current.

Quality

aws-assume-role has 0 bugs and 0 code smells.

Security

aws-assume-role has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

aws-assume-role code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

aws-assume-role is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

aws-assume-role releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

aws-assume-role saves you 1023 person hours of effort in developing the same functionality from scratch.

It has 2322 lines of code, 152 functions and 60 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of aws-assume-role

Get all kandi verified functions for this library.

aws-assume-role Key Features

No Key Features are available at this moment for aws-assume-role.

aws-assume-role Examples and Code Snippets

No Code Snippets are available at this moment for aws-assume-role.

Community Discussions

Trending Discussions on aws-assume-role

How to allow an assume role connect from EC2 to EKS on AWS?

It is service account inpersonation in GCP the best way to handle developer credentials and permissions

QUESTION

How to allow an assume role connect from EC2 to EKS on AWS?

Asked 2021-Aug-13 at 05:05

I created an EC2 instance and an EKS cluster in the same AWS account. In order to use the EKS cluster from EC2, I have to grant necessary permissions to it.

I added an instance profile role with some EKS operation permissions. Its role arn is arn:aws:iam::11111111:role/ec2-instance-profile-role(A) on dashboard. But in the EC2 instance, it can be found as arn:aws:sts::11111111:assumed-role/ec2-instance-profile-role/i-00000000(B).

...

ANSWER

Answered 2021-Aug-13 at 05:05

- name: external-staging
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - exec
      - test-dev
      - --
      - aws
      - eks
      - get-token
      - --cluster-name
      - eksCluster-1234
      - --role-arn
      - arn:aws:iam::3456789002:role/eks-cluster-admin-role-e65f32f
      command: aws-vault
      env: null

Source https://stackoverflow.com/questions/68766219

QUESTION

It is service account inpersonation in GCP the best way to handle developer credentials and permissions

Asked 2020-Feb-05 at 03:44

In GCP service account inpersonationis a way to create temporary IAM credentials to perform an action as developer (see here). This have been describe as equivalent to assuming a role in AWS , see this other question.

My question is:

is this the recommended/canonical way of doing this in google cloud, namely grouping permissions around service accounts & allowing developers to inpersonate that service account ? Or alternatively is it better to create custom roles and assign them directly to developers identities (and not indirectly via a service account) ? But then of course you lose the advantage of short living credentials.

If the first option is valid it would also mean that you would end up having as many service accounts as roles in AWS.

...

ANSWER

Answered 2020-Feb-05 at 03:44

In general, you should grant IAM roles to groups, and then add developers to the appropriate groups.

For example, you may want to grant all developers "Editor" access to a project. To do this, grant group:ll-developers@yourcompany.com the Editor role to the project. Then, use LDAP or G Suite to ensure that all developers are a member of that group.

You can give developers the ability to actAs a service account, but then the audit logs and principle would be the service account, not the developer.

Source https://stackoverflow.com/questions/60068658

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install aws-assume-role

You should already have an IAM user that you can log in to via AWS' console. If you do not already have an AWS access key and matching secret key for your own IAM user, use the AWS console to create that credential pair.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: