Skip to content
This repository has been archived by the owner on Feb 5, 2020. It is now read-only.

AWS credentials should be in TF vars #644

Closed
ggreer opened this issue May 10, 2017 · 5 comments
Closed

AWS credentials should be in TF vars #644

ggreer opened this issue May 10, 2017 · 5 comments
Assignees

Comments

@ggreer
Copy link
Contributor

ggreer commented May 10, 2017

AWS key, secret, & STS token are currently in environment vars. This makes it really hard to apply/destroy a cluster that a user created with the GUI installer. These should be TF vars like region.

@ggreer ggreer added this to the Theme: Overall cleanup and stability milestone May 10, 2017
@alexsomesan
Copy link
Contributor

This opens up the same conversation like we had for the tectonic license and quay pull secreted.
I don't think credentials in configuration are any kind of good practice. Region is not a part of the credentials set.

In the case of using an impersonated role, Terraform itself can do that impersonation, so there's no need to struggle with injecting these three values. They're also refreshed on every run, so no more annoying expired sessions.

If we want to streamline the credentials injection story, I think this is a better path to follow. Ask users to have a role available and put that role in tfvars to be passed to the provider.

Did I mention that credentials in configuration are bad practice? :)

@philips
Copy link
Contributor

philips commented May 15, 2017

Has there been reported friction on this from users on having environment variables used? It seems like the normal flow for AWS and Terraform.

@Quentin-M
Copy link
Contributor

@sym3tri @robszumski Are we doing this?

@robszumski
Copy link
Member

There is some friction, but it sounds like this is normal. Of course, throwing secrets in the file needs to be very controlled. Sounds like we should skip for now.

@sym3tri sym3tri modified the milestones: Sprint 2: Overall cleanup and stability, Sprint 3: Continued Test Automation May 19, 2017
@sym3tri
Copy link
Contributor

sym3tri commented May 26, 2017

Discussed a plan IRL. Closing out and will create new issue with the plan.

@sym3tri sym3tri closed this as completed May 26, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants