forked from pangeo-data/terraform-deploy
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Merge back to stsci - IGNORE THIS #1
Open
mgough-970
wants to merge
19
commits into
super-cob:master
Choose a base branch
from
mgough-970:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-Authored-By: Yuvi Panda <[email protected]>
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
…into fix/no-users
Only needs to run describe-cluster on the one we just created
…into fix/no-users # Conflicts: # aws-creds/iam.tf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.