Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support role assumption #19

Open
andrewkrug opened this issue Nov 13, 2016 · 3 comments
Open

Support role assumption #19

andrewkrug opened this issue Nov 13, 2016 · 3 comments

Comments

@andrewkrug
Copy link
Member

Follow best practices for assumeRole following the Netflix model of having an:

  • Incident Read Role
  • Incident Write Role

aws_ir should be able to create these roles for assumption should they not exist given appropriate privilege for the initial examiner.

@vegardvaage
Copy link
Contributor

Related: how about using the AWS metadata endpoint together with EC2 instance roles so that you don't have to configure AWS keys at all using the AWS SDK? That way one might just spin up a premade AMI, set an instance role for it with the necessary AWS permissions and everything would be ready to go.

@andrewkrug
Copy link
Member Author

@vegardvaage we already use the default credential provider chain. So if you are running in an instance with instance-profile attached it will use that:

http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html

@andrewkrug
Copy link
Member Author

There is a little bit of work to support this WIP https://github.com/ThreatResponse/aws_ir/tree/feature/session_handling

For now I'm going to recommend that users simple use boto profiles and pass those as an optional arg OR set environment vars for AWS_DEFAULT_PROFILE

@andrewkrug andrewkrug self-assigned this Jun 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants