Skip to content

Merge back to stsci - IGNORE THIS#1

Open
mgough-970 wants to merge 19 commits intosuper-cob:masterfrom
mgough-970:master
Open

Merge back to stsci - IGNORE THIS#1
mgough-970 wants to merge 19 commits intosuper-cob:masterfrom
mgough-970:master

Conversation

@mgough-970
Copy link

No description provided.

jmatuskey and others added 19 commits April 6, 2020 13:39
Co-Authored-By: Yuvi Panda <yuvipanda@gmail.com>
We were creating AWS service users, giving them keys
and then checking those keys in with git-crypt. This isn't
good security practice. We should be creating roles with
minimal permissions instead. These roles can then be 'assumed'
by different entities - an EC2 instance running GitHub actions,
a local user on a computer, etc. This also removes need to
managed EC2 access credentials in a repo - dangerous, and bothersome
to rotate.

This needs corresponding changes in hubploy to use assumed
roles before it can work.
Currently, only the user who created the cluster can
access the cluster. We need to explicitly set role in
[aws-auth](https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html)
to let roles access the cluster.

We set this up, so the hubploy role can actually talk to the
kubernetes cluster
We create a role that can assume only the two roles
necessary for hubploy. This role can only be attached
to ec2 instances
Only needs to run describe-cluster on the one we just
created
…into fix/no-users

# Conflicts:
#	aws-creds/iam.tf
@mgough-970 mgough-970 changed the title Merge back to stsci Merge back to stsci - IGNORE THIS Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants