Skip to content

Comments

Add support for AWS Deployments#11

Open
kenXengineering wants to merge 7 commits intokelseyhightower:masterfrom
kenXengineering:feature/aws
Open

Add support for AWS Deployments#11
kenXengineering wants to merge 7 commits intokelseyhightower:masterfrom
kenXengineering:feature/aws

Conversation

@kenXengineering
Copy link

This pull request adds support for Vault deployments in AWS. It follows the same idea as the Google Cloud Platform implementation, utilizing AWS KMS for encrypting/decrypting the unseal keys, and storing the encrypted files in S3.

Added prefix env variable to append a prefix to the encrypted files when storing/reading from storage.

Note: Vault dose support using AWS KMS as a seal wrapper, however this is currently only available in Vault Enterprise.

Utilizes the Official AWS Golang library.  Uses AWS KMS to encrypt the
root token and unseal keys, then stores the values to S3.

Signed-off-by: Ken Herner <kherner@navistone.com>
Signed-off-by: Ken Herner <kherner@navistone.com>
The prefix env variable allows you to specify a key prefix for the files
saved in either AWS S3 or GCP Buckets.

Signed-off-by: Ken Herner <kherner@navistone.com>
Removed the keys from InitResponse as they are not used

Signed-off-by: Ken Herner <kherner@navistone.com>
Signed-off-by: Ken Herner <kherner@navistone.com>
Signed-off-by: Ken Herner <kherner@navistone.com>
Signed-off-by: Ken Herner <kherner@navistone.com>
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.

1 participant