You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I use the aws_iam_access_key module to generate access keys, they end up stored in plain text in terraform.tfstate and there doesn't seem to be a way around that.
Keeping those keys around in plain text should arguably not be encouraged, not be the default and not be a requirement. There should at least be a way to exclude them from the full text plan or somehow encrypt them.
The text was updated successfully, but these errors were encountered:
ejoubaud
changed the title
Obfuscate secret output in .tfstate (e.g. aws_iam_access_key)
Obfuscate secret values in .tfstate (e.g. aws_iam_access_key)
Dec 23, 2015
Hi @ejoubaud. Thanks for opening this issue! We have been aware of the need to deal with sensitive parts of the .tfstate for a while now - the first issue which addresses it is #516. It's also relevant to #1421. We have a major refactor here on the roadmap - for now we'll continue to update #516 as it develops, so I'll close this issue - if you'd like to track progress here please subscribe to #516! Thanks!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I use the
aws_iam_access_key
module to generate access keys, they end up stored in plain text in terraform.tfstate and there doesn't seem to be a way around that.Input:
And now in the tfstate I have (dummy example):
Keeping those keys around in plain text should arguably not be encouraged, not be the default and not be a requirement. There should at least be a way to exclude them from the full text plan or somehow encrypt them.
The text was updated successfully, but these errors were encountered: