Re:Crypto Tools for DevOps: Git-Crypt – Tozny
by varikin on Monday April 10, 2017 @01:55PM
(#14080938)
Why not store your remote state in S3 buckets? They support encryption at rest.
Re:Crypto Tools for DevOps: Git-Crypt – Tozny
by eamann on Wednesday April 12, 2017 @12:53PM
(#14099468)
S3's "encryption at rest" is transparent (see: http://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-enc...). If someone (or some server) has access to the S3 bucket, they have access to all of the data. Control then is delegated to IAM roles and permissions, not to the crypto model.
> As long as you authenticate your request and you have access permissions, there is no difference in the way you access encrypted or unencrypted objects.
The only advantage of S3 encryption is that if someone walks out of the data center with a disk, they can't read the data on it.
Re:Crypto Tools for DevOps: Git-Crypt – Tozny
by JoshTriplett on Monday April 10, 2017 @08:13PM
(#14083719)
Then you need a different secret in the application: the key to the data in the S3 buckets.
Ultimately, you have to supply at least one secret to the application at runtime, and then it can bootstrap its way to others if needed.
Terraform does support a number of out of band state management backends that I would prefer to use, but none of those backends support encryption at rest. Hopefully hashicorp will roll out support for vault as a backend at some point...